Xref:	news2.mv.net comp.os.msdos.djgpp:4038
From:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Are "real" long filenames possible with DJGPP v2 (make)?
Date:	Sun, 19 May 1996 23:31:31 CDT
Organization:	Rice University, Houston, Texas
Lines:	26
Message-ID:	<319ff5a3.sandmann@clio.rice.edu>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 960519194419 DOT 10504R-100000 AT is>
Reply-To:	sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host:	clio.rice.edu
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

> I think when LFN is set to y, opendir should always preserve case and 
> the filenames shouldn't be dosified.  Why should a user be requested to 
> define additional variables?  Is something wrong with what I suggest?

This is one of the little details that I never finished with LFNs.  In 
the opendir/readdir code, DJ and I agreed that if LFNs were turned on,
and the file contained any lower case and/or special characters, it 
wouldn't be "tolower"ed.  If the name was 8.3 and all upper case, it would
still be lowercased for compatibility.

The other place that needed to be hacked was the built-in globbing code,
which also tolower's all the names.

I also think argv[0] is provided as the short name always, no matter if you
invoked it with the long or short.

Lots of details - but at the time V2 was betaing/released there were only
a couple of people who had tried the code and we weren't sure if anyone
would care (which is why it was supposed to be off by default).

> Btw, I always though that Win95 is case-preserving but case-insensitive. 
> If I'm correct, then "TheLongFile" and "thelongfile" should be treated by
> Win95 as if it were the same file.  Isn't this the case?

This is usually the case, but there are flags in the file system to support
case sensitivity, but I'm not sure if they work/are implemented anywhere.

- Raw text -