Date:	Tue, 28 Jan 2003 19:29:44 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	djgpp AT delorie DOT com
Message-Id:	<6137-Tue28Jan2003192943+0200-eliz@is.elta.co.il>
X-Mailer:	emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
CC:	"Gary Hubbard" <me AT sandia DOT gov>
In-reply-to:	<b16aeu$ilk$1@sass2141.sandia.gov> (me@sandia.gov)
Subject:	Re: Command line wildcard expansion under Win2K
References:	<b16aeu$ilk$1 AT sass2141 DOT sandia DOT gov>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: "Gary Hubbard" <me AT sandia DOT gov>
> Newsgroups: comp.os.msdos.djgpp
> Date: Tue, 28 Jan 2003 08:18:09 -0800
> 
> Comman line filename expansions (any presumably others) seem to be case
> sensitive.

That's true: DJGPP tries to mimic a Unix environment, and thus
file-name expansion is by design case-sensitive.  However, since the
filesystems on which DJGPP runs are case-INsensitive, the wildcard
expansion tries to play along: the file names match case-insensitively
unless the wildcard includes upper-case characters.

See the documentation for the library function `glob' for more details
(type "info libc alpha glob" from the DOS prompt).

> 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.
> 
> Is this a known problem?

No, I don't think we know about this problem.  Please post the
details:

  - the exact command you type from the command prompt;

  - the exact error message(s) printed when the program fails, and

  - the output of "dir /x" in the directory where you run the failing
    command.

Thanks.

- Raw text -