public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Fergus Henderson <fjh@cs.mu.OZ.AU>
To: earnie_boyd@yahoo.com
Cc: gw32 <gnu-win32@cygnus.com>
Subject: Re: Asterisk expansion...
Date: Mon, 27 Jul 1998 14:23:00 -0000	[thread overview]
Message-ID: <19980728010316.56058@mundook.cs.mu.OZ.AU> (raw)
In-Reply-To: <19980727142753.6493.rocketmail@send1e.yahoomail.com>

On 27-Jul-1998, Earnie Boyd <earnie_boyd@yahoo.com> wrote:
> ---Fergus Henderson <fjh@cs.mu.OZ.AU> wrote:
> > My point is that your statement "It is the shells job to do the globbing
> > not the programs", while valid in Unix, is not valid in DOS, and it
> > is not valid in any unqualified sense in gnu-win32.
> 
> I know from the experience of my mingw32-sup package that cmd.exe and
> commmand.com do globbing, it is not as robust though.

It has nothing to do with robustness.  `cmd.exe' and `command.com' do
globbing only for their builtin commands, because according to the DOS
design it is the program's responsibility to do globbing, not the
shell's.  This design is in fact *more* robust (although arguably less
flexible) than the Unix design, because it problems with commands such
as `cp *.c' sometimes silently doing the wrong thing instead of
reporting an error message.

(The reason that the Unix design is arguably more flexible is that it
allows you to change the globbing syntax by simply changing shells.)

> For example:
> `ls' doesn't do any globbing, it only reports on a list of files given
> it on stdin.  I ported it to native win32 using mingw32.

If you didn't add code to `ls' to glob-expand its arguments as part
of that port, then you didn't do a complete port, and the problem
is thus best ascribed to a bug in your port, not to any lack of robustness
in the way DOS handles globbing.

-- 
Fergus Henderson <fjh@cs.mu.oz.au>  |  "I have always known that the pursuit
WWW: < http://www.cs.mu.oz.au/~fjh >  |  of excellence is a lethal habit"
PGP: finger fjh@128.250.37.3        |     -- the last words of T. S. Garp.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

  reply	other threads:[~1998-07-27 14:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-27 14:23 Earnie Boyd
1998-07-27 14:23 ` Fergus Henderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-07-31 12:10 Earnie Boyd
1998-07-31  3:03 Earnie Boyd
1998-07-29 17:43 Andrew Dalgleish
1998-07-28  5:54 Andrew Dalgleish
1998-07-28  0:57 Robertson, Jason V
1998-07-27 15:12 ` Michael Weiser
1998-07-27  9:00 Earnie Boyd
1998-07-27  9:00 ` Fergus Henderson
     [not found] <35B93BE2.2642EDA3@home.com>
1998-07-25 18:10 ` Jason V Robertson
1998-07-27 14:23   ` Michael Weiser
1998-07-24 12:58 Earnie Boyd
1998-07-25  1:22 ` Fergus Henderson
1998-07-25 10:30   ` Leo Mauro
1998-07-23 15:30 Robertson, Jason V
1998-07-24 11:17 ` Matthias Morche
1998-07-24 12:58 ` Mike Bandy
1998-07-25  0:08 ` Michael Hirmke
1998-07-25  4:14   ` Fergus Henderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19980728010316.56058@mundook.cs.mu.OZ.AU \
    --to=fjh@cs.mu.oz.au \
    --cc=earnie_boyd@yahoo.com \
    --cc=gnu-win32@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).