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.2 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	FROM_STARTS_WITH_NUMS autolearn=no autolearn_force=no version=3.4.4
X-Received: by 10.107.201.195 with SMTP id z186mr4667545iof.129.1519301727388;
        Thu, 22 Feb 2018 04:15:27 -0800 (PST)
X-Received: by 10.157.113.143 with SMTP id o15mr314296otj.6.1519301727150;
 Thu, 22 Feb 2018 04:15:27 -0800 (PST)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!weretis.net!feeder4.news.weretis.net!news.roellig-ltd.de!open-news-network.org!peer01.am4!peer.am4.highwinds-media.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!w142no199515ita.0!news-out.google.com!10ni400ite.0!nntp.google.com!w142no199513ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Thu, 22 Feb 2018 04:15:26 -0800 (PST)
In-Reply-To: <503e3322-ee8e-4d6f-9aa5-e7b98f87e8f8@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=85.240.212.129;
 posting-account=rhqvKAoAAABpikMmPHJSZh4400BboHwT
NNTP-Posting-Host: 85.240.212.129
References: <503e3322-ee8e-4d6f-9aa5-e7b98f87e8f8@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <5d8580c2-b43d-4b2c-8a46-3a6ed33967aa@googlegroups.com>
Subject: Re: article on acces types and dynamic serialization in Ada (2003)
From: Mehdi Saada <00120260a@gmail.com>
Injection-Date: Thu, 22 Feb 2018 12:15:27 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Body-CRC: 2681626603
X-Received-Bytes: 2392
Xref: reader02.eternal-september.org comp.lang.ada:50547
Date: 2018-02-22T04:15:26-08:00
List-Id: <comp.lang.ada>

>> what means exactly Some_access_type'Write(Stream1, Some_Pointer) ?
> Bug, unless=20
> 2. Stream is used for communication inside the same program, e.g. the=20
> pointer is simply marshaled.=20
"Bug", then why is it allowed... Considering access types as elementary typ=
es also confuses me. First thing I learnt about them is you can't hardly ev=
er assume they are simple addresses, or elementary. As for point 2, isn't i=
t what I did in my first example ? I reset the file with mode IN, in immedi=
ate enclosing block, 'Read it but got an erroneous memory access.
There might be numerous ways around this linked data issue but having a san=
e default implementation, as we already have defaults everywhere you can st=
ill override. At least for something as straightforward as "list references=
 and identifiers, reconstruct by aliasing and taking access here, use the s=
tack there". Generics subprograms could be provided in the standard librari=
es.=20
Not enough requests maybe ?