Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!mcvax!ukc!etive!lfcs!sam
From: sam@lfcs.ed.ac.uk (S. Manoharan)
Newsgroups: comp.lang.c
Subject: Re: case sensitivity
Message-ID: <1831@etive.ed.ac.uk>
Date: 24 Apr 89 10:02:53 GMT
References: <1989Apr21.194615.5344@utzoo.uucp> <4402@goofy.megatest.UUCP> <17061@mimsy.UUCP> <850@twwells.uucp>
Sender: news@etive.ed.ac.uk
Reply-To: sam@lfcs.ed.ac.uk (S. Manoharan)
Organization: Laboratory for the Foundations of Computer Science, Edinburgh U
Lines: 27



    Bill ({ uunet | novavax } !twwells!bill) writes:
>In article <17061@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes:
: More seriously: I have used languages that ignore case, and languages
: that care about case, and have never been particularly impressed with
: the former, nor particularly excited about the case distinctions in the
: latter.

>I use the case of identifiers to tell me some important bits of
>information about the identifier that are not properly conveyed by the
>name.  Here's my table:


>Having these distinctions made consistently makes reading the code
much easier.
>

Having two ids foo and FOO that mean  two different things will sure
lead to confusion. If one accepts this, 
how would a case-insensitive language not support readabiltity?
And how would a case-sensitive lang  make the id-name space larger?

Voice: 031-667 5076                          S. Manoharan
Janet: sam@uk.ac.ed.lfcs                     Dept of Computer Science
Uucp : ..!mcvax!ukc!lfcs!sam                 University of Edinburgh
Arpa : sam%lfcs.ed.ac.uk@nss.cs.ucl.ac.uk    Edinburgh EH9 3JZ    UK.