Mark Dickinson <[EMAIL PROTECTED]> added the comment: Another thought: macros that are going to be used elsewhere in Python (like the way you're using PyLong_SIGN in mathmodule.c) would probably be better off in longobject.h. The fewer places there are that have to include longintrepr.h, the easier it is to mess with the internal representation.
It's quite tempting to 'fix' _PyLong_AsScaledDouble to return e as the number of bits, rather than the number of digits; then mathmodule.c wouldn't have to include longintrepr.h at all. (And if marshal.c were also changed, to read and write integers as byte strings, we wouldn't need longintrepr.h anywhere any more!) _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4294> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
