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-Thread: a07f3367d7,5afd69f1373c41cc
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news2.google.com!news.glorb.com!gegeweb.org!aioe.org!not-for-mail
From: tmoran@acm.org
Newsgroups: comp.lang.ada
Subject: reserved fields; was Re: Interfacing with C ;
 an ununsed fields dilemma
Date: Thu, 2 Jul 2009 18:14:51 +0000 (UTC)
Organization: Aioe.org NNTP Server
Message-ID: <h2iter$ba4$1@aioe.org>
References: 
 <bcd29aeb-57e6-4da7-bf30-d20717e98193@l12g2000yqo.googlegroups.com>
NNTP-Posting-Host: jsj6/wjO/cHSAHkcGxcp1Q.user.aioe.org
X-Complaints-To: abuse@aioe.org
X-Notice: Filtered by postfilter v. 0.7.9
X-Newsreader: Tom's custom newsreader
Cancel-Lock: sha1:Tiy23KJZIfMO5s7Dx7m8ETi4yuc=
Xref: g2news2.google.com comp.lang.ada:6807
Date: 2009-07-02T18:14:51+00:00
List-Id: <comp.lang.ada>

> A lot of C structure are defined with so called unused field
> reserved for future use (oftenly never used in any future). This
> fields are generally to be initialized to zero, what is required, to
> unsure it will not be errorneously interpreted ...

  So such a field is not unused - it's currently a version field whose
value is zero, but in the future it may take non-zero values with
meanings other than version number, so "Version_Number" would not
be an appropriate name. "Reserved", or possibly "TBD", would be
appropriate names.

   type C_Rec is record
      I1       : Integer  := 0;
      Reserved : Integer range 0 .. 0 := 0;
      F1       : Float    := 0.0;
   end record;
   for C_Rec use record
      I1       at 0 range  0 .. 31;
      Reserved at 4 range 32 .. 63;
      F1       at 8 range 64 .. 95;
   end record;