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,9b17a1f51a26de9d X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: An array of records within an array of records (Still a problem) Date: 1998/05/06 Message-ID: #1/1 X-Deja-AN: 350760484 References: <6ifs4p$fl8@lotho.delphi.com> <354DF790.B61E09F7@gsfc.nasa.gov> <354FB3A5.4522@atlas.otago.ac.nz> X-Complaints-To: usenet@news.nyu.edu X-Trace: news.nyu.edu 894459423 15878 (None) 128.122.140.58 Organization: New York University Newsgroups: comp.lang.ada Date: 1998-05-06T00:00:00+00:00 List-Id: Stephen said <<> 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. >> Uniformity might be desirable here, but clearly the rule cannot be to add _Type to every type (a real noise generator in my opinion), since clearly this is not the style of the existing language design, which defines many types. The style in the RM (which I assume you also find subtly frustating) is to use nouns as type names, so that something "is a" String or Integer or Unbounded_String or whatever. Of course there are some cases where Type is used (File_Type), so I would gather that the consensus from the RM is to use one of these two styles depending on what is clearer. Sounds good to me! It's certainly the approach I use. Of course you have to be tuned in to the criterion of how to make his this choice. I guess I must be, because I find the RM quite clear and not frustrating, and I like its decisions on when to use Type and when not to!