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,438f2856ab36a026 X-Google-Attributes: gid103376,public From: tmoran@bix.com (Tom Moran) Subject: Re: 83/95 issue, bad code or compiler bug Date: 1998/11/20 Message-ID: <3655a8f6.326075@news.pacbell.net>#1/1 X-Deja-AN: 413933795 References: X-Complaints-To: abuse@pacbell.net X-Trace: typhoon-sf.snfc21.pbi.net 911583627 206.170.24.102 (Fri, 20 Nov 1998 09:40:27 PDT) Organization: SBC Internet Services NNTP-Posting-Date: Fri, 20 Nov 1998 09:40:27 PDT Newsgroups: comp.lang.ada Date: 1998-11-20T00:00:00+00:00 List-Id: >Don't mix rep clauses and types-with-constraints. Why not? Certainly if it's an input record the usual caveats about not relying on correctness apply, but for an output record I see no problem. I've also used the component form Fixed_Thing : Integer range 10 .. 10 := 10; when the Fixed_Thing component of an output record is required to have a particular, fixed value (eg the record size in some Windows API calls).