Date:	Thu, 2 Apr 92 10:32:16 EST
From:	marc DOT hoffman AT spd DOT analog DOT com (Marc M. Hoffman)
To:	PEPRBV AT CFAAMP DOT BITNET
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu, PEPRBV AT CFAAMP DOT BITNET
Subject:	Last word (for now) on globbing
Status:	O

   Date: Mon, 1992 Mar 30 16:33 EST
   From: Bob Babcock <PEPRBV AT CFAAMP DOT BITNET>

   >Just a note: I added globbing to go32 1.06 over the weekend.  It's
   >primitive, but it works.

   Can this be disabled?  I've always thought that globbing by the shell
   is a mistake.  The program should get first crack at the command line,
   and the shell should provide a convenient method of globbing only if it
   is desired.  The simplest example of a program which fails if the shell
   does globbing is something like WHEREIS which searches an entire disk
   for a file matching a wildcard.  If the shell expands the wildcard, you
   get an error if it doesn't match something in the current directory, or
   if something does match, then WHEREIS doesn't see the wildcard.  Of
   course, WHEREIS doesn't require 32-bit protected mode, but the same
   sort of problem could arise with a program which knows where its data
   files are kept and doesn't require a complete path on the command line.


Can't you just quote the regex so the shell doesn't do globbing??  And
I don't belive that globbing by the shell is a mistake it reduces code
size and makes applications simpler to write.

- Raw text -