Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!boulder!stan!ddv
From: ddv@Solbourne.COM (Dan DeVries)
Newsgroups: comp.lang.c
Subject: Re: Explanation of "Case-sensitive"
Message-ID: <860@tp.Solbourne.COM>
Date: 22 Apr 89 21:16:40 GMT
References: <13174@dartvax.Dartmouth.EDU>
Reply-To: ddv@Solbourne.com (Dan DeVries)
Distribution: na
Organization: Solbourne Computer Inc., Longmont, Colorado
Lines: 12

I'm suprised this hasn't come up.

In (K&R) p179 it states that external identifiers may be constrained
by the loader.  It gives 2 examples (IBM,Honeywell) where the loader
only uses one case.  Therefore, the argument about increased naming
space is not true for external identifiers (assuming portable code is
desirable).  The loader may map Tree and tree to the same identifier.

I have yet to here a good argument for cases being distinct, and have
seen several that say it's a bad idea.  So, once again:

Why is C case sensitive?  And who can we blame for this mistake?