Message31484
I expressed myself badly. I apologise. This really isn't about +0. and -0.
being different, or not. I'm perfectly comfortable with the idea that +0.
and -0. may or may not be distinguishable on any given platform.
The surprise is the other way around: two *identical* calls to atan(0., -1.)
(or to repr(0.) for that matter) give *different* results, depending solely
on whether a -0. literal has appeared earlier on in the code unit being compiled.
So if the first float zero literal encountered in a source file just happens to be a
-0. rather than a 0., the meaning of str(0.) later on suddenly becomes "-0.0"
rather than "0.0". I'd like to be able to rely on str(0.) meaning "0.0" without
having to worry about whether there might be a -0. literal appearing in some
faraway and otherwise completely irrelevant portion of the file.
|
|
Date |
User |
Action |
Args |
2007-08-23 14:52:24 | admin | link | issue1678380 messages |
2007-08-23 14:52:24 | admin | create | |
|