[MIT-Scheme-devel] Default floating-point traps

[Taylor R Campbell]

I spend way too much time fighting with floating-point traps when I
practically never want them on by default, particularly when trying to
print (e.g.) subnormals at the REPL.

Does anyone care that they're on by default?  Can we disable them?
One can always detect them, or explicitly trap, in particular
computations anyway.

It would also be nice if, e.g., (exp -1000.) gave 0. and set the
inexact-result exception bit, rather than barfing -- that's something
the ucode does explicitly which the floating-point trap control has no
power over.