Re: Range checking not working as expected?

Maciej Sobczak wrote:

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.

The default for GNAT, unfortunately, is not Ada. IIRC, at one time overflow checking was "very expensive" on one platform GNAT supported, so they turned it off by default. I don't think that's the case any longer, but it's still turned off by default.

--
Jeffrey Carter
"Now go away or I shall taunt you a second time."
Monty Python and the Holy Grail
E-mail: jeffrey_r_carter-nr [commercial-at]
        raytheon [period | full stop] com
.