[Python-Dev] Compiler warnings

Thomas Wouters thomas at xs4all.net
Wed Feb 1 22:34:22 CET 2006

On Wed, Feb 01, 2006 at 10:15:15AM -0500, Tim Peters wrote:

> Thomas, for these _PyLong_AsScaledDouble()-caller cases, I suggest doing
> whatever obvious thing manages to silence the warning.  For example, in
> PyLong_AsDouble:
> 	int e = -1;  /* silence gcc warning */
> and then add:
> 	assert(e >= 0);
> after the call.

Done, although it was nowhere near obvious to me that -1 would be a sane
sentinel value ;) Not that I don't believe you, but it took some actual
reading of _PyLong_AsScaledDouble to confirm it.

Reading--imagine-that-ly y'rs,
Thomas Wouters <thomas at xs4all.net>

Hi! I'm a .signature virus! copy me into your .signature file to help me spread!

More information about the Python-Dev mailing list