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,d2c23a44c4c8fd6b X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: fixed point types over an interface Date: 1997/02/18 Message-ID: #1/1 X-Deja-AN: 219686506 References: <32FBB550.41C67EA6@efogm.msd.ray.com> <1997Feb17.181818.3508@news.nbi.dk> Organization: New York University Newsgroups: comp.lang.ada Date: 1997-02-18T00:00:00+00:00 List-Id: Jacob says <<| For composite types, the Write or Read attribute for each component is | called in a canonical order ... Read and Write should use the smallest | number of stream elements needed to represent all values in the base | range of the scalar type. ^^^^^^^^^^ Is there anything that prevents the "stream elements" to fill 32 bits? If I read 13.13.1 in the LRM correctly, then there's absolutely nothing that prevents type Stream_Element from being declared as "mod 32".>> Right, that would be perfectly valid, but in any case, the part of yoru quote after the ... is only implementation advice, and this means that it should be followed unless there is good reason not to follow it, and in any case whether you follow it or not has nothing to do with conformance.