Mail Archives: djgpp/2003/06/27/06:15:11
> > "Eli Zaretskii" <eliz AT elta DOT co DOT il> wrote in message
> > news:2593-Wed25Jun2003075056+0300-eliz AT elta DOT co DOT il...
> > > > From: "deckerben" <bdeck AT lycos DOT co DOT uk>
> > > > Newsgroups: comp.os.msdos.djgpp
> > > > Date: Tue, 24 Jun 2003 23:34:01 +0200
> > > This is not the default because in most situations the behavior you
> > > see now is what users want, especially if they have files that come
> > > from DOS (where _all_ directory entries are in UPPERCASE).
> > I really understand the DOS issue. But this would not be true under NT
> > systems, where true filename cases are reported correctly.
> I meant DOS filenames under Windows, not under DOS. So your case is
> included.
This is just wrong. NT returns filename case correctly, from both the CMD
and COMMAND prompts. You are probably refering to Windoze32 DOS-based
thunking OSes. They are still DOS. NT is not DOS.
"Hans-Bernhard Broeker" <broeker AT physik DOT rwth-aachen DOT de> wrote in message
news:bdeepo$jik$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE...
> deckerben <bdeck AT lycos DOT co DOT uk> wrote:
> > I really understand the DOS issue. But this would not be true under NT
> > systems, where true filename cases are reported correctly.
> I'm not all that sure about "are". They *can* be, just like they can
> be under 9x. Whether they are or not is a configuration option.
Do you actually have NT? I have yet to see NT return a directory list in all
upper-case. A person who knows what he is doing might be able to change this
default behavior, but then it's their own idea.
> > Fooling with this causes problems... (I thought something was *really*
wrong).
> Some *is* really wrong, but I disagree that the behaviour of DJGPP is.
I gave this some thought, too. But I would consider it wrong to disable a
capability provided by the OS because of an intentional limitation of the
programming tools. This situation reminds me of the strange Rhide failure to
recognize a 'C' sourcefile just because the extension *wasn't* uppercase.
This all seems a bit overly-complicated. I know the "reasons" for that, but
from my end, that just doesn't seem consistant with this discussion now, for
example.
> Then you should als recommend they be prepared for some rather strange
> behaviour in all kinds of tools.
No, strange behavior is when I do an 'ls' to see everything just as 'dir'
reports, except that all uppercase files are now lowercase. That's strange.
Especially when the OS *doesn't* require it whatsoever.
> Trying to depend on the case of filenames in any way is usually a
> futile exercise on Windows.
Not on NT. NT is not DOS. IMHO, the "failure" is in DJGPP in this single
case.
> > I am recommending all NT-based PythonD users to set FNCASE=y.
...and I still am. Believe me, I really gave this some thought, and I think
that the best solution is for DOS/Win32 users to define PYTHONCASEOK=1, and
NT users to define FNCASE=y.
Please remember, I don't recommend anything that I'm not doing myself.
Please also remember that many many PythonD users are *not* DJGPP users.
Most letters I get come from folks that are having problems because they
don't want DJGPP installed. Just Python. I am not a fan of telling my users
that the need to rewrite all their packages because of stuff like this.
Sorry.
It is possible that my thinking will change again later on this.
Ben
- Raw text -