Re: The case insensitive #include statement horror...
"Carl Daniel [VC++ MVP]" <cpdaniel_remove_this_and_nospam@mvps.org.nospam>
wrote in message news:e8cMioJFHHA.4432@TK2MSFTNGP03.phx.gbl...
IMO that's a great idea. A little cross-polination between the 'doze and
'nix teams is a good thing on many levels.
Really? Except for the fact that it makes me feel like I have used a time
machine every time I log on, I can't think of a good one. <bseg>
Seriously, what irks me about posts like the OP's, is that what underlies
his question is that there is some a priori reason why Windows should behave
like 'nix, 'nux and 'pux. There is not.
Looking for the option he wants would be like asking to turn off the file
system's case sensitivity on his favored platform.
And as to specifics, there are some things that exist on 'nix that might be
nice to have on my favorite platform. The single-rooted file system
namespace might be one.
But for the life of me, I can't figure out why it would be a good thing for
the file system to allow the existence of two distinct files foo.h and
Foo.h, for example. Chances are the reason is historic and goes back to the
times when the o/s designers feared the machines of the day didn't have the
horsepower for the case insensitive compares.
I don't want to relive the 80s. Been there. Done that. :-)
Regards,
Will