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=-2.9 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI autolearn=unavailable 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 11:42:48 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!213.56.195.71!fr.usenet-edu.net!usenet-edu.net!enst!enst.fr!not-for-mail From: "Beard, Frank" Newsgroups: comp.lang.ada Subject: RE: How to convert record? Date: Wed, 31 Oct 2001 14:40:22 -0500 Organization: ENST, France Sender: comp.lang.ada-admin@ada.eu.org Message-ID: Reply-To: comp.lang.ada@ada.eu.org NNTP-Posting-Host: marvin.enst.fr Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Trace: avanie.enst.fr 1004557367 48248 137.194.161.2 (31 Oct 2001 19:42:47 GMT) X-Complaints-To: usenet@enst.fr NNTP-Posting-Date: Wed, 31 Oct 2001 19:42:47 +0000 (UTC) To: "'comp.lang.ada@ada.eu.org'" Return-Path: X-Mailer: Internet Mail Service (5.5.2448.0) Errors-To: comp.lang.ada-admin@ada.eu.org X-BeenThere: comp.lang.ada@ada.eu.org X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: comp.lang.ada mail<->news gateway List-Unsubscribe: , List-Archive: Errors-To: comp.lang.ada-admin@ada.eu.org X-BeenThere: comp.lang.ada@ada.eu.org Xref: archiver1.google.com comp.lang.ada:15501 Date: 2001-10-31T14:40:22-05:00 -----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. 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.