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-7-bit
X-Google-Thread: 103376,63a41ccea0fc803a
X-Google-Attributes: gid103376,public
From: eachus@spectre.mitre.org (Robert I. Eachus)
Subject: Re: Naming of Tagged Types and Associated Packages
Date: 1998/07/29
Message-ID: <EACHUS.98Jul29172330@spectre.mitre.org>#1/1
X-Deja-AN: 376129228
References: <ur9zlv6tx.fsf@sandia.SPAMFREE.gov>
 <m34sw6mcbx.fsf@mheaney.ni.net> <6pdhfo$1br$1@platane.wanadoo.fr>
 <m367gl943o.fsf@mheaney.ni.net> <6pi71p$n90$1@platane.wanadoo.fr>
Organization: The Mitre Corp., Bedford, MA.
Newsgroups: comp.lang.ada
Date: 1998-07-29T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <6pi71p$n90$1@platane.wanadoo.fr> "Jean-Pierre Rosen" <rosen.adalog@wanadoo.fr> writes:

 > The trouble is that when you instantiate the generic, you can choose the
 > name of the new package, but not the names of what is declared inside, and
 > especially the type. I you want the type name to carry the useful
 > information, the type name should change with each instantiation! With my
 > notation, the package name carries the useful information, and therefore the
 > same convention can be used for packages obtained by generic instantiations
 > and for regular packages.

   Ah, but I always find myself doing the following:

   package Foobar is new Foo(....);
   type Something_Meaningful is new Foobar.Object_Type with null;
   -- and possibly
   function My_Op(Param: Something_Meaningful) return Integer;

   So both the use clause issue, and the meaningful name issue go away.
--

					Robert I. Eachus

with Standard_Disclaimer;
use  Standard_Disclaimer;
function Message (Text: in Clever_Ideas) return Better_Ideas is...