Re: [Stds-754] motion: update exception and flag operations for consistency

[David Hough 754R work <754r@xxxxxxxxxxx>]

> If these functions are added to a general purpose language, such as C,
then they need to work in environments where the floating-point is
not IEEE-754 

Note that none of the spellings or even calling sequences of 754R 
operations are binding on implementations.    Indeed I can't think of any
widespread language that would swallow 754R's unusualNamingConvention whole.

A way for a language like C to deal with 754 and 754R features on
hardware that doesn't support them is to conditionally define them
(so programs fail as early as possible, at compile time).
Another way is to define the calling sequence or function return value to 
be more general than what 754R calls for, to include the possibility of
failure returns to indicate the feature is not available.

754R doesn't require language committees to do anything, but does encourage
them to actively define how their language will deal with 754R, to encourage
portable programming by discouraging too much innovation among implementations.
But 754R explicitly notes that languages might by action or inaction defer
many or all decisions to implementations.