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 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!news4.google.com!news2.google.com!news1.google.com!newshub.sdsu.edu!flpi089.ffdc.sbc.com!prodigy.net!flpi088.ffdc.sbc.com!prodigy.com!flpi107.ffdc.sbc.com!nlpi065.nbdc.sbc.com.POSTED!cfe18fef!not-for-mail From: Gary Scott Organization: Home User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Suffix _T for types found good References: <2e9ebb23-a68b-43cf-8871-febcb173f951@56g2000hsm.googlegroups.com> <4899d2af$0$19731$4d3efbfe@news.sover.net> <9LmdncTBAPGV5jbVnZ2dnUVZ_sTinZ2d@comcast.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <3%Wqk.17251$LG4.5286@nlpi065.nbdc.sbc.com> NNTP-Posting-Host: 68.94.37.188 X-Complaints-To: abuse@prodigy.net X-Trace: nlpi065.nbdc.sbc.com 1219247167 ST000 68.94.37.188 (Wed, 20 Aug 2008 11:46:07 EDT) NNTP-Posting-Date: Wed, 20 Aug 2008 11:46:07 EDT X-UserInfo1: FKPO@MC@@S@]RV@[WBHB^WHAAJYFBL@MAHU^_BAMEH]TCDYG^WHEAE[YETZPIWWI[FCIZA^NBFXZ_D[BFNTCNVPDTNTKHWXKB@X^B_OCJLPZ@ET_O[G\XSG@E\G[ZKVLBL^CJINM@I_KVIOR\T_M_AW_M[_BWU_HFA_]@A_A^SGFAUDE_DFTMQPFWVW[QPJN Date: Wed, 20 Aug 2008 10:46:03 -0500 Xref: g2news1.google.com comp.lang.ada:1685 Date: 2008-08-20T10:46:03-05:00 List-Id: Stephen Leake wrote: > "Steve" writes: > > >>>"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... > > > Huh? The problem is that the language rules forbid this: > > Buffer : Buffer; > > That is what we would _like_ the language to allow. what? that looks completely ambiguous in terms of readability. you must know some arcane rule to interpret it. > > >>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. > > > So can clear language rules! If we assume that the reader _fully_ > understands the language, extra noise like "_Type" or "A_" just get in > the way. > > Fortunately, the human mind/brain is good at filtering out such noise, > as long as it is present consistently. > > If we try to right Ada code so someone who understands only some > C-like language can read it, then coding conventions might help. I > avoid doing that; one of my goals is to stamp out C coding :). > > >>For example indenting code uniformly makes it easier to follow. > > > That's true, independent of language rules. > -- Gary Scott mailto:garylscott@sbcglobal dot net Fortran Library: http://www.fortranlib.com Support the Original G95 Project: http://www.g95.org -OR- Support the GNU GFortran Project: http://gcc.gnu.org/fortran/index.html If you want to do the impossible, don't hire an expert because he knows it can't be done. -- Henry Ford