From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Command line wildcard expansion under Win2K
Date: Tue, 28 Jan 2003 20:43:52 CST
Organization: Rice University, Houston TX
Lines: 21
Message-ID: <3e373fe8.sandmann@clio.rice.edu>
References: <b16osl$pkd$1 AT sass2141 DOT sandia DOT gov>
NNTP-Posting-Host: clio.rice.edu
X-Trace: joe.rice.edu 1043809804 4741 128.42.105.3 (29 Jan 2003 03:10:04 GMT)
X-Complaints-To: abuse AT rice DOT edu
NNTP-Posting-Date: 29 Jan 2003 03:10:04 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

> As Charles notes *.vec and *.VEC DO do the same thing.  The problem is with
> a*.vec, which only works if the a and obj parts are lower case, or A*.VEC,
> which only works i A and VEC are upper case in the real directory entry.
> They simply return the pattern, as a Unix program would do.  All this does
> occur in djecho, at least for me.

I see this behavior.  For example, "A.vec" exists (A upper case):

C:\>djecho a*.vec A*.vec A*.VEC a*.VEC
a.vec A.vec A*.VEC a*.VEC

This behavior is not Win2K specific - it also happens on Win98

"B.VEC" exists (all upper case):

C:\>djecho b*.vec B*.vec b*.VEC B*.VEC
b.VEC B*.vec b*.VEC B.VEC                    (on Win98, either build)
B.VEC B*.vec b*.VEC B.VEC                    (Win2K, v2.03 refresh)
b.vec B*.vec b*.VEC B.VEC                    (Win2K, CVS build)

It is certainly not what I would expect.