Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!sco!seanf
From: seanf@sco.COM (Sean Fagan)
Newsgroups: comp.lang.c
Subject: Re: Explanation of "Case-sensitive"
Message-ID: <2630@scolex.sco.COM>
Date: 1 May 89 23:26:34 GMT
References: <13174@dartvax.Dartmouth.EDU> <175100004@hobbiton> <39708@think.UUCP> <59@ajfcal.UUCP>
Reply-To: seanf@scolex.UUCP (Sean Fagan)
Organization: The Santa Cruz Operation, Inc.
Lines: 19

In article <59@ajfcal.UUCP> tony@ajfcal.UUCP (Tony Field) writes:
>In article <39708@think.UUCP>, barmar@think.COM (Barry Margolin) writes:
>> And the reason Unix is case-sensitive is that it was modeled after
>> Multics, which is also case-sensitive.  I suspect that the reason
>> Multics was made case-sensitive was that it seemed more modern.
>      .. etc ..

Another reason (or advantage) in Unix's case-sensitivity is that filenames
can have any character other than '/' and '\0'.  Every OS I've seen that had
case-*in*sensitivity would only allow a small subset of those.

Of course, you generally can't have a variable, in C, called 'M-fooM-bar'
(where M-<x> is Meta-<x>)... 8-)


-- 
Sean Eric Fagan  | "An acid is like a woman:  a good one will eat
seanf@sco.UUCP   |  through your pants." -- Mel Gibson, Saturday Night Live
(408) 458-1422   | Any opinions expressed are my own, not my employers'.