Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!haven!uflorida!gatech!hubcap!ncrcae!secola!gharris
From: gharris@secola.Columbia.NCR.COM (Buddy Harris)
Newsgroups: comp.lang.c
Subject: Re: Explanation of "Case-sensitive"
Message-ID: <354@secola.Columbia.NCR.COM>
Date: 1 May 89 13:40:17 GMT
References: <13174@dartvax.Dartmouth.EDU> <30009@sri-unix.SRI.COM>
Reply-To: gharris@secola.Columbia.NCR.COM (Buddy Harris)
Distribution: na
Organization: NCR SE-Columbia, West Columbia, SC
Lines: 26

In article <30009@sri-unix.SRI.COM> trent@unix.sri.com (Ray Trent) writes:
>In the above article, jskuskin@eleazar.dartmouth.edu (Jeffrey Kuskin) writes:

>>In Pascal (a case-insensitive language by my definition), "myVar := 2"
>>is the same as "mYvAR := 2"
>
>One way
>of preventing idiots from using both "mYvAR" and "MyVar" in the same
>program is to make the language case sensitive. 

But shouldn't someone who is making the case for case-sensitivity double-check
the cases that they are writing in.  This shows how easy it is to accidentally
mess up a case that could take days to find depending upon your compiler.  And 
if you want types, variable, pointers, functions, etc. to have similiar names,
try a convention like tname, vname, pname, fname, etcname.  I will live with 
the C (or is it c) case-sensitivity, but I don't have to like it.  





-- 
------------------------------------------------------------------------------
! Sleep well and dream of large women.  -  The Dread Pirate Roberds          ! 
! gharris@secola.Columbia.NCR.COM (George Harris)  Have a nice day :-)       !
------------------------------------------------------------------------------