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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII X-Google-Thread: 103376,63a41ccea0fc803a X-Google-Attributes: gid103376,public From: "Jean-Pierre Rosen" Subject: Re: Naming of Tagged Types and Associated Packages Date: 1998/08/04 Message-ID: <6q6h7l$t7l$1@platane.wanadoo.fr>#1/1 X-Deja-AN: 377764118 Content-Transfer-Encoding: 8bit References: <6pdhfo$1br$1@platane.wanadoo.fr> <6pi0pf$df8$1@nnrp1.dejanews.com> <6pirk1$iar$1@nnrp1.dejanews.com> <6pknai$qst$1@nnrp1.dejanews.com> <6pl5rh$elr$1@nnrp1.dejanews.com> <35BF50B4.6FDCDDA0@west.raytheon.com> Content-Type: text/plain; charset="iso-8859-1" X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Organization: Adalog Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1998-08-04T00:00:00+00:00 List-Id: Matthew Heaney a �crit dans le message ... >A package name is not a type name, because a package is not a type. A >package is a namespace, and it exists only (more or less) to prevent >name clashes among identically named types. > This is absolutely true from the point of view of the *language definition*. However, you *use* it to form higher level abstractions. It then becomes that higher level abstraction. For example, a paint is just a chemical product with peculiar optical properties, but when used in a certain way, it becomes the Joconde... A package used in a certain way makes up a class (in classical OO mode). When used otherwise, it may become something else, and I 100% agree that different conventions might then be preferable.