From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Command line wildcard expansion under Win2K
Date: Thu, 30 Jan 2003 00:25:11 CST
Organization: Rice University, Houston TX
Lines: 20
Message-ID: <3e38c547.sandmann@clio.rice.edu>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1030129080002 DOT 11962C AT is> <b193vm$hpg$1 AT overload DOT lbl DOT gov>
NNTP-Posting-Host: clio.rice.edu
X-Trace: joe.rice.edu 1043908431 14584 128.42.105.3 (30 Jan 2003 06:33:51 GMT)
X-Complaints-To: abuse AT rice DOT edu
NNTP-Posting-Date: 30 Jan 2003 06:33:51 GMT
X-NewsEditor: ED-1.5.9
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

First, I suggest looking at the info docs for the glob function, which
is what DJGPP internally calls to handle the command line:

info libc alpha glob

About 57% down the page is text:

On MSDOS, filenames are always matched case-insensitively.  On
filesystems that preserve letter-case in filenames (such as Windows 9x),
matches are case-insensitive UNLESS THE PATTERN INCLUDES UPPERCASE
CHARACTERS. (my caps)

So, if you use any upper case characters on your input you may be
surprised.  I believe this is the behavior which is non-intuitive.

There are some good reasons for this behavior, but I agree it would be
nice in many applications to be able to turn it off case sensitive
matching and still be able to return the lowercased names when 
appropriate.