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,40c8d1d2d927ffd9 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2004-02-19 23:41:13 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!npeer.de.kpn-eurorings.net!rz.uni-karlsruhe.de!feed.news.schlund.de!schlund.de!news.online.de!not-for-mail From: Michael Paus Newsgroups: comp.lang.ada Subject: Re: Interoperability: differing storage units and/or endianess Date: Fri, 20 Feb 2004 08:41:10 +0100 Organization: 1&1 Internet AG Message-ID: References: <9fb7e8e1.0402190429.49b37b16@posting.google.com> NNTP-Posting-Host: p508a95e8.dip0.t-ipconnect.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: online.de 1077262871 27043 80.138.149.232 (20 Feb 2004 07:41:11 GMT) X-Complaints-To: abuse@einsundeins.com NNTP-Posting-Date: Fri, 20 Feb 2004 07:41:11 +0000 (UTC) User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030612 X-Accept-Language: en-us, en In-Reply-To: <9fb7e8e1.0402190429.49b37b16@posting.google.com> X-Enigmail-Version: 0.76.8.0 X-Enigmail-Supports: pgp-inline, pgp-mime Xref: archiver1.google.com comp.lang.ada:5683 Date: 2004-02-20T08:41:10+01:00 List-Id: Bibb Latting wrote: > Hi, I am working on a distributed application where the processors > have differing storage unit sizes and/or endianess. My problem is how > to handle the specification of memory contents and the delivery of > data to applications with minimal variation between implementations. > I'd like to know what solutions have worked well for others. And I'd like to know which currently used processors have a storage unit size other than 8. Michael