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,8df81176cbd821cd X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news3.google.com!news.glorb.com!news.tele.dk!not-for-mail Newsgroups: comp.lang.ada Subject: Re: Range checking not working as expected? References: <1305313.0eqo9PA42Q@jellix.jlfencey.com> From: Mark Lorenzen Date: 28 Jul 2005 20:10:24 +0200 Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Organization: TDC Totalloesninger NNTP-Posting-Host: 83.88.98.142 X-Trace: 1122574225 dtext02.news.tele.dk 178 83.88.98.142:11390 X-Complaints-To: abuse@post.tele.dk Xref: g2news1.google.com comp.lang.ada:3823 Date: 2005-07-28T20:10:24+02:00 List-Id: Maciej Sobczak writes: > Vinzent 'Gadget' Hoefler wrote: > > > Try again after compiling with -gnato to actually enable the overflow > > checking. > > OK, it "works" now. It is still not what I'd expect - "the default in > Ada is safety", or something like this; I'd expect to actually need to > go into some troubles to disable such checking. But it is still good > that it works by default for non-border-case definitions like range > 1..10. I presume that in practice the Integer type is not widely used > and that typical ranges have limits dependent on the given domain and > not on some hardware specifics. > > Thank you for explanation, > > > -- > Maciej Sobczak : http://www.msobczak.com/ > Programming : http://www.msobczak.com/prog/ Check the "-gnato" section at http://gcc.gnu.org/onlinedocs/gcc-4.0.1/gnat_ugn_unw/Run_002dTime-Checks.html#Run_002dTime-Checks for a discussion. - Mark Lorenzen