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-03-03 05:32:38 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!proxad.net!freenix!enst.fr!not-for-mail From: Lionel.DRAGHI@fr.thalesgroup.com Newsgroups: comp.lang.ada Subject: RE: Endianness independance Date: Mon, 3 Mar 2003 14:33:16 +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 1046698358 24276 137.194.161.2 (3 Mar 2003 13:32:38 GMT) X-Complaints-To: usenet@enst.fr NNTP-Posting-Date: Mon, 3 Mar 2003 13:32:38 +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:34824 Date: 2003-03-03T14:33:16+01:00 | -----Message d'origine----- | De: Marin David Condic [mailto:mcondic.auntie.spam@acm.org] ... | | Realistically, the answer is to assess the communications | mechanisms needed, | establish a clearly defined protocol & representation and | then build your | software to deal with that. Ada can be very good at handling the | representation selected, but it really can't define the | representation for | you. I agree with this. What i am complaining about, is that you can't just rely on representation clauses to have interoperability between the same code compiled on two different platform, and exchanging data through a stream socket for exemple. I think that the representation/size/alignment clauses could give enough informations to the compiler to ensure interoperability (provided RM modifications). Am i wrong? As said Amir Yantimirov: "But including notion of endianess (as kind of storage specifier) in existent Ada type system seems impossible to me." Note that Norman Cohen's paper do not address the whole interoperability problem, he just propose a way to portably specify "a data layout". However, this is, i think, the most difficult part of the job. Lionel Draghi