| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
All, Of course, the matter is different for external character strings. When we convert '0.1' to interval, we know it is inexact, so we would probably want an interval whose lower bound and upper bound enclose the exact number '0.1'. The lower bound and upper bound can be specified according to the round-down and round-up rules specified in 754-2008 for converting such character strings to the floating point format. Baker P.S. I'm speaking now as a participant, rather than acting chair. Arnold Neumaier wrote:
[forwarded to the list] R. Baker Kearfott wrote:Arnold Neumaier wrote:But do you really support Van Snyder's view that conversion of floats should treat the latter as inaccurate?No, I do not. We have no idea what the user intends when a float is presented to the conversion operator. I feel the best course would be to treat it as exact. If it's clear in the standard, then users can go from there, and compensate if they know just how inexact it is. If it's not treated as exact, we are forcing the user to accept wider data than was possibly intended. You can quote me to the entire list as you wish. Best regards, Baker
-- --------------------------------------------------------------- R. Baker Kearfott, rbk@xxxxxxxxxxxxx (337) 482-5346 (fax) (337) 482-5270 (work) (337) 993-1827 (home) URL: http://interval.louisiana.edu/kearfott.html Department of Mathematics, University of Louisiana at Lafayette (Room 217 Maxim D. Doucet Hall, 1403 Johnston Street) Box 4-1010, Lafayette, LA 70504-1010, USA ---------------------------------------------------------------