Mosh Teitelbaum wrote:
> > I imagine the powers that be in Redmond figured that allowing
> > multiple files that were all named the "same thing" (despite case
> > differences) would be too confusing for the intended every day users
> > of the
> > OS.

Sean A Corfield wrote:
> Remember that DR-DOS predates MS-DOS (and Windows) and was 8.3 filename
> format (and case insensitive). MS-DOS was 'compatible' with that and
> every single Windows version inherited that. An interesting comparison
> is Mac OS X - Mac OS has also historically been case insensitive, as is
> Mac OS X, but OS X is Unix Inside(tm) so there's a conflict of
> personalities here... resolved in favor of Mac OS: the UNIX under the
> hood is case INsensitive!

Granted, MS inherited case-insensitivity from DR-DOS but, like Apple did
with OS X, MS could have made it case-sensitive.  But... [see my original
comments] 8^)

> > I think though, like with Windows, the intended audience
> > for the OS were people who would want near complete control over their
> > environment and would likely be very comfortable differentiating between
> > files that were spelled the same but cased differently.
>
> Yes, and when you can easily map filenames to lowercase it's not such a
> big deal:
>
>       for f in *[A-Z]*
>       do
>               mv $f `echo $f | tr A-Z a-z`
>       done
>
> :)

Wait!  That's one of those 30-odd commands I don't remember.  8^)

(And what about all the code that had already been written referring to
mixed-case filenames?  sed & awk anyone?  Bleh).  8^)

--
Mosh Teitelbaum
evoch, LLC
Tel: (301) 625-9191
Fax: (301) 933-3651
Email: [EMAIL PROTECTED]
WWW: http://www.evoch.com/

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

Reply via email to