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,LOTS_OF_MONEY 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 14:30:50 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!sn-xit-03!sn-xit-01!sn-post-01!supernews.com!corp.supernews.com!not-for-mail From: "David C. Hoos" Newsgroups: comp.lang.ada Subject: Re: Qs re 'Write & 'Read Date: Tue, 10 Jun 2003 16:30:46 -0500 Organization: Posted via Supernews, http://www.supernews.com Message-ID: References: <02qFa.1186062$F1.140501@sccrnsc04> X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Complaints-To: abuse@supernews.com Xref: archiver1.google.com comp.lang.ada:38937 Date: 2003-06-10T16:30:46-05:00 List-Id: wrote in message news:02qFa.1186062$F1.140501@sccrnsc04... > >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. Maybe my mind's just in a fog today, but please explain why there'd be a problem with any kind of access type -- general, or not, using my approach. > _______________________________________________ > comp.lang.ada mailing list > comp.lang.ada@ada.eu.org > http://ada.eu.org/mailman/listinfo/comp.lang.ada >