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,34d47d048b177d0b
X-Google-Attributes: gid103376,public
From: tmoran@bix.com (Tom Moran)
Subject: Re: limited/non-limited in Ada95
Date: 1997/10/21
Message-ID: <344ccece.1720086@SantaClara01.news.InterNex.Net>#1/1
X-Deja-AN: 282219565
References: <3442C2A3.3781@bix.com>
 <mheaney-ya023680001610972221540001@news.ni.net>
 <ufhgaghueo.fsf@synquiry.com>
 <3449390f.142507@SantaClara01.news.InterNex.Net>
 <mheaney-ya023680001810971645020001@news.ni.net>
 <344a4329.812635@SantaClara01.news.InterNex.Net>
 <mheaney-ya023680001910971304190001@news.ni.net>
Organization: InterNex Information Services 1-800-595-3333
Newsgroups: comp.lang.ada
Date: 1997-10-21T00:00:00+00:00
List-Id: <comp.lang.ada>


>>Another problem is that once a tagged type is non-limited, no
>>extension can be, or have components that are,llimited.

>Yes, that's true.  But you could always add a discriminant of a named
>access type to the derived type, to point to objects that are limited.
  Using a (named)access type instead of the limited object directly is
ugly, increases code size and complexity, is error prone, and
expensive (eg on Windows CE where they tell you to avoid memory
allocation/deallocation as much as possible) .  Other than that, it's
just fine. :(