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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,9eeeccfe8f29c5a1
X-Google-Attributes: gid103376,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!postnews.google.com!h25g2000hsf.googlegroups.com!not-for-mail
From: arban <kevin.dickson@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: Sequential_Io metadata
Date: Fri, 29 Feb 2008 10:10:13 -0800 (PST)
Organization: http://groups.google.com
Message-ID: 
 <3945e196-a05a-4f07-8c4b-e14c4dad6cf8@h25g2000hsf.googlegroups.com>
References: <7a532ced-6e6c-4906-8b75-b42a5618204c@41g2000hsc.googlegroups.com>
NNTP-Posting-Host: 199.46.198.237
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Trace: posting.google.com 1204308613 23250 127.0.0.1 (29 Feb 2008 18:10:13
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Fri, 29 Feb 2008 18:10:13 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: h25g2000hsf.googlegroups.com; posting-host=199.46.198.237;
	posting-account=jxRpoQoAAADtVlf2JLrawgK5uIC6r0is
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.8.1.12)
	Gecko/20080201 Firefox/2.0.0.12,gzip(gfe),gzip(gfe)
X-HTTP-Via: 1.1 bos-gate6.raytheon.com:8080 (Squid/2.4.STABLE7)
Xref: g2news1.google.com comp.lang.ada:20155
Date: 2008-02-29T10:10:13-08:00
List-Id: <comp.lang.ada>

Never mind my stupidity. In my test client I was printing the data
from the wrong byte offset.

All three bytes of metadata is the size in bytes of the record
following it.

On Feb 29, 11:53 am, arban <kevin.dick...@gmail.com> wrote:
> I have files which were written using Sequential_Io instantiations of
> a record with discriminants under Rational Apex 3.2.0. It would appear
> that 3 extra bytes are written to the file just before the actual
> record data. The first two bytes appear to be the size of the record
> written, but I cannot figure out what the 3rd byte represents. Anyone
> happen to have worked with this before?
>
> Thanks,
> Kevin