Aren't signaling NaNs defined to trigger a floating point exception, not invoke undefined trap-representation behavior? EDIT: I found this proposal (http://www

Aren't signaling NaNs defined to trigger a floating point exception, not invoke undefined trap-representation behavior? EDIT: I found this proposal (http://www.cl.cam.ac.uk/~pes20/cerberus/n2091.html http://www.cl.cam.ac.uk/~pes20/cerberus/n2091.html) which has some discussion about existing trap representations (including whether to consider signaling NaNs to be trap representations). The conclusion seems to be that segmented pointers on the Motorola 68k are the only place trap representations are truly necessary -- maybe it's time to just remove them.