Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!novavax!twwells!bill
From: bill@twwells.uucp (T. William Wells)
Newsgroups: comp.lang.c
Subject: Re: Just Wondering
Message-ID: <866@twwells.uucp>
Date: 25 Apr 89 21:57:25 GMT
References: <10095@smoke.BRL.MIL> <12561@lanl.gov>
Reply-To: bill@twwells.UUCP (T. William Wells)
Organization: None, Ft. Lauderdale
Lines: 21
Summary:
Expires:
Sender:
Followup-To:
Distribution:
Keywords:

'Round and round we go...

In article <12561@lanl.gov> jlg@lanl.gov (Jim Giles) writes:
: Most people DO mentally mapp int monocase when reading.  Otherwise,
: I would haver to conclude that the word "DOES" is your statement is
: intended to mean something other than "does".  In fact these are
: perfect examples of why a programming language should NOT be case
: sensitive.  It allows better code readibility by allowing the programmer
: to EMPHASIZE parts of the code.

Inconsistent casing Makes the Code harder to Read. Consistent casing
is better, pretty much independetly of which style of case you use.

And if you use consistent casing, you want your compiler system to
tell you when you've goofed.

So, even if you want to use case for such purposes as emphasis, you
want case sensitivity in the language.

---
Bill                            { uunet | novavax } !twwells!bill