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-03 08:32:01 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!nntp4.savvis.net!uunet!dfw.uu.net!dca.uu.net!ash.uu.net!spool0901.news.uu.net!spool0902.news.uu.net!not-for-mail Date: Tue, 03 Jun 2003 11:31:24 -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: <0vGdnQFmVPoZj0Gj4p2dnA@gbronline.com> <1054647054.761122@master.nyc.kbcfp.com> <1054651042.211055@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: <1054654285.466839@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: 1054654286 7427 204.253.250.10 Xref: archiver1.google.com comp.lang.ada:38502 Date: 2003-06-03T11:31:24-04:00 List-Id: John R. Strohm wrote: > Making the language case-insensitive fixes that problem, > by preventing it from ever occurring. You might be right if the language were case-insensitive, but it isn't. Character and string literals are sensitive to case. It's only identifiers which ignore case. So your hypothetical mainframe environment couldn't handle Put("Hello, world!"); And speaking of such primitive environments, I started programming in college on a very early UNIX system on a PDP-11 using uppercase-only terminals that used rolls of paper, not display screens. The drivers translated all input to lower case internally, and if you wanted upper case, you escaped the letter with a backslash. The system would then print such actual upper case letters with a backslash prefix. So it was certainly possible to use mixed case even on such a platform.