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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,6cc2d0131145e263 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-08-10 13:08:03 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!newsfeed00.sul.t-online.de!t-online.de!newsfeed.r-kom.de!fu-berlin.de!news.cid.net!news.enyo.de!news1.enyo.de!not-for-mail From: Florian Weimer Newsgroups: comp.lang.ada Subject: Re: Question about "for X'Size use ..." Date: Fri, 10 Aug 2001 22:25:44 +0200 Organization: Enyo's not your organization Message-ID: <87ofpnzmpj.fsf@deneb.enyo.de> References: <3B72C23E.62F7B3D2@san.rr.com> <5ee5b646.0108091439.3e48faef@posting.google.com> <871ymk480x.fsf@deneb.enyo.de> <5ee5b646.0108100911.1e1b02fb@posting.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Xref: archiver1.google.com comp.lang.ada:11781 Date: 2001-08-10T22:25:44+02:00 List-Id: dewar@gnat.com (Robert Dewar) writes: > The mention of storing the sign is a bit bogus, given that virtually > all machines are twos complement now. Hmm, the DSP on one of the sound cards lying around here is a one-complement architecture, but you're right nevertheless. > More importantly you now get complete interoperability for the type > > type x is range 0 .. 255; > for x'size use 8; > > which was not the case before But the cases in which one stream element is written are the only ones which are specified completely. The others still remain open. I find this highly undesirable. With the current scenario, you don't even achieve cross-compiler compatibility on the same architecture. For example, a vendor might have chosen to write integers generally in big-endian format, independently of the preferred order of the architecture, to gain cross-architecture compatibility for this compiler. > If you think an AI is pointless, you are probably missing something. Probably. I'm still a bit irritated because people are dealing with such issues and do not tackle the more eminent problem of specifying the byte/octet order for discrete types (both in-memory representation and stream I/O layout).