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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,dd6622a305422ade X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-09-09 22:49:51 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!newsfeed00.sul.t-online.de!t-online.de!newsfeed.r-kom.de!newsfeed.stueberl.de!newsfeed.vmunix.org!newsfeed2.easynews.net!easynews.net!news.cid.net!news.enyo.de!news1.enyo.de!not-for-mail From: Florian Weimer Newsgroups: comp.lang.ada Subject: Re: Suggestion for Ada 0X - "Complete" Record Rep Clauses Date: Mon, 10 Sep 2001 07:44:01 +0200 Organization: Enyo's not your organization Message-ID: <87sndvsiqm.fsf@deneb.enyo.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Xref: archiver1.google.com comp.lang.ada:12970 Date: 2001-09-10T07:44:01+02:00 List-Id: "Chris Miller" writes: > Record representation clauses (LRM13.5.1) allow the locations for the > components of a record to be specified, but there is no way to ensure that > the location for each and every field is specified. If you do not specify > the location for a component then the compiler can put it anywhere. This is > generally not what is wanted, if a rep clause is used then typically the > location of all fields will need to be specified. Specifying the representation only partially could be used in some contexts, for example to rearrange some components so that they appear in a single cache line.