Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: yes on motion 48, with comments



I vote yes on 48, but believe that I/O syntax and semantics should be left to implementers with only one requirement: containment in both input and output.



On 8/28/13 8:05 AM, Richard Fateman wrote:
I vote yes on motion 48 but with the following comments.

1. I would hope that any language in which interval arithmetic is supported would provide sufficient tools to read and write scalar numeric quantities
to allow read/write  or write/read isomorphism, and that therefore
Exact to Interval etc.  are unnecessary.

2. Also .. any language .. would allow reading of numeric quantities with
rounding up or down, making the issue of enclosure moot.  This might be
eased by defining NaI as an interval with a NaN endpoint.

3. I do not expect to ever have to use this part of an interval package.

44.  I expect that the standard document could be made much simpler
by essentially leaving this out.

5. If some people feel otherwise and insist on internalizing
I/O into the standard and are willing to spend the time and effort to
refine it until there is a consensus among people who care about it, OK.

So I vote yes.