Re: The case insensitive #include statement horror...

William DePalo [MVP VC++] wrote:

OK. That's your point of view. What follows from it is the fact, say, that
given a string of eight characters there are 256 possible files which can
live in one directory, using those characters in the given order, which
differ only in case. As I see it, that's just nuts. :-)

"No bit left behind!"

The point I have been trying to make here is that you are applying a 'nix
mindset to Windows.

That's just a coincidence, I had this mindset before I got in contact with
Unix. I like "Do what I say"-things better than "Do what most people
mean"-things, especially for computers.

But you are right in the sense, that wanting Windows change it fs behaviour
would be the wrong way. I don't want to change its philosophy. I just hoped
to find a tool for a technical problem in the development tools from
Microsoft. But I understand, that there are good reasons for the dev-team
not to waste its time with implementing such functions (although I think I
gave some reasons why there might be some needs for this functionality) -
but I get it anyway, just not out of the box, I do it myself.

But it makes it easy to lose this data, since someone can
easily overwrite this semantics accidently by writing another
file with a similar name, differing only in case.

No, we won't allow two different files with names that differ only in case
to be created in the same directory and with the Win32 API.

See, and thats where the original data gets lost... But I don't care about
that, I always have backups. Although I do not like that feature of the
Windows fs, I can live with it and accept it. What I wanted, was something
different. The fs should not be changed to be case sensitive, instead I
wanted a check in the development tools that compares the case of include
statements to the case of the actual filename on the disk and probably
print out a warning or better an error.

Regards
Stephan
.

Relevant Pages

  • Re: What is a unique Joliet name?
    ... "Joliet" is a system level file specification for CDs and the naming rules - length, allowed characters, etc - it requires differ from those of Windows itself. ...
    (microsoft.public.project)
  • Re: Window sizing buttons
    ... When the caption buttons differ, that usually suggests that the Windows in Taskbar settings are different. ... Click the Office button, Word Options, Advanced tab, Display section, and compare to see if both computers have the same setting for "Show all windows in the Taskbar". ...
    (microsoft.public.word.docmanagement)
  • Re: 500 Cant connect to search.cpan.org:80 (Bad protocol tcp) at web.plline 24.
    ... :>I beg to differ... ... be interpreted as an internal Perl command or a shell one). ... : of Windows APIs capabilities. ...
    (comp.lang.perl.misc)
  • Re: Same content, but doesnt fit
    ... If the horizontal specs of the characters in the first PN differ from the ... original file fits an average of 2-4 lines more per page). ...
    (microsoft.public.word.pagelayout)
  • Re: XML Manifest contains invalid characters
    ... Windows views them identically, who am I to differ. ... String consisting of Characters 0 through 255 into Unicode, ... I'm not so sure that it actually /is/ evolving all that much in Dolphin. ...
    (comp.lang.smalltalk.dolphin)
Loading