cvs.gedasymbols.org/archives/browse.cgi   search  
Mail Archives: djgpp/2003/01/28/13:33:45

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 11:15:28 CST
Organization: Rice University, Houston TX
Lines: 14
Message-ID: <3e36bab0.sandmann@clio.rice.edu>
References: <b16aeu$ilk$1 AT sass2141 DOT sandia DOT gov>
NNTP-Posting-Host: clio.rice.edu
X-Trace: joe.rice.edu 1043776108 5639 128.42.105.3 (28 Jan 2003 17:48:28 GMT)
X-Complaints-To: abuse AT rice DOT edu
NNTP-Posting-Date: 28 Jan 2003 17:48:28 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

> Comman line filename expansions (any presumably others) seem to be case
> sensitive.  Thus running a program
>     prog *.vec
> will fail with a memory access exception (before main() is started) if the
> files were written as upper case, say A.VEC and B.VEC.  Running with
>    prog *.VEC
> will work.

I think we need more information (such as a reproducible example) and
the versions you are using to help here.  I have a Windows 2000 system
and I don't see any exceptions.  

For example, djecho *.vec and djecho *.VEC both return the same thing

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019