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,e55245590c829bef X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news4.google.com!feeder.news-service.com!kanaga.switch.ch!news-zh.switch.ch!switch.ch!newsfeed-0.progon.net!progon.net!newsfeed.ision.net!newsfeed2.easynews.net!ision!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Thu, 04 Nov 2010 10:41:06 +0100 From: Georg Bauhaus User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Beginners question: Compound types, how-to? References: <86wroy58ff.fsf@gareth.avalon.lan> <86pqup5xfy.fsf@gareth.avalon.lan> <86y69d3rec.fsf@gareth.avalon.lan> <4cd19583$0$6977$9b4e6d93@newsspool4.arcor-online.net> <82oca54q8a.fsf@stephe-leake.org> In-Reply-To: <82oca54q8a.fsf@stephe-leake.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <4cd27fb2$0$7658$9b4e6d93@newsspool1.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 04 Nov 2010 10:41:06 CET NNTP-Posting-Host: 2cc5a0cd.newsspool1.arcor-online.net X-Trace: DXC=FQ=330`>UAZmG86`U=_nC_ic==]BZ:af^4Fo<]lROoRQ<`=YMgDjhgRI3?B2M?cZ7WPCY\c7>ejVXQQfIKUEA2ZW7E85IXfTEZV X-Complaints-To: usenet-abuse@arcor.de Xref: g2news2.google.com comp.lang.ada:16177 Date: 2010-11-04T10:41:06+01:00 List-Id: On 11/4/10 6:23 AM, Stephen Leake wrote: Why is it that the "_type" camp is so consistently silent about giving specific contexts of what are just programming examples? > Notice that the "find a better name" camp always suggests _several_ > names, and each person suggests _different_ ones. That means there is no > common solution, and the resulting code will be confusing, and subject > to endless arguments about "the right name" in code reviews. The "find a better name" camp only suggests several names in order to offer ideas, as best as they can not knowing the context like the programmers do---or are supposed to do. The programmers or team can pick the one name that matches best. Only they have enough domain knowledge to choose properly.