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 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,997e6472f58cc955
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-06-04 18:27:16 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!wn14feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi_feed4!attbi.com!sccrnsc02.POSTED!not-for-mail
Message-ID: <3EDE9C4D.7000708@attbi.com>
From: "Robert I. Eachus" <rieachus@attbi.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Case dependence and coding standards
References: <035odv8mfiksmqo69q0250qp141oebtdro@4ax.com>
 <wccr86bjcdw.fsf@shell01.TheWorld.com>
 <bbin05$9onrq$2@ID-175126.news.dfncis.de>
 <wccu1b7yod6.fsf@shell01.TheWorld.com>
 <bbkba3$aatu7$1@ID-175126.news.dfncis.de> <uisrlx0p6.fsf@nasa.gov>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 24.62.164.137
X-Complaints-To: abuse@attbi.com
X-Trace: sccrnsc02 1054776435 24.62.164.137 (Thu, 05 Jun 2003 01:27:15 GMT)
NNTP-Posting-Date: Thu, 05 Jun 2003 01:27:15 GMT
Organization: AT&T Broadband
Date: Thu, 05 Jun 2003 01:27:15 GMT
Xref: archiver1.google.com comp.lang.ada:38652
Date: 2003-06-05T01:27:15+00:00
List-Id: <comp.lang.ada>

Stephen Leake wrote:

> I disagree. The compiler enforces capitalization, in the same way it
> enforces syntax rules. I'm trading brain cycles for CPU cycles, and I
> see a net gain. Since I now have more brain cycles available, dirty
> hacks are less likely.

Personally, I am comfortable with using "pretty printers" through some 
stage of the procedings, and from then on I do like the GNAT behavior of 
treating capitalization errors as errors.  They are, but the compiler 
can't be sure what the error is, just that there is one.  So it 
shouldn't "fix" it silently.  As I said, beyond a certain point I want 
to control all changes to the code myself.