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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,768ec7d79291ed2c
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: IDENTIFIERS in Upper Case
Date: 1997/03/28
Message-ID: <dewar.859561259@merv>#1/1
X-Deja-AN: 229120611
References: <1997Mar26.185431.12742@nosc.mil>
 <collins-2703970617290001@ratbert.cs.wm.edu> <5hfd5b$4ro$1@news.pacifier.com>
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1997-03-28T00:00:00+00:00
List-Id: <comp.lang.ada>


iBy the way Steve, here is what GNAT gives for your little example:

     1. PROCEDURE Doiel IS
     2. BEGIN
     3.   IF a < b THEN
     4.     DoProc1( arg )
                          |
        >>> missing ";"

     5.   ELBE
          |
        >>> incorrect spelling of keyword "ELSE"

     6.     DoProc2( arg )
                          |
        >>> missing ";"

     7.   END IF;
     8. END;


(Hmm! I guess your great capitalization style did not let you notice
the missing semicolons :-) I wonder if that is because the upper case
keywords distracted you? :-)

Note that GNAT does not discriminate, its error circuits work better 9if
you use a consistent style -- any of the style commonly used, including
Steve's are fine, but it learns your style from the program, and uses
this style for both error messages and error recovery (notice the
upper case ELSE in the error message).