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=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: G. B. <nonlegitur@nmhp.invalid>
Newsgroups: comp.lang.ada
Subject: Re: article on acces types and dynamic serialization in Ada (2003)
Date: Fri, 23 Feb 2018 20:28:13 -0000 (UTC)
Organization: A noiseless patient Spider
Message-ID: <p6ptgt$qr5$1@dont-email.me>
References: <503e3322-ee8e-4d6f-9aa5-e7b98f87e8f8@googlegroups.com>
 <5d8580c2-b43d-4b2c-8a46-3a6ed33967aa@googlegroups.com>
 <p6nkte$tbk$1@franka.jacob-sparre.dk>
 <434b1e3e-da5a-4846-8942-f7ec8ea6ce34@googlegroups.com>
 <87tvu8890r.fsf@jacob-sparre.dk>
 <p6oju9$12qv$1@gioia.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 23 Feb 2018 20:28:13 -0000 (UTC)
Injection-Info: reader02.eternal-september.org;
 posting-host="5f401bfa869a065845c8ba38987add76";
	logging-data="27493"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX182jj5iVGq/wol6iu19Cwuf3KAHlMnYjeg="
User-Agent: NewsTap/5.3.1 (iPhone/iPod Touch)
Cancel-Lock: sha1:YAsmKghJe8wjXlZv8bBbqaLS60o=
	sha1:X2aEpfqqz13ZNo2XuWK3BbFQT1c=
Xref: reader02.eternal-september.org comp.lang.ada:50609
Date: 2018-02-23T20:28:13+00:00
List-Id: <comp.lang.ada>

Dmitry A. Kazakov <mailbox@dmitry-kazakov.de> wrote:
> On 23/02/2018 08:23, Jacob Sparre Andersen wrote:
>> Shark8 <onewingedshark@gmail.com> writes:
>>> On Thursday, February 22, 2018 at 4:49:04 PM UTC-7, Randy Brukardt wrote:
>> 
>>>> What default (read relatively cheap to read/write) implementation
>>>> could possibly be sane?
>>> 
>>> ASN.1 serialization/deserialization.
>> 
>> That doesn't solve the problem of the compiler having to figure out how
>> to interpret the access types.
> 
> It does not solve any problem, being an utter abomination and horror to 
> anyone who must implement a protocol described in this form.

Serialization isn‘t a protocol, though.