Re: How to catch NaNs with gnat3.14p

["Alexander Boucke" <alexb@lufmech.rwth-aachen.de>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]


Preben Randhol wrote in message ...
>I don't have 3.14p yes, so what does it say in the : Run-time Checks
>part of the GNAT User Guide? In 3.13p it says:
>
>`-gnato'
>     Enables overflow checking for integer operations.  This causes
>     GNAT to generate slower and larger executable programs by adding
>     code to check for both overflow and division by zero (resulting in
>     raising `Constraint_Error' as required by Ada semantics).  Note
>     that the `-gnato' switch does not affect the code generated for
>     any floating-point operations; it applies only to integer
>     operations. For floating-point, GNAT has the `Machine_Overflows'
>     attribute set to `False' and the normal mode of operation is to
>     generate IEEE NaN and infinite values on overflow or invalid
>     operations (such as dividing 0.0 by 0.0).
>
>
>--
>Preben Randhol         �For me, Ada95 puts back the joy in programming.�

This read similar in the gnat3.14p UG, but in the features-file included it
says
that gnat has now been modified so that all generated NaNs "will always fail
any range check and cause Constraint_Error to be raised". That's what I was
looking for.

Regards,
Alexander