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=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED.3d73Ybk3C5U4I2t8lv+lAQ.user.gioia.aioe.org!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Type naming conventions: Any_Foo Date: Thu, 5 Dec 2019 18:45:05 +0100 Organization: Aioe.org NNTP Server Message-ID: References: NNTP-Posting-Host: 3d73Ybk3C5U4I2t8lv+lAQ.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 X-Notice: Filtered by postfilter v. 0.9.2 Content-Language: en-US Xref: reader01.eternal-september.org comp.lang.ada:57658 Date: 2019-12-05T18:45:05+01:00 List-Id: On 2019-12-05 18:27, Jeffrey R. Carter wrote: > I would even say that those who use naming conventions such as > _T[y[p[e]]] are either not S/W engineers or are shirking their duties. There exist cases: 1. Formal generic types. They are customarily named XXX_Type. 2. Types which are artifacts of language issues or of design. These have no separate problem space meaning and thus no meaningful name. E.g. type Something is ...; type Something_Ptr is access Something; -- I don't want access type, I am required to have it BTW, this includes all sorts of helper types Ada kept introducing recently. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de