I'm getting a compiler warning from your checkin: C:\py25\Objects\floatobject.c(1430) : warning C4244: 'initializing' : conversion from 'double ' to 'float ', possible loss of data
"Raymond Hettinger"
I'm getting a compiler warning from your checkin:
"your"? Mine?
C:\py25\Objects\floatobject.c(1430) : warning C4244: 'initializing' : conversion from 'double ' to 'float ', possible loss of data
That's this line: float y = x; where x is of double type. This seems an, um, daft warning to me, but it's easy to fix, and I've fixed it. Cheers, mwh -- The only problem with Microsoft is they just have no taste. -- Steve Jobs, (From _Triumph of the Nerds_ PBS special) and quoted by Aahz on comp.lang.python
[Raymond Hettinger]
I'm getting a compiler warning from your checkin:
[Michael Hudson]
"your"? Mine?
Alas, a typical exchange. The checkins are mailed from the committer's Sf email address, but the mailing list has been set up to redirect all replies to python-dev -- if you don't catch this before sending, you may be embarrassed in public or confuse the addressee. Is this behavior of the checkins list really a good idea? -- --Guido van Rossum (home page: http://www.python.org/~guido/)
Alas, a typical exchange. The checkins are mailed from the committer's Sf email address, but the mailing list has been set up to redirect all replies to python-dev -- if you don't catch this before sending, you may be embarrassed in public or confuse the addressee.
Is this behavior of the checkins list really a good idea?
I think it should be changed. In addition to making it a PITA to send notes to the committer, there is another issue. For anyone subscribing to python-dev but not the checkins list, they see conversations started without seeing the history of checkins that gave rise to those conversations. Worse, the resolution of those conversations is often another checkin (which doesn't get cc'd to python-dev so it is not obvious when there is a resolution). For instance, this thread was resolved by Michael's checkin, 2.137, but you wouldn't know that from reading python-dev. A few years ago, the cc to python-dev was not automatic and the default reply address was the original committer. That worked much better. Raymond P.S. I still don't follow the whole yours/mine comment from Michael. The offending code line was part of 2.136 which CVS says was checked-in by him on 5/27/2005 and then fixed by him on 6/30/2005.
On 4 Jul 2005, at 18:59, Raymond Hettinger wrote:
P.S. I still don't follow the whole yours/mine comment from Michael. The offending code line was part of 2.136 which CVS says was checked-in by him on 5/27/2005 and then fixed by him on 6/30/2005.
Well, my confusion started and ended with the fact that a mail to python-dev with no obvious indication of being a reply to anything used the word "your", without a name or any indication of who you were addressing. I'm afraid I don't remember the exact revisions of the exact files I've checked in recently :) Cheers, mwh
participants (4)
-
Guido van Rossum
-
Michael Hudson
-
Raymond Hettinger
-
Raymond Hettinger