Path: news.daimi.aau.dk!news.uni-c.dk!sunic!trane.uninett.no!nntp.uio.no!usenet From: aas@velociraptor.nr.no (Gisle Aas) Newsgroups: comp.lang.beta Subject: Re: Why can't we have ... ? Date: 20 Sep 1994 12:27:06 GMT Organization: Norwegian Computing Center, Oslo, Norway Lines: 24 Message-ID: References: <35j8ki$3ld@engnews2.Eng.Sun.COM> <35mffu$bu1@fbi-news.informatik.uni-dortmund.de> Reply-To: Gisle.Aas@nr.no NNTP-Posting-Host: velociraptor.nr.no In-reply-to: hofmeist@kleene.informatik.uni-dortmund.de's message of 20 Sep 1994 11:02:22 GMT In article <35mffu$bu1@fbi-news.informatik.uni-dortmund.de> hofmeist@kleene.informatik.uni-dortmund.de (Thomas Hofmeister) writes: > What could be the advantage of case sensitive identifiers? One thing is that it forces the programmer to write identifiers the same way. "TempMemory", "tempmemory", and "TEMPMEMORY" look very different. It is also easier for external programming tools to handle identifiers that look exactly alike. Another thing is that is it often nice to have both classes and instance variable have the same name, but use different capitalization. Besides there will be a lot more short (1-2 char) identifiers to choose from. (# Room: (# ... #); ... room: @Room; (* instead of "theRoom", "aRoom" or something *) #) But introducing case sensitive identifiers at this late stage would break a lot of programs!! -- ¤ Gisle Aas - Norsk Regnesentral