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=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham 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-04 10:30:58 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!headwall.stanford.edu!newshub.sdsu.edu!elnk-nf2-pas!newsfeed.earthlink.net!in.100proofnews.com!in.100proofnews.com!news.stealth.net news.stealth.net!news.stealth.net!newshosting.com!news-xfer1.atl.newshosting.com!uunet!dca.uu.net!ash.uu.net!spool0901.news.uu.net!spool0902.news.uu.net!not-for-mail Date: Wed, 04 Jun 2003 13:30:15 -0400 From: Hyman Rosen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030529 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Case sensitivity (was Re: no title) References: <20619edc.0306021018.6ee4dd09@posting.google.com> <1054649187.11497@master.nyc.kbcfp.com> <20619edc.0306031034.6a2f5f25@posting.google.com> <1054666439.685312@master.nyc.kbcfp.com> <1054735867.264510@master.nyc.kbcfp.com> <1054742601.548195@master.nyc.kbcfp.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Organization: KBC Financial Products Message-ID: <1054747823.316857@master.nyc.kbcfp.com> Cache-Post-Path: master.nyc.kbcfp.com!unknown@nightcrawler.nyc.kbcfp.com X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/) NNTP-Posting-Host: 204.253.250.10 X-Trace: 1054747824 13762 204.253.250.10 Xref: archiver1.google.com comp.lang.ada:38625 Date: 2003-06-04T13:30:15-04:00 List-Id: Preben Randhol wrote: >>How does case sensitivity increase bugs? > If you read previous posts you will see. OK, I went back and read the previous posts. I found exactly one post, by Booby D. Bryant, who claimed that "a large proportion of the bugs I've fixed in my whole life were the result of people using identifiers with the wrong case". There were no examples, so it's hard to evaluate how typical this might be. Then there was one post by you, giving an example of how you might call the wrong routine if two different packages had a method with the same spelling but different case, and the same argument types, whereas currently, you would be required to disambiguate by specifying the package name. I find that less than compelling as well - what prevents you from specifying the wrong package, after all? >>If two names differ only in case, >>and, say, one names a type and the other an object, > > No, no and. They differ only in case, what then? Then you have to know which one you want, and use it. If you have objects named L00P and LOOP, you are in the same position. But it's an odd situation to have things of the same sort that differ only in case. It's very seldom that I see anything like that, and I program mostly in case sensitive languages.