At 09:49 AM 10/17/2006 -0400, Hal Kaplan wrote:
Filenames are not case-sensitive. a.b is exactly the same as A.B or a.B or A.b , etc.
They are in Unix systems
We are talking about cosmetics here. The OS would actually run faster and be less intrusive if filenames were case-sensitive because all the "normalizing" that takes place would be eliminated. Filename-intensive apps would run quicker too.
I'm not talking about cosmetics. I'm talking about function. The file ThisIsCrap.ms should be opened even if it is referenced as THISISCRAP.ms. Having 1 file named Thisiscrap.ms and another allowed to exist (in same directory) named ThisIsCrap.ms is ridiculous. It'll trip up users often, and professionals frequently.
I agree that case-sensitive probably processes faster because the OS didn't take the time to 'normalize' (e.g. uppercase/lowercase) the file name request. But, IMO, that's one of the things the OS should do.
Actually, changing to case-sensitive filenames at this point in time would be consistent with M$'s practice of arbitrarily changing things.
Very true. I think MS may already be part way there on XP (original thread was about some filename thing between VFP and the OS?) Why the heck are we supporting MS again? We're about as 'dumb' as case-sensitive filenames..... Oh well, if we were over in the Linux world, I guess we'd still be saddled with stupid case-sensitive filenames.
-Charlie _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
