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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,1b41412c7bc28c47 X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Path: g2news1.google.com!news2.google.com!postnews.google.com!c58g2000hsc.googlegroups.com!not-for-mail From: amado.alves@gmail.com Newsgroups: comp.lang.ada Subject: Re: Suffix _T for types found good Date: Thu, 7 Aug 2008 05:37:12 -0700 (PDT) Organization: http://groups.google.com Message-ID: References: <2e9ebb23-a68b-43cf-8871-febcb173f951@56g2000hsm.googlegroups.com> <188191be-d2c6-4d94-8d6b-082015954332@t54g2000hsg.googlegroups.com> <489A0440.9080201@obry.net> <594cdbb8-4018-44bd-a8db-0df3f23df247@z72g2000hsb.googlegroups.com> <489aa138$0$20716$9b4e6d93@newsspool4.arcor-online.net> <489aca09$0$12946$9b4e6d93@newsspool2.arcor-online.net> NNTP-Posting-Host: 92.250.122.24 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1218112633 382 127.0.0.1 (7 Aug 2008 12:37:13 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Thu, 7 Aug 2008 12:37:13 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: c58g2000hsc.googlegroups.com; posting-host=92.250.122.24; posting-account=3cDqWgoAAAAZXc8D3pDqwa77IryJ2nnY User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.0.04506; .NET CLR 1.1.4322),gzip(gfe),gzip(gfe) Xref: g2news1.google.com comp.lang.ada:1503 Date: 2008-08-07T05:37:12-07:00 List-Id: > =A0 =A0 Cam_Corder: Input_Stream; > =A0 =A0 Null_Device: Output_Stream; When obvious different names exist this is fine. This concerns only one adavantage of _T, automatic different names. The suffix helps here in other cases, which seem to pop up often too. And then for uniformity we append _T to all. It does not exclude proper naming. Cam_Corder: Input_Stream_T; Null_Device: Output_Stream_T; And then there are the other advantages (see passim).