From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,8d472879e3f609e0
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-06-08 20:02:53 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!small1.nntp.aus1.giganews.com!nntp.giganews.com!nntp3.aus1.giganews.com!nntp.gbronline.com!news.gbronline.com.POSTED!not-for-mail
NNTP-Posting-Date: Sun, 08 Jun 2003 22:02:49 -0500
Date: Sun, 08 Jun 2003 22:03:20 -0500
From: Wesley Groleau <wesgroleau@despammed.com>
Reply-To: wesgroleau@despammed.com
Organization: Ain't no organization here!
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
 rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en, es-mx, pt-br, fr-ca
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Case sensitivity (was Re: no title)
References: <mailman.8.1054540581.12990.comp.lang.ada@ada.eu.org>
 <slrnbdm1i7.1k5.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <bbf9kl$7kt$1@ns.felk.cvut.cz> <ZXTCa.1089424$F1.129227@sccrnsc04>
 <0vGdnQFmVPoZj0Gj4p2dnA@gbronline.com>
 <gNUCa.41201$fT5.2098@nwrdny01.gnilink.net>
 <slrnbdp2bt.1lk.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <1054647054.761122@master.nyc.kbcfp.com>
 <slrnbdpc43.87p.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <1054651042.211055@master.nyc.kbcfp.com>
 <slrnbdpdfj.87p.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <1054652619.86785@master.nyc.kbcfp.com>
 <h4AEa.15891$JA5.306769@news.xtra.co.nz>
 <WJAEa.46002$ca5.5643@nwrdny02.gnilink.net>
 <coCEa.16092$JA5.308770@news.xtra.co.nz>
 <hzDEa.17603$b8.11964@nwrdny03.gnilink.net>
In-Reply-To: <hzDEa.17603$b8.11964@nwrdny03.gnilink.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <6yadnQol9JdHZX6jXTWcow@gbronline.com>
NNTP-Posting-Host: 216.117.18.20
X-Trace: 
 sv3-2us/wEq7nm5p3wwOVGm/1a91YLVRK4/ErDXfCvDeTgdiBP5OYgOL8UkUcJBGLQeWCiMoQ91OGVUWMJa!2+qhD38OddIChgkC/y5opQUG/MxBWkhbbnEu+zQeNCFNbIln4VvZMj4q2UWPEOgUrK+K4cjy9DHh!7mBF
X-Complaints-To: abuse@gbronline.com
X-DMCA-Complaints-To: abuse@gbronline.com
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint
 properly
X-Postfilter: 1.1
Xref: archiver1.google.com comp.lang.ada:38840
Date: 2003-06-08T22:03:20-05:00
List-Id: <comp.lang.ada>


> We've seen sevral examples of code which benefits from
> case sensitivity (that is, it's used to good effect).
> One was "FILE *file", another was enumerators which were

One could argue that in this example, the code did _not_
benefit.  Perhaps if the language were case insensitive
the programmer would have put some thought into selecting
names that told more about what was happening.

Then again, maybe that wouldn't have been the case.

Can either side come up with one real-world incident
where an error occurred that would have been prevented
by case-sensitivity or by case-insensitivity?