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.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,c39ad3e35a7690a9 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Received: by 10.68.238.198 with SMTP id vm6mr9721813pbc.3.1329138085558; Mon, 13 Feb 2012 05:01:25 -0800 (PST) Path: wr5ni20060pbc.0!nntp.google.com!news1.google.com!eweka.nl!lightspeed.eweka.nl!feeder.erje.net!news.mixmin.net!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Convention for naming of packages Date: Mon, 13 Feb 2012 14:01:16 +0100 Organization: cbb software GmbH Message-ID: References: <4f355230$0$21451$ba4acef3@reader.news.orange.fr> <1sx3fy79wys5s.1723nejowbg76.dlg@40tude.net> <15fgcngmgl41e$.113i7gtuwpwpv$.dlg@40tude.net> Reply-To: mailbox@dmitry-kazakov.de NNTP-Posting-Host: FbOMkhMtVLVmu7IwBnt1tw.user.speranza.aioe.org Mime-Version: 1.0 X-Complaints-To: abuse@aioe.org User-Agent: 40tude_Dialog/2.0.15.1 X-Notice: Filtered by postfilter v. 0.8.2 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Date: 2012-02-13T14:01:16+01:00 List-Id: On Mon, 13 Feb 2012 12:57:48 +0100, Yannick Duch�ne (Hibou57) wrote: > Le Mon, 13 Feb 2012 12:03:05 +0100, Dmitry A. Kazakov > a �crit: >> 1. If you could meaningfully rename it afterwards, why would not you name >> it properly at the original declaration point? > The context is then not the same. > > The most trivial example comes with Instance_Type. That's not the same > when it stands for the main type of a package and when it is used along > with many other types. Can be compared with generics in some way. This is a good example of a bad name, which tells nothing about the thing. Of course it is legitimate to use one bad name in place of other bad name. > When something is named after its role, then the context matters, and the > name may change with the context. No. The user's context cannot matter to the role, as it contradicts to all principles of reuse, information hiding and good design. Even less the declaration context is appropriate to influence the name. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de