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=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,9b17a1f51a26de9d
X-Google-Attributes: gid103376,public
From: "Dr Richard A. O'Keefe" <ok@atlas.otago.ac.nz>
Subject: Re: An array of records within an array of records (Still a problem)
Date: 1998/05/06
Message-ID: <354FB3A5.4522@atlas.otago.ac.nz>#1/1
X-Deja-AN: 350599728
Content-Transfer-Encoding: 7bit
References: <6ifs4p$fl8@lotho.delphi.com> <354DF790.B61E09F7@gsfc.nasa.gov>
Content-Type: text/plain; charset=us-ascii
Organization: Department of Computer Science, University of Otago
Mime-Version: 1.0
Reply-To: ok@atlas.otago.ac.nz
Newsgroups: comp.lang.ada
Date: 1998-05-06T00:00:00+00:00
List-Id: <comp.lang.ada>


Stephen Leake wrote:
> Sorry, I couldn't resist. I use _Type, and I just spent the weekend
> reading the Ada 95 Booch components, which don't.  It was subtly
> frustrating.  It would be nice if we (the Ada community) could agree
> on a consensus for this issue, as we seem to have on the
> Capitalization_Of_Multi_Word_Names issue.

The rule I was taught is a very simple one.  You should name your
types and your variables so that an object declaration like

    Open_Goal_Set: Goal_Set;

can be read aloud as a TRUE and USEFUL sentence, pronouncing the
colon as "is a".  Hence
    Open_Goal_Set is a Goal_Set
works, but
    Open_Goal_Set is a Goal_Set_Type
doesn't work, and
    Open_Goal_Set is a Goal_Sets
_really_ grates.

Note that this _is_ consistent with the names of the Ada built in
types:
    Space: Character;
NOT
    Space: Character_Type;
or  Space: Characters;

Unlike capitalisation, where the case pattern was _defined_ not to
make any difference to the predefined things in the language, we
_can't_ _consistently_ switch to a *_Type or *s convention.