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.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,1b41412c7bc28c47 X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local02.nntp.dca.giganews.com!nntp.comcast.com!news.comcast.com.POSTED!not-for-mail NNTP-Posting-Date: Tue, 19 Aug 2008 21:01:44 -0500 From: "Steve" Newsgroups: comp.lang.ada References: <2e9ebb23-a68b-43cf-8871-febcb173f951@56g2000hsm.googlegroups.com> <4899d2af$0$19731$4d3efbfe@news.sover.net> Subject: Re: Suffix _T for types found good Date: Tue, 19 Aug 2008 19:01:45 -0700 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5512 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Message-ID: <9LmdncTBAPGV5jbVnZ2dnUVZ_sTinZ2d@comcast.com> X-Usenet-Provider: http://www.giganews.com NNTP-Posting-Host: 24.20.111.206 X-Trace: sv3-5WNlRhxwuHhYk1FqbOPYzrQxHMsd1HRLzXzt2GSVwSYP4I2ys8rDYOaPA7TQP+9N27gQ+fmqdV+Z/XN!0xc6K7iF+M0FOfulhftVBMq562DS+8ALoNGIpIQvfYiyy2VaBqKpl2vFVhSi31js+fJsj1yA4EK2!mxL5+3AVo8jh1iEuHbf0pg8bJlavBw== X-Complaints-To: abuse@comcast.net X-DMCA-Complaints-To: dmca@comcast.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.39 Xref: g2news1.google.com comp.lang.ada:1661 Date: 2008-08-19T19:01:45-07:00 List-Id: >"Martin" wrote in message >news:efded36d-c0f1-45f9-b1ac->f3575f642ad7@w7g2000hsa.googlegroups.com... [snip] >I've used (and mandated) the "A_"/"An_" prefixes on a few projects and >it does work quite well and read fine. > >I'll put my hand up and admit I _hate_ the noise of "_Type" - it >really ought to be clear and unambiguous from language rules but >isn't. :-( Actually I think it is clear from the language rules, but... When reading source code it is often important to be able to scan through code quickly and comprehend the meaning. Coding conventions can make it quicker to recognize things in without reading the text. For example indenting code uniformly makes it easier to follow. While the format of the code doesn't change its meaning, it can make it considerably easier to read. Regards, Steve >Cheers >-- Martin