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: 103376,ab43ecf7e1a10743 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!fu-berlin.de!uni-berlin.de!not-for-mail From: "Martin Dowie" Newsgroups: comp.lang.ada Subject: Re: Zero_Fill pragma Date: Wed, 21 Jul 2004 10:00:26 +0100 Organization: BAE SYSTEMS Message-ID: <40fe2f6b$1_1@baen1673807.greenlnk.net> References: X-Trace: news.uni-berlin.de RNewiH0MVzMPchTMRD2JBgoj1tMMs23IBHiw4RhdIK+yWPByVk X-Orig-Path: baen1673807.greenlnk.net!baen1673807!not-for-mail X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Original-NNTP-Posting-Host: baen1673807.greenlnk.net Xref: g2news1.google.com comp.lang.ada:2307 Date: 2004-07-21T10:00:26+01:00 List-Id: Nick Roberts wrote: > The pragma is not intended to affect any of the bits that are > used to represent a value. In a composite type, you sometimes > get 'gaps' in between components (or possibly at the edges), > of 'unused' bits. The pragma is intended to cause these > unused bits to be initialised to 0 whenever the composite > object as a whole is initialised. It is not intended to affect > the initialisation (or reading or updating) of any of the > components. What about hardware/interface specs that require '1' not '0'?.. ;-)