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=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,d2c23a44c4c8fd6b
X-Google-Attributes: gid103376,public
From: Mats Weber <Mats.Weber@elca-matrix.ch>
Subject: Re: fixed point types over an interface
Date: 1997/02/10
Message-ID: <32FF352D.3EA1@elca-matrix.ch>#1/1
X-Deja-AN: 217887879
references: <32FBB550.41C67EA6@efogm.msd.ray.com> <dewar.855364096@merv>
content-type: text/plain; charset=us-ascii
organization: ELCA Matrix SA
mime-version: 1.0
reply-to: Mats.Weber@elca-matrix.ch
newsgroups: comp.lang.ada
x-mailer: Mozilla 3.01 (Macintosh; I; PPC)
Date: 1997-02-10T00:00:00+00:00
List-Id: <comp.lang.ada>


> Two processors are communicating over an interface.  The
> applications for each processor are written/compiled
> using compilers from two different vendors.

> To pin this down, you need to use a Small clause and a Size clause,
> then you should be pretty safe relying on the result, although one
> can imagine compilers doing weird things.

You may also run into big endian/little endian problems. If performance
is not a problem, passing the data in text representation will always
work and be portable.