Plan for implementation of Fortran IEEE modules

N.M. Maclaren nmm1@cam.ac.uk
Thu Nov 7 12:08:00 GMT 2013


Sorry about this, but I have just realised that I was missing a trick.

The information calls and constants can, at worst, be wrong.  There
is no reason not to have them always available.

A lot of people will get very unhappy if libraries fiddle with the
settings in a way that affects their code, and they don't know about it.
That's a disaster in C, and a multiplex disaster on wheels in C++, but
even Fortran has procedure arguments and derived type methods.

Mode settings probably should be enabled by some environment variable
or flag such as IEEE_ME_HARDER or -fieee-me-harder, though one can
argue ad tedium about how many such flags, their defaults and their
names.  Now, it IS possible for implementations to have a compiler
flag that is checked for consistency by the run-time system, but that
is sadly out of fashion :-(  My main point is that there is an actual
requirement for production code.


Regards,
Nick Maclaren.



More information about the Fortran mailing list