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,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.36.10.20 with SMTP id 20mr529930itw.30.1519357204405;
        Thu, 22 Feb 2018 19:40:04 -0800 (PST)
X-Received: by 10.157.46.5 with SMTP id q5mr13292otb.10.1519357204340; Thu, 22
 Feb 2018 19:40:04 -0800 (PST)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!border1.nntp.ams1.giganews.com!nntp.giganews.com!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer03.am4!peer.am4.highwinds-media.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!w142no586767ita.0!news-out.google.com!s63ni1508itb.0!nntp.google.com!o66no584906ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Thu, 22 Feb 2018 19:40:04 -0800 (PST)
In-Reply-To: <p6nkte$tbk$1@franka.jacob-sparre.dk>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=76.113.16.86;
 posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC
NNTP-Posting-Host: 76.113.16.86
References: <503e3322-ee8e-4d6f-9aa5-e7b98f87e8f8@googlegroups.com>
 <5d8580c2-b43d-4b2c-8a46-3a6ed33967aa@googlegroups.com>
 <p6nkte$tbk$1@franka.jacob-sparre.dk>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <434b1e3e-da5a-4846-8942-f7ec8ea6ce34@googlegroups.com>
Subject: Re: article on acces types and dynamic serialization in Ada (2003)
From: Shark8 <onewingedshark@gmail.com>
Injection-Date: Fri, 23 Feb 2018 03:40:04 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 1686
X-Received-Body-CRC: 4103340029
Xref: reader02.eternal-september.org comp.lang.ada:50582
Date: 2018-02-22T19:40:04-08:00
List-Id: <comp.lang.ada>

On Thursday, February 22, 2018 at 4:49:04 PM UTC-7, Randy Brukardt wrote:
> "Mehdi Saada" wrote in message 
> news:5d8580c2-b43d-4b2c-8a46-3a6ed33967aa
> ...
> >There might be numerous ways around this linked data issue but having a
> >sane default implementation, as we already have defaults everywhere
> >you can still override.
> 
> What default (read relatively cheap to read/write) implementation could 
> possibly be sane?

ASN.1 serialization/deserialization.