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=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,c6f0d0c4aaf03392
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!postnews.google.com!i3g2000cwc.googlegroups.com!not-for-mail
From: "Adam Beneschan" <adam@irvine.com>
Newsgroups: comp.lang.ada
Subject: Re: Universal float or not - who's right ?
Date: 11 Sep 2006 12:44:06 -0700
Organization: http://groups.google.com
Message-ID: <1158003846.013059.75150@i3g2000cwc.googlegroups.com>
References: <45016cb7$1_4@news.bluewin.ch>
   <UK6dnTg4_IC6h5_YnZ2dnUVZ_oidnZ2d@megapath.net>
NNTP-Posting-Host: 66.126.103.122
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1158003851 21106 127.0.0.1 (11 Sep 2006 19:44:11
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Mon, 11 Sep 2006 19:44:11 +0000 (UTC)
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.7.12) Gecko/20050922 Fedora/1.7.12-1.3.1,gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: i3g2000cwc.googlegroups.com; posting-host=66.126.103.122;
   posting-account=cw1zeQwAAABOY2vF_g6V_9cdsyY_wV9w
Xref: g2news2.google.com comp.lang.ada:6559
Date: 2006-09-11T12:44:06-07:00
List-Id: <comp.lang.ada>

Randy Brukardt wrote:
> "Gautier" <gautier@fakeaddress.nil> wrote in message
> news:45016cb7$1_4@news.bluewin.ch...
> ...
> >    d: constant FF.FFLoat:= 2.0**4;
> >    -- Fails on compiler A,B,C
> >    -- "**" is not visible, an "use FF;" is missing
> >
> >    package FPe is new P(FF.FFLoat,2.0**4);
> >    -- ** A,B,C differ:
> >    -- Passes on C: (2.0**4) probably taken as universal float
> >    -- Fails on compiler A,B: same reason as for constant d
>
> Compiler C is wrong, the expression resolution for D and the parameter of
> FPe should be the same. The short reason is that expressions can only have a
> universal type if they are in a context that allows one (such as a named
> number); otherwise *operators* (as opposed to literals) must have the
> correct type. Adam explains why in detail.

You mean I got it right?  Yay!!

                        -- Adam