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-Thread: a07f3367d7,36c197595b07e443 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!feeder.news-service.com!news.albasani.net!not-for-mail From: Leslie Newsgroups: comp.lang.ada Subject: Re: Cross-platform issues Date: Sun, 06 Dec 2009 17:39:00 -0600 Organization: albasani.net Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Trace: news.albasani.net pjHwDsyV4Q2ngG7WGCOu0hlTaTYSF6tfgfTCo2vG3Rk3g89JfGf96bFb81+dsPQ+VR4fAN6DrVTTxvbHxITvascY3p6OyJoL0ULG5Gf/Ly47vWsB1tQ5zATev21fJlN4 X-Complaints-To: abuse@albasani.net NNTP-Posting-Date: Sun, 6 Dec 2009 23:38:29 +0000 (UTC) X-User-ID: YDbVcW/VEye73S7tph938QeK67yyp38mUKgAyxTmOc5KVDQch6JDseqrcuaaJ2OaxOiYa2iRYLx54DSx39dSXA== Cancel-Lock: sha1:b+WI3L4pLU2ljkOWR3clViLS8P0= User-Agent: KNode/0.10.9 X-NNTP-Posting-Host: mBw0hRtLejaZ+B9p9bqyLc2p9UbvKJKIHkDSarfyQVg= Xref: g2news1.google.com comp.lang.ada:8328 Date: 2009-12-06T17:39:00-06:00 List-Id: John B. Matthews wrote: > In article , > Leslie wrote: > >> I'm working on an application that I would like to be capable >> of communicating between hosts, and I wonder how the issue of >> 32-bit vs. 64-bit, and perhaps endianness should best be >> handled? > > I'm guessing that would depend on how much and what kind of > data, as well as a given compiler's support for representation. > Here's an example of one vendor's documentation of this: > > nd-Pragmas.html#Representation-Clauses-and-Pragmas> > > Another approach is to avoid such problems altogether by using > Ada Web Server (AWS) and defining all communication atop HTTP: > > > What I'm working on is a product that I want to conform as closely as possible to the one that inspired it. The original emits trace data with things like field length info in 4-byte integers, for example. I suppose that using a derived type to ensure that in my implementation those fields conform with the original is one way to do it, but is that accepted practice, or is there a more usual one? BTW, I'm just getting into Ada, and the only books I have for reference were from the early 90s, so at this point my ideas on how to proceed are a bit vague. :-) Leslie