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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,45a9122ddf5fcf5
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Valid Attribute and Unchecked Conversion
Date: 1996/10/11
Message-ID: <dewar.845050338@merv>#1/1
X-Deja-AN: 188882798
references: <DyCF97.7zp@world.std.com> <1996Oct1.100608.1@eisner>
 <qw6buemy9ea.fsf@gargantua.enst.fr>
 <mheaney-ya023180000110962027510001@news.ni.net> <Dynt6I.5D1@world.std.com>
 <DyqAKA.DJn@thomsoft.com> <dewar.844695770@schonberg>
 <325D44F2.32F5@lmtas.lmco.com>
organization: New York University
newsgroups: comp.lang.ada
Date: 1996-10-11T00:00:00+00:00
List-Id: <comp.lang.ada>


"Can't we go a little further, and write an AI (similar to the Ada 83 AI on
unchecked conversion between scalars of the same size) to formally document
what should happen? It's good that the AARM says "act sensibly," but wouldn't
an AI be better?"

Well the first step is for someone to write a question and send it to
the appopriate email address (see Ada 95 RM). This will usually result
in an AI prepared by Bob Duff, although he will be happy to have help!

But this is not an easy AI to write. In particular, I suggest restricting
it to discrete types rather than scalar types, since floating-point types
are contentious because of signalling Nan's.

Also, be sure to think in terms of conversion between scalar *types* and
not scalar *objects*, since this is what UC is about. I am not quite
sure what the abbreviation scalars means above, but it smacks of scalar
object to me!