From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=0.8 required=3.0 tests=BAYES_50 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Date: 1 Jul 93 21:43:33 GMT
From: scf16!bashford@ford-wdl1.arpa  (Dave Bashford)
Subject: Re: Ada Operators in 9x
Message-ID: <1993Jul1.214333.17698@scf.loral.com>
List-Id: <comp.lang.ada>

In article ... eachus@spectre.mitre.org (Robert I. Eachus) writes:
>In article ... bwallet@apssgi.nswc.navy.mil (Brad Wallet) writes:
>
>  > no, i think you all are missing point behind making Ada case sensitive.
>  > since the original statement was that case sensitivity would allow for
>  > more uniform coding standards enforcement by the language, i think the
>  > implementation would be something like all reserved words must be
>  > written in lower case and other stuff must be all caps.  that's part of
>  > our coding standards.  this would make perfect sense...
>
>  Gee, since you are too lazy (apparently) to build a tool to enforce
>your coding standards on everyone in the project, you want to require
>all Ada compilers to enforce them on everyone!  That DOES NOT make
>perfect sense to me.
>
>[some CRAZY IDEA about LETTING THE COMPUTER FORMAT CODE AUTOMATICALLY]
>
>     This worked just fine.  The only refinement added later was to
>have a set of "project" preferences for delivered code.

I JUST WANTED TO SAY that I LIKE THE IDEA OF ALL CAPS ON EVERYTHING BUT
keywords.  I AM CONSTANTLY being CONFUSED ABOUT WHETHER A CERTAIN word
IS A keyword OR NOT and IT MAKES SUCH A huge DIFFERENCE TO SOMEONE WHO
IS TRYING TO read Ada^H^H^HADA SOURCE code.  MY keyword QUICK REFERENCE
CARD FOR ADA LISTS ALL 10#63# of THE keywords, BUT IT'S BEGINNING TO
GET WORN OUT FROM USE.

BESIDES, I FEEL LIKE I'M GOING blind SINCE I LEFT VMS, FORTRAN, and BASIC.

(is a flame a flame in a religious discussion ?)
-- 

db
bashford@srs.loral.com (Dave Bashford, Sunnyvale, CA)