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,17395bd9bffaca19
X-Google-Attributes: gid103376,public
From: kilgallen@eisner.decus.org (Larry Kilgallen)
Subject: Re: Ada95/Mil-Std-1553 Problem (Long Post - Sorry About That)
Date: 1997/01/15
Message-ID: <1997Jan14.203917.1@eisner>#1/1
X-Deja-AN: 209904387
x-nntp-posting-host: eisner.decus.org
references: <97011417264268@psavax.pwfl.com>
x-nntp-posting-user: KILGALLEN
x-trace: 853292369/20451
organization: LJK Software
newsgroups: comp.lang.ada
Date: 1997-01-15T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <97011417264268@psavax.pwfl.com>, "Marin David Condic, 561.796.8997, M/S 731-93" <condicma@PWFL.COM> writes:

>     Is there a way with tagged records to control the position/content
>     of any and all tag data? (In a manner that is reasonably close to
>     portable so that it's not dependent on, for example,
>     implementation X uses a 16 bit integer for a tag vs implementation
>     Y uses a 32 bit integer...) In other words, if I can guarantee that
>     the tag data will occur at the end (or beginning?) of the record
>     and/or that it will occupy exactly N bytes, I think I can figure out
>     how to solve my send/receive problems. It would be better if I
>     could control the *value* of the tag, but I'll settle for knowing
>     where it is so I can strip it off.

I don't know how you could control the size.

I would think you could ensure it was at the end by using
representation clauses for all the other elements of the records,
essentially "filling up" the beginning so there is no space left
for the tag data except at the end.

Larry Kilgallen