Richard Earnshaw wrote:
This restriction rules out, for example, using a volatile value as an input in many floating point operations (since the operations may trap depending on the values read).
I don't see this at all. If you have a volatile variable that traps in this situation, then that's just fine, you get the trap. The trap cannot occur unless the program is wandering into undefined areas in any case. Please give an exact scenario here, and explain why you think the standard or useful pragmatic considerations demand the treatment you suggest above.
R.
