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,2afac1a4161c7f35 X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Distinguishing type names from other identifiers Date: 1998/01/16 Message-ID: #1/1 X-Deja-AN: 316705214 References: <884736089.2104295427@dejanews.com> <69lael$90o@top.mitre.org> <01bd2207$18f3fac0$95fc82c1@xhv46.dial.pipex.com> <69nt40$q7n@top.mitre.org> X-Complaints-To: usenet@news.nyu.edu X-Trace: news.nyu.edu 884998828 23008 (None) 128.122.140.58 Organization: New York University Newsgroups: comp.lang.ada Date: 1998-01-16T00:00:00+00:00 List-Id: Note as an interesting postscript to this discussion of enforced coding styles, that a very common request for enhancement of GNAT is an official feature similar to -gnatg. Indeed, quite a few of our customers are using -gnatg even though we advise against it (we advise against it, becuase (a) it makes the compiler non-standard, e.g. allowing compilation of new children of Ada and (b) we feel free to change this at any time, typically by adding new requirementsw which you might or might not like)). We definitely plan some limited capability of this type for style enforcement available as a user capability in the future. Note that you can also use external tools, such as AdaAssured to do this kind of style checking.