🚀 go-pugleaf

yIn article <ROCKWELL.92Apr15214305@socrates.umd.edu> rockwell@socrates.umd.edu (Raul Deluth Miller-Rockwell) writes:
|Stephen P Spackman:
|   Obviously, I meant 32767 (that or I meant max). The point is that
|   the maximum for the representation and the maximum for the type are
|   different notions, and that in any case (no matter what IEEE may
|   tell you) "infinity" is not an integer and it's not a float. It's a
|   domain extension, and you shouldn't have to rely on them in order
|   to code up simple notions like min and max.
|
|So use the maximum for the type.
|
|If you wish to exclude certain representations, there will still be a
|maximum element among the representations you allow.

Not safe in the presence of conversions. And, unless your type was
specified by the user choosing bounds of hir own, a dangerous
confusion of the implementation with the object. Finally, how does
this solution work with bignums?

All in all, not an acceptable engineering alternative, IMHO.
----------------------------------------------------------------------
stephen p spackman         Center for Information and Language Studies
stephen@estragon.uchicago.edu                    University of Chicago
----------------------------------------------------------------------