Re: text2interval again, was Another thought Re:..
On 2013-03-06 17:03:37 -0800, Richard Fateman wrote:
> The value I expect for 0.1 is in hex, 3DCCCCCD for 32 bits
> and in 64 bits,
> 3FB999999999999A
No, what is important is that the string provided to text2interval
is regarded as an interval, not as a pair of numbers (xinf,xsup),
where deserialization would be applied to each of these number,
since the deserialization of a number is just a fixed conversion
from a string to a number while one also needs here a context: a
rounding mode. And that's why text2interval is necessary.
--
Vincent Lefèvre <vincent@xxxxxxxxxx> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
- References:
- Correction to my last posting Re: dependent and independent intervals, proposal to toss out text2interval. Was re: about emp (was: Motion 42:no)
- From: Ralph Baker Kearfott
- Re: dependent and independent intervals, proposal to toss out text2interval. Was re: about emp (was: Motion 42:no)
- Re: dependent and independent intervals, proposal to toss out text2interval. Was re: about emp (was: Motion 42:no)
- Re: dependent and independent intervals, proposal to toss out text2interval. Was re: about emp (was: Motion 42:no)
- Re: dependent and independent intervals, proposal to toss out text2interval. Was re: about emp (was: Motion 42:no)
- dependent and independent intervals, proposal to toss out text2interval. Was re: about emp (was: Motion 42:no)
- dependent and independent intervals, proposal to toss out text2interval. Was re: about emp (was: Motion 42:no)
- text2interval again, was Re: Another thought Re:..
- text2interval again, was Another thought Re:..
- Re: text2interval again, was Another thought Re:..