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=-2.9 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI autolearn=unavailable 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 09:21:17 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!skynet.be!skynet.be!freenix!enst.fr!not-for-mail From: Lionel.DRAGHI@fr.thalesgroup.com Newsgroups: comp.lang.ada Subject: RE: Endianness independance Date: Fri, 28 Feb 2003 18:21:55 +0100 Organization: ENST, France Message-ID: Reply-To: "comp.lang.ada mail to news gateway" NNTP-Posting-Host: marvin.enst.fr Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Trace: avanie.enst.fr 1046452876 11727 137.194.161.2 (28 Feb 2003 17:21:16 GMT) X-Complaints-To: usenet@enst.fr NNTP-Posting-Date: Fri, 28 Feb 2003 17:21:16 +0000 (UTC) To: comp.lang.ada@ada.eu.org Return-Path: X-Mailer: Internet Mail Service (5.5.2653.19) X-BeenThere: comp.lang.ada@ada.eu.org X-Mailman-Version: 2.1 Precedence: list List-Id: comp.lang.ada mail to news gateway List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Xref: archiver1.google.com comp.lang.ada:34728 Date: 2003-02-28T18:21:55+01:00 | -----Message d'origine----- | De: Stephen Leake [mailto:Stephen.A.Leake@nasa.gov] .. | I was not aware that he had made a proposal that required language | revision. | | I use a variant of his technique now, with good results (once I | actually _know_ what the hardware endianness is :). | You are probably speaking of his technique to get Bit_Order attribute effect with Ada 83 code, presented in the "Endian-Independent Record Representation Clauses" paper? 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. -- Lionel Draghi.