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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: Victor Porton Newsgroups: comp.lang.ada Subject: Re: Intermixing two tagged types Date: Thu, 14 Aug 2014 14:57:18 +0300 Organization: Aioe.org NNTP Server Message-ID: References: NNTP-Posting-Host: AnnUDmZwVERVUXyHDyOl5A.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: abuse@aioe.org User-Agent: KNode/4.12.4 X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:21751 Date: 2014-08-14T14:57:18+03:00 List-Id: Simon Wright wrote: > Victor Porton writes: > >> So (now in Ada terms, which I am implementing) a function can belong >> to two tagged types. > > Are you sure that it's appropriate to use *tagged* types? And even if if > is appropriate for raptor_namespace (i.e., you derive new types from > it), is it so for raptor_namespace_stack? - which clearly is a stack of > raptor_namespace (or possibly raptor_namespace'Class). Tagged types a little decrease efficiency, but I use tagged types anyway (primarily for controlled finalization). -- Victor Porton - http://portonvictor.org