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,LOTS_OF_MONEY 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 02:53:52 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: martin.dowie@btopenworld.com (Martin Dowie) Newsgroups: comp.lang.ada Subject: Re: Case sensitivity (was Re: no title) Date: 3 Jun 2003 02:53:51 -0700 Organization: http://groups.google.com/ Message-ID: References: NNTP-Posting-Host: 20.138.254.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1054634032 32632 127.0.0.1 (3 Jun 2003 09:53:52 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 3 Jun 2003 09:53:52 GMT Xref: archiver1.google.com comp.lang.ada:38449 Date: 2003-06-03T09:53:52+00:00 List-Id: "Steve" wrote in message news:... > IMHO, case sensitivity does not ensure consistency of names. It permits you > to have Text_IO, Text_Io, text_io and TEXT_IO in the same program, that all > do different things (Yuk!). Having seen this sort of thing in some C code, > I think it's a very bad thing and does do harm. > > Now if you want to add a compiler switch that warns if the same identifier > appears in different places with different casing... I think that is a good > idea. Maybe a smart IDE could even pop-up a list of casings for the same > identifier and let you choose the "right" one. Just use a Pretty-Printer! Make it part of your config control process that before checking anything in it is passed through the PP. This should be enough to keep all you code consistent.