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,2afac1a4161c7f35 X-Google-Attributes: gid103376,public From: mheaney@ni.net (Matthew Heaney) Subject: Re: Distinguishing type names from other identifiers Date: 1998/01/24 Message-ID: #1/1 X-Deja-AN: 318898888 Content-Transfer-Encoding: 8bit References: <199801151530.QAA21301@basement.replay.com> Content-Type: text/plain; charset=ISO-8859-1 Organization: Estormza Software Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1998-01-24T00:00:00+00:00 List-Id: In article <199801151530.QAA21301@basement.replay.com>, nobody@REPLAY.COM (Anonymous) wrote: >> This is similar to the issue shops have declaring a heading type that >> doesn't have the value 360.0 in the range. Do this for a floating point >> type, if you really insist on not having 360.0 as a value: >> >> type Ownship_Heading_Base is digits 5; -- whatever the precision req'd >> >> subtype Ownship_Heading is >> Ownship_Heading_Base range 0.0 .. Ownship_Heading_Base'Succ (360.0); >> > >Surely you mean 'Pred, not 'Succ? Yup. I should have written Ownship_Heading_Base'Pred (360.0) Thanks for the correction, and sorry for any confusion. Matt -------------------------------------------------------------------- Matthew Heaney Software Development Consultant (818) 985-1271