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: a07f3367d7,25d835bb9a4a003f X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news2.google.com!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.earthlink.com!news.earthlink.com.POSTED!not-for-mail NNTP-Posting-Date: Thu, 05 Nov 2009 14:18:55 -0600 From: "Vincent Marciante" Newsgroups: comp.lang.ada References: <561e0a4a-c6c0-42db-9f31-a70f4eae1ed9@a21g2000yqc.googlegroups.com> Subject: Re: Types, packages & objects : the good old naming conventions question (without religious ware) Date: Thu, 5 Nov 2009 15:18:16 -0500 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5843 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Message-ID: X-Usenet-Provider: http://www.giganews.com NNTP-Posting-Host: 75.99.9.146 X-Trace: sv3-GqDPgJjaCiBeFjZgy3Tb+UbKgTbNz8vnAbA4Z/S/ilrP0FSgOpJG1IfrxrsybaiNzh9GcIsq/7ypqSc!9Xe0OyA09gtJia0x2MIvuc/aM8G5RRmponA37E3mCM5wiZ8gcE5wRm2i2DhWEz4d1Ipzgz2ptH/9!d1+lie/UFaE6dVyRbgiwUxFrvYDFJoc= 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.40 Xref: g2news2.google.com comp.lang.ada:9006 Date: 2009-11-05T15:18:16-05:00 List-Id: "Stephen Leake" wrote in message news:u1vkdrert.fsf@stephe-leake.org... > "Peter C. Chapin" writes: > >> Stephen Leake wrote in >> news:u4ope4pqa.fsf@stephe-leake.org: >> >>> Yes, but reading is also important. The _Type suffix is essentially >>> noise when reading; it's only there for the compiler, not the human. >>> So you want to read it as few times as possible, as well as write it >>> as few times as possible. >> >> This seems backwards to me. I could use a type name such as X72efY9 for >> all >> the compiler cares. The _Type suffix is most definitely for the human. It >> says, "Hey! This is the name of a type so keep that in mind when looking >> at >> this code." > > Well, you can read it that way. But the original reason the _Type > convention got started (at least, as far as I'm concerned) is to solve > the problem of overlapping object and type namespaces. > > This is illegal: > > procedure (List : in list); > > So we have to add noise to either the object or the type, to keep the > compiler happy. That's all there is to it. That is not necessary: package sdgfkjasf is -- or whayever type List is ... procedure jsdfks (List : sdgfkjasf.List); ... >> In the past I used _Type as a suffix for all of my types. However, there >> are times when that doesn't seem to fit. After all the standard types >> don't >> (usually) use a _Type suffix (Character, Integer, Positive, Vector, etc). > > The standard is Just Wrong. But we have to live with it. > > -- > -- Stephe Vinny