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!news2.google.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post02.iad.highwinds-media.com!news.flashnewsgroups.com-b7.4zTQh5tI3A!not-for-mail From: Stephen Leake 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> <4cd27fb2$0$7658$9b4e6d93@newsspool1.arcor-online.net> Date: Sat, 06 Nov 2010 12:49:13 -0400 Message-ID: <8239re1jp2.fsf@stephe-leake.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (windows-nt) Cancel-Lock: sha1:DxQ2TZ74tUHBI2VbRKNhd55d1K8= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: abuse@flashnewsgroups.com Organization: FlashNewsgroups.com X-Trace: 074a24cd58489e9cdf0b023667 Xref: g2news2.google.com comp.lang.ada:16309 Date: 2010-11-06T12:49:13-04:00 List-Id: Georg Bauhaus writes: > 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? Because when you are writing a general purpose library, there is no specific context. A list package can be used in many different contexts. The package should be named Lists (or Gen_Lists if it is generic), the type should be named Lists.List, the subprogram arguments should be named List. What more is there to say? >> 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. Like I said, not actually solving the problem, only providing for endless discussion. > The programmers or team can pick the one name that matches best. No, they can't, because they won't agree on what is "best", any more than this newsgroup does. -- -- Stephe