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,febd9e55846c9556
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-02-28 12:35:09 PST
Path: 
 archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-post-02!sn-post-01!supernews.com!corp.supernews.com!not-for-mail
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
Subject: Re: Endianness independance
Date: Fri, 28 Feb 2003 14:37:12 -0600
Organization: Posted via Supernews, http://www.supernews.com
Message-ID: <v5vhvstp1nbp00@corp.supernews.com>
References: <mailman.8.1046452875.1343.comp.lang.ada@ada.eu.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft Outlook Express 4.72.3612.1700
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3719.2500
X-Complaints-To: abuse@supernews.com
Xref: archiver1.google.com comp.lang.ada:34741
Date: 2003-02-28T14:37:12-06:00
List-Id: <comp.lang.ada>

Lionel.DRAGHI@fr.thalesgroup.com wrote in message ...
>I was speaking of "A Proposal for Endian-Portable Record Representation
>Clauses", which suggest to get non default bit order support mandatory,
and
>the byte offset (the number between "at" and "range" within
representation
>clauses) related to machine scalar instead of byte.
>
>As i understand it, this proposal cause no upward compatibility
problem, but
>i have no idea of the rework it could cause within compilers.


His proposal was turned into AI-133.

Unfortunately, he stopped attending meetings about that time. When we
(the ARG) considered his proposal, we couldn't understand the the
details (which were never written up in the standard form), and
essentially assigned someone to make a complete proposal. It's still on
someone's action list, but it seems likely that other priorities (such
as coming to a consensus on a solution to the mutually dependent types
problem) will keep it from being addressed again.

                    Randy Brukardt
                    ARG Editor