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=ham autolearn_force=no version=3.4.4
X-Google-Thread: 103376,fd173879a595bde
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!nntp.comcast.com!news.comcast.com.POSTED!not-for-mail
NNTP-Posting-Date: Sun, 06 Nov 2005 08:04:58 -0600
From: "Steve" <nospam_steved94@comcast.net>
Newsgroups: comp.lang.ada
References: <slrndmloee.kq0.bogus_addy@tango.mindfuq.org>
 <meKdnXXIJd6tVPfeRVn-vw@comcast.com>
 <slrndmlus8.kq0.bogus_addy@tango.mindfuq.org>
 <TlCaf.1406$uD5.768@newsread3.news.pas.earthlink.net>
 <S9OdnXaVctqkvvHeRVn-jQ@comcast.com>
 <YNWaf.50$Xo.35@newsread2.news.pas.earthlink.net>
Subject: Re: Default rep specs for record types - documented??
Date: Sun, 6 Nov 2005 06:05:27 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Response
Message-ID: <Qs6dndQOsuQXkPPeRVn-qw@comcast.com>
NNTP-Posting-Host: 24.20.111.245
X-Trace: 
 sv3-EOXqROnp7EJohNOS15JJOIOdfJEtvcXnLVaoIqK4lSxOG+a3OaMtJARQdL5QgrGPXxTLs1wY0R1Tk+J!00OEchqgMZ9w5PQW2O3nhN1RXJ3018NfErojqlzMD+QUO0EAg8sGI5iZW4u3vJf3v1djkHGkwdL2
X-Complaints-To: abuse@comcast.net
X-DMCA-Complaints-To: dmca@comcast.net
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint
 properly
X-Postfilter: 1.3.32
Xref: g2news1.google.com comp.lang.ada:6254
Date: 2005-11-06T06:05:27-08:00
List-Id: <comp.lang.ada>

"Jeffrey R. Carter" <spam@spam.com> wrote in message 
news:YNWaf.50$Xo.35@newsread2.news.pas.earthlink.net...
> Steve wrote:
>>
>> I disagree with this conclusion.  While I agree that 3.5.1 describes the 
>> relation between the representation values, it does not define the 
>> representation.
>
> ARM 3.5.1 defines the position numbers, and ARM 13.4 specifies that the 
> representation will be the same as the position numbers unless specified 
> otherwise.
>

Yes, what is the representation of a "position number"?

Is a position number 8 bits?  16 bits? 32 bits?

Isn't it true that for the definition:

  type Color is ( Red, Green, Blue );

Compiler A may choose to use 8 bits to represent an instance of Color, while 
compiler B may use 32 bits to represent an instance of color?

But if you add a representation clause:

  for Color'size use 8;

All compilers will use the same number of bits to represent an instance of 
color?

You're missing my point.

Steve
(The Duck)

> -- 
> Jeff Carter
> "Have you gone berserk? Can't you see that that man is a ni?"
> Blazing Saddles
> 38