Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!agate!pasteur!ames!pacbell!att-ih!ihnp4!ihlpf!nevin1 From: nevin1@ihlpf.ATT.COM (00704a-Liber) Newsgroups: comp.lang.misc Subject: Re: case sensitivity Message-ID: <4049@ihlpf.ATT.COM> Date: 18 Mar 88 18:36:47 GMT References: <2318@bsu-cs.UUCP> <2400010@otter.hple.hp.com> <2832@csli.STANFORD.EDU> Reply-To: nevin1@ihlpf.UUCP (00704a-Liber,N.J.) Organization: AT&T Bell Laboratories - Naperville, Illinois Lines: 34 In article <2832@csli.STANFORD.EDU> kasper@csli.UUCP (Kasper Osterbye) writes: >In a previous posting I said that I would like to be able to use both >cases (upper and lower) in my writing and reading, but the compiler >should not be able to tell the difference between i and I. > >I hereby retract from the scene, a bit wiser. Don't retract so fast :-)! Following this discussion, there seems to be only two possibilities: A) Variables such as 'CaseVar' and 'casevar' should be considered the same. (Case-insensitive) B) Variables such as 'CaseVar' and 'casevar' should be considered distinct. (Case-sensitive) There is a third possibility. Here is my proposal: C) If two or more variables, such as 'CaseVar' and 'casevar', only differ with respect to case, only one of the variable declarations is allowed and the other declarations result in an error (or alternatively, the variables are consdered distinct but the second and subsequent declarations produce warnings). This seems to fix the problems with case-sensitive and case-insensitive languages. Comments?? -- _ __ NEVIN J. LIBER ..!ihnp4!ihlpf!nevin1 (312) 510-6194 ' ) ) "The secret compartment of my ring I fill / / _ , __o ____ with an Underdog super-energy pill." / (_