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,79db4ff72bff9422 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-10-31 18:13:14 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: byhoe@greenlime.com (Adrian Hoe) Newsgroups: comp.lang.ada Subject: Re: How to convert record? Date: 31 Oct 2001 18:13:14 -0800 Organization: http://groups.google.com/ Message-ID: <9ff447f2.0110311813.4bf57352@posting.google.com> References: NNTP-Posting-Host: 210.186.172.45 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1004580794 5405 127.0.0.1 (1 Nov 2001 02:13:14 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 1 Nov 2001 02:13:14 GMT Xref: archiver1.google.com comp.lang.ada:15522 Date: 2001-11-01T02:13:14+00:00 List-Id: "Beard, Frank" wrote in message news:... > -----Original Message----- > From: byhoe@greenlime.com [mailto:byhoe@greenlime.com] > > > You are wrong. Try compile the following example and you will get 14 > > and 16 for each. > > I'm not wrong. Your posts on this thread said nothing about requiring > it to be 11 bytes. You were asking how to convert it to a POSIX IO_Buffer. You are wrong in another way. :) Joseph asked to convert it to POSIX IO_Buffer, not me, Adrian! > What I was saying is, if ALL YOU WANT TO DO is send and receive it across > homogeneous platforms then you don't need to worry about the size. Let > the system, via 'size of the object, do it for you. The compiler will > do what is more efficient for it's processing. There's no reason to > work against it unless you have to. > > If you are sending it to a device that requires it to be 11 bytes, then > that's a different issue. And of course a rep spec and pragma pack are > going to make a difference in the size, but that wasn't the issue either. > > Your thread on "Size and pack" only led me to believe you expected 11 > bytes, but got 14. NOT that it HAD to be 11. Expecting one thing and > getting something else does not imply a requirement. > > So, which is it? Does it have to be 11, or are you just sending it to > an equivalent peer system. OK. My apologies to the wrong pointing. It's my fault but I knew Joseph is working on a similar project like mine (we are colleagues :) and my instinct immediately jumped to the conclusion without thoroughly going through your post properly. Hey.. Take it easy, I am not written in Ada! :,)