Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ukma!rutgers!bellcore!texbell!sugar!ficc!peter
From: peter@ficc.uu.net (Peter da Silva)
Newsgroups: comp.lang.c
Subject: Re: Explanation of "Case-sensitive"
Message-ID: <3952@ficc.uu.net>
Date: 24 Apr 89 13:37:51 GMT
References: <13174@dartvax.Dartmouth.EDU>
Distribution: na
Organization: Xenix Support
Lines: 22

In article <13174@dartvax.Dartmouth.EDU>, jskuskin@eleazar.dartmouth.edu (Jeffrey Kuskin) writes:
> Why was C specified this way?  A case-insensitive language puts no
> restrictions on source-file formatting:  symbolic constants can be
> all upper case, variables all lower case, functions mixed-case, etc.

Neither does a case-sensitive language. In fact, the draft Ferranti coding
standard for 'C' makes such a distinction. If you're consistent, you win.
If you're inconsistent, then you win (oh, I should have called it MyVar,
now shouldn't I?).

> The only difference comes at compile time when silly errors (IMHO)
> such as "mYvAR not declared" start to appear (when you *have* declared
> "myVar").

Why would you do that?

How about confusing "Ile", "lIe", and "IIe"? Silly errors.
-- 
Peter da Silva, Xenix Support, Ferranti International Controls Corporation.

Business: uunet.uu.net!ficc!peter, peter@ficc.uu.net, +1 713 274 5180.
Personal: ...!texbell!sugar!peter, peter@sugar.hackercorp.com.