Path: utzoo!mnetor!uunet!husc6!sri-unix!quintus!ok
From: ok@quintus.UUCP (Richard A. O'Keefe)
Newsgroups: comp.lang.misc
Subject: Re: case sensitivity
Message-ID: <791@cresswell.quintus.UUCP>
Date: 21 Mar 88 08:45:57 GMT
References: <2318@bsu-cs.UUCP> <2400010@otter.hple.hp.com> <4049@ihlpf.ATT.COM>
Organization: Quintus Computer Systems, Mountain View, CA
Lines: 16

In article <4049@ihlpf.ATT.COM>, nevin1@ihlpf.ATT.COM (00704a-Liber) writes:
: 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??

Comment:  Euclid already does this.
Comment:  Some Xerox file-systems retain the case specified when a file was
	  created but accept either case when a file is looked up; attempting
	  to create another file with the same name but different case pattern
	  can warn you of the existing file.