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: kenner@lab.ultra.nyu.edu (Richard Kenner)
Subject: Re: Ada95/Mil-Std-1553 Problem (Long Post - Sorry About That)
Date: 1997/01/16
Message-ID: <5bk2sj$cj4$1@news.nyu.edu>#1/1
X-Deja-AN: 210368512
references: <97011417264268@psavax.pwfl.com> <1997Jan14.203917.1@eisner>
organization: New York University Ultracomputer Research Lab
newsgroups: comp.lang.ada
Date: 1997-01-16T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <1997Jan14.203917.1@eisner> kilgallen@eisner.decus.org (Larry Kilgallen) writes:
>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,

>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.

This isn't portable.  There's explicit implementation permission to
reserve a particular space in a record for the tag (but not for any
other internal field).  So a compiler is permitted to reject such a
rep clause (GNAT will, for example).