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 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,60d761814c33393c
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-06-10 12:09:49 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!arclight.uoregon.edu!wn13feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!sccrnsc04.POSTED!not-for-mail
From: tmoran@acm.org
Newsgroups: comp.lang.ada
Subject: Re: Qs re 'Write & 'Read
References: <vec6t08neudvea@corp.supernews.com>
X-Newsreader: Tom's custom newsreader
Message-ID: <02qFa.1186062$F1.140501@sccrnsc04>
NNTP-Posting-Host: 12.234.13.56
X-Complaints-To: abuse@attbi.com
X-Trace: sccrnsc04 1055272188 12.234.13.56 (Tue, 10 Jun 2003 19:09:48 GMT)
NNTP-Posting-Date: Tue, 10 Jun 2003 19:09:48 GMT
Organization: AT&T Broadband
Date: Tue, 10 Jun 2003 19:09:48 GMT
Xref: archiver1.google.com comp.lang.ada:38927
Date: 2003-06-10T19:09:48+00:00
List-Id: <comp.lang.ada>

>the string itself is preceded by its contstraint, access types are written
>to the stream with a boolean value preceding the data (if any).
  Sounds right.

>It surely seemed to me like the language standard could have defined
>something like this as the default for access types, but alas, it did not.
  I can see there would be difficulties for general access types, but
heap access types seem easy enough.  Unless storage pools cause
difficulties.