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,56250291936154a0 X-Google-Attributes: gid103376,public From: "Tarjei T. Jensen" Subject: Re: OS Bindings (was: Where is the elusive jump command?) Date: 2000/04/13 Message-ID: <8d457u$5n33@ftp.kvaerner.com>#1/1 X-Deja-AN: 610597461 Content-Transfer-Encoding: 7bit References: <38D771CA.D41AF9B5@port.ac.uk><8bq7ku$mc8$1@nnrp1.deja.com><38E0E723.C39C392@quadruscorp.com><8brfm4$4uc$1@nnrp1.deja.com><8brn4k$p6i$1@slb0.atl.mindspring.net><8brrpj$i04$1@nnrp1.deja.com><38E312F8.78883ACB@icn.siemens.de><8c4rvf$d9k$1@nnrp1.deja.com><2000Apr5.070127.1@eisner><2000Apr6.081305.1@eisner><8ci6vf$r5a$1@nnrp1.deja.com><8ck638$krs3@ftp.kvaerner.com><8cp23c$4gp$1@nnrp1.deja.com><8csjs8$o2p3@ftp.kvaerner.com><8d0su8$bqt$1@nnrp1.deja.com> <8d20bq$o2p4@ftp.kvaerner.com> Content-Type: text/plain; charset="iso-8859-1" X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0 Organization: Kv�rner Group IT Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 2000-04-13T00:00:00+00:00 List-Id: Robert A Duff wrote >Also because System.Max_Int is 2**63-1 or 2**31-1 on most >implementations, and there's a rule saying that the bounds have to be >less than or equal to System.Max_Int. > >If I made the rules, there would be no Max_Int. Then I change the declaration to type T is range 0 .. #16#ffff_ffff_ffff_ffff; If the compiler complains because the number is out of range for an integer if it otherwise supports 64 bit numbers I think the compiler has been poorly constructed. As long as the lower bound is 0 or positive then it is quite clear that it is a unsigned type. It seems pointless to involve max_int in this unless we are talking about a signed number. I don't care about the T base type. I think that the above definition is perfectly reasonable even though it may be contrary to the letter of the standard. I think it is a glaring oversight in the standard if it not only allows, but requires compilers to honour a definition like the one above. I don't have the final version of the RM here, only the June 94 version. Greetings,