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 2002:a05:620a:127a:: with SMTP id
 b26mr26743107qkl.219.1588079009377;
        Tue, 28 Apr 2020 06:03:29 -0700 (PDT)
X-Received: by 2002:aca:4858:: with SMTP id v85mr2718757oia.51.1588079008958;
 Tue, 28 Apr 2020 06:03:28 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!aioe.org!peer01.ams4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Tue, 28 Apr 2020 06:03:28 -0700 (PDT)
In-Reply-To: <r88gta$edb$1@dont-email.me>
Complaints-To: groups-abuse@google.com
Injection-Info: google-groups.googlegroups.com; posting-host=70.109.61.2;
 posting-account=QF6XPQoAAABce2NyPxxDAaKdAkN6RgAf
NNTP-Posting-Host: 70.109.61.2
References: <ea6d64d1-fb0c-42de-b787-26ccfbccee9b@googlegroups.com>
 <26e971a9-6fcc-4e4c-84ee-d74aecd5b217@googlegroups.com>
 <r838c5$5ts$1@dont-email.me>
 <2c769c87-72f2-4107-b0bf-3846e3ae6c7a@googlegroups.com>
 <r84f7m$20l$1@dont-email.me>
 <670160da-e66d-446f-a415-27df39d9a73f@googlegroups.com>
 <r86jep$93r$1@dont-email.me>
 <250c110a-667d-419a-b52a-89646c178d99@googlegroups.com>
 <r88gta$edb$1@dont-email.me>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <f653c10d-44b5-48be-8c1a-005115cfd717@googlegroups.com>
Subject: Re: Image attribute (yet again)
From: Jere <jhb.chat@gmail.com>
Injection-Date: Tue, 28 Apr 2020 13:03:29 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2940
X-Received-Body-CRC: 624598314
Xref: reader01.eternal-september.org comp.lang.ada:58520
Date: 2020-04-28T06:03:28-07:00
List-Id: <comp.lang.ada>

On Tuesday, April 28, 2020 at 2:02:20 AM UTC-4, J-P. Rosen wrote:
> Le 27/04/2020 =C3=A0 16:10, Jere a =C3=A9crit=C2=A0:
> >> This feature requires that if you write a number in a certain base, th=
en
> >> you need to recognize the base when reading. So it's not an error, but=
 a
> >> design decision. Of course, like any design decision, you may agree wi=
th
> >> it or not.
> > As I have thought about this more, I don't think I see the need
> > for the "16#" and associated for this functionality to work.  If you
> > are using the reflective Get to the Put, that knows the base.  The
> > text doesn't need to specify it. If you want something more runtime
> > adaptive, then sure, but for pure reflective Get/Put it isn't needed
> > that I can tell.  In the case where a more runtime adaptive strategy
> > is desired, that is where I would have expected the language to want
>=20
> Huh? The Get procedure has no parameter for the base, it accepts
> whatever is in the file.
>=20
> The design principle is that you are precise on output, and tolerant on
> input. Same idea with 'Image (required to be upper case) and 'Value
> (accepts any case).
>=20
> --=20
> J-P. Rosen
> Adalog
> 2 rue du Docteur Lombard, 92441 Issy-les-Moulineaux CEDEX
> Tel: +33 1 45 29 21 52, Fax: +33 1 45 29 25 00
> http://www.adalog.fr

Yeah, I misread the RM as having the base on Get as well.