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=0.7 required=5.0 tests=BAYES_00,MSGID_RANDY
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,4b89102f705d4611
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2000-11-06 16:10:19 PST
Path: 
 supernews.google.com!sn-xit-02!supernews.com!bignews.mediaways.net!newsfeed.ision.net!ision!cpk-news-hub1.bbnplanet.com!news.gtei.net!nntp2.deja.com!nnrp1.deja.com!not-for-mail
From: Robert Dewar <robert_dewar@my-deja.com>
Newsgroups: comp.lang.ada
Subject: Re: The Incredible Shrinking Type
Date: Tue, 07 Nov 2000 00:04:03 GMT
Organization: Deja.com - Before you buy.
Message-ID: <8u7gte$7ie$1@nnrp1.deja.com>
References: <3A0703F5.9333AE56@earthlink.net>
NNTP-Posting-Host: 129.37.100.242
X-Article-Creation-Date: Tue Nov 07 00:04:03 2000 GMT
X-Http-User-Agent: Mozilla/4.61 [en] (OS/2; I)
X-Http-Proxy: 1.0 x69.deja.com:80 (Squid/1.1.22) for client 129.37.100.242
X-MyDeja-Info: XMYDJUIDrobert_dewar
Xref: supernews.google.com comp.lang.ada:1832
Date: 2000-11-07T00:04:03+00:00
List-Id: <comp.lang.ada>

In article <3A0703F5.9333AE56@earthlink.net>,
  "Marc A. Criley" <marccriley@earthlink.net> wrote:

> However, when passing an instance of this type as a parameter
to a procedure and
> extracting its 'Size, the result is 64.  What happened to the
rest of the bits?
> Granted, they were unused, but still...  Where is this
behavior addressed by the
> language (if it is), or is it a freedom granted to compiler
implementor's?


You are making the common mistake of confusing the size of
a type with the size of objects of the type. Specifying the
size of a type only affects packing and unchecked conversion
in Ada 95 semantics. It does not determine the size of
objects of the type, and there is no requirement that the
size of all objects of the type be the same.

So the real issue here is what you have read in the RM that
implies that the above behavior is expected or not expected.
Actually asking for more than 64 bits for a scalar type is
a bit peculiar anyway (and way out of the portable behavior
required by the RM).


Sent via Deja.com http://www.deja.com/
Before you buy.