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!news4.google.com!news.glorb.com!solnet.ch!solnet.ch!news-zh.switch.ch!switch.ch!cern.ch!news From: Maciej Sobczak Newsgroups: comp.lang.ada Subject: Re: Range checking not working as expected? Date: Thu, 28 Jul 2005 17:35:17 +0200 Organization: CERN - European Laboratory for Particle Physics Message-ID: References: <1305313.0eqo9PA42Q@jellix.jlfencey.com> NNTP-Posting-Host: abpc10883.cern.ch Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sunnews.cern.ch 1122564916 19058 (None) 137.138.37.241 X-Complaints-To: news@sunnews.cern.ch User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050724 Red Hat/1.7.10-1.1.3.1.SL3 X-Accept-Language: en-us, en In-Reply-To: <1305313.0eqo9PA42Q@jellix.jlfencey.com> Xref: g2news1.google.com comp.lang.ada:3819 Date: 2005-07-28T17:35:17+02:00 List-Id: 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/