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: a07f3367d7,25d835bb9a4a003f X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!postnews.google.com!k19g2000yqc.googlegroups.com!not-for-mail From: =?ISO-8859-1?Q?Hibou57_=28Yannick_Duch=EAne=29?= Newsgroups: comp.lang.ada Subject: Re: Types, packages & objects : the good old naming conventions question (without religious ware) Date: Tue, 29 Dec 2009 15:27:04 -0800 (PST) Organization: http://groups.google.com Message-ID: <0ef44c2d-3848-4780-8663-f5f96efc7638@k19g2000yqc.googlegroups.com> References: <561e0a4a-c6c0-42db-9f31-a70f4eae1ed9@a21g2000yqc.googlegroups.com> <-9ydneBa_O8wB2TXnZ2dnUVZ_tadnZ2d@earthlink.com> NNTP-Posting-Host: 86.75.149.146 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: posting.google.com 1262129224 8524 127.0.0.1 (29 Dec 2009 23:27:04 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Tue, 29 Dec 2009 23:27:04 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: k19g2000yqc.googlegroups.com; posting-host=86.75.149.146; posting-account=vrfdLAoAAAAauX_3XwyXEwXCWN3A1l8D User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; fr),gzip(gfe),gzip(gfe) Xref: g2news1.google.com comp.lang.ada:8549 Date: 2009-12-29T15:27:04-08:00 List-Id: Do not remember if it was already previously suggested in this discussion : it appears to me a naming convention for tagged types is helpful to better understand an implementation. I already use _Class and _Class_Access (although I would enjoy a shorter one for this one) postfix for class-wide types and class-wide access, now I feel the _Type postfix is not enough. Types and tagged types should be distinguishable at first sight as well. By the way, I was thinking this may be an idea to think about in future days, to add to the now widely used syntax colorization, a step forward : semantic colorization (may be with font variants).