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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,d233b131fc3b7ba7
X-Google-Attributes: gid103376,public
From: Simon Wright <simon@pogner.demon.co.uk>
Subject: Re: Help: Storage size
Date: 1999/07/14
Message-ID: <x7vyagjdmsl.fsf@pogner.moho>#1/1
X-Deja-AN: 501068036
X-NNTP-Posting-Host: pogner.demon.co.uk:158.152.70.98
References: <7mejue$9lk$1@nnrp1.deja.com> <7mf7lp$c9g@hobbes.crc.com>
 <7mfndb$mc8$1@nnrp1.deja.com> <7mfs92$jch@hobbes.crc.com>
 <7mh556$7ue$1@nnrp1.deja.com>
X-Trace: news.demon.co.uk 931985424 nnrp-13:24904 NO-IDENT
 pogner.demon.co.uk:158.152.70.98
Organization: At Home
Newsgroups: comp.lang.ada
X-Complaints-To: abuse@demon.net
Date: 1999-07-14T00:00:00+00:00
List-Id: <comp.lang.ada>

Adrian Hoe <byhoe@my-deja.com> writes:

> This method gives the most assurance in plain Ada context. But, what
> if the intention to interface from Ada to the original (assumed) C's
> struct? Is this method applicable in this context (Interfacing to
> C)?

If you are interfacing to C then you should definitely use the types
in Interfaces.C. But I thought you said earlier that you had :16 in a
struct in case the platform's unsigned_short wasn't 16 bits???

You really need to go back to see how CARD16 is defined, I think.

IIRC, you are looking at Xlib stuff -- almost certainly this will be
in terms of C types. X protocol stuff, now that's different ..

In X, you're much more likely to have portability trouble with long,
in my experience. Also endianness.

Do you really have to implement your own bindings? I'm sure there are
some free ones out there .. try adahome ..