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-Thread: 103376,3ae40b42b99b8123
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!postnews.google.com!d12g2000vbz.googlegroups.com!not-for-mail
From: AdaMagica <christoph.grein@eurocopter.com>
Newsgroups: comp.lang.ada
Subject: Re: Little tutorial about streams
Date: Tue, 1 Mar 2011 01:54:12 -0800 (PST)
Organization: http://groups.google.com
Message-ID: 
 <3f9d3d5b-e51e-4fd2-ad8c-bd41296918ef@d12g2000vbz.googlegroups.com>
References: 
 <f8e7ccbf-a966-4568-9f0d-8e9e38f37dc6@glegroupsg2000goo.googlegroups.com>
 <ikhqa5$7tr$1@munin.nbi.dk>
NNTP-Posting-Host: 80.156.44.178
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
X-Trace: posting.google.com 1298973252 11190 127.0.0.1 (1 Mar 2011 09:54:12
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Tue, 1 Mar 2011 09:54:12 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: d12g2000vbz.googlegroups.com; posting-host=80.156.44.178;
 posting-account=rmHyLAoAAADSQmMWJF0a_815Fdd96RDf
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.2; de; rv:1.9.0.4)
 Gecko/2008102920 Firefox/3.0.4,gzip(gfe)
Xref: g2news1.google.com comp.lang.ada:17672
Date: 2011-03-01T01:54:12-08:00
List-Id: <comp.lang.ada>

On 1 Mrz., 04:48, "Randy Brukardt" <ra...@rrsoftware.com> wrote:
> The little table under "Serialization functions" seems confusing, since it
> uses "composite" for Input and Output. But of course you can use Read and
> Write for "composite" types. It seems the intent is to be more informal
> (since "simple" is used rather than "elementary", which is good as there are
> no elementary class-wide types); may I suggest that the other entries use
> "complex" rather than "composite"? (Or some word meaning the same, if the
> confusion with "complex" numbers is a concern.)

I would propose "definite" for "simple" and "indefinite" for
"composed".

For definite types, the bounds and discriminants are known, so need
not be put on the stream (Read/Write).

For indefinite types, the bounds and discriminants are needed to
construct the object, so they have to be put into the stream (Input/
Output).