Re: [Python-Dev] longobject.c ob_size

2005-04-06 Thread Michael Hudson
Tim Peters [EMAIL PROTECTED] writes: [Michael Hudson] Asking mostly for curiousity, how hard would it be to have longs store their sign bit somewhere less aggravating? Depends on where that is. It seems to me that the top bit of ob_digit[0] is always 0, for example, Yes, the top bit of

Re: [Python-Dev] longobject.c ob_size

2005-04-06 Thread Michael Hudson
Michael Hudson [EMAIL PROTECTED] writes: Tim Peters [EMAIL PROTECTED] writes: [Michael Hudson] Asking mostly for curiousity, how hard would it be to have longs store their sign bit somewhere less aggravating? Depends on where that is. [...] I'd much rather give struct _longobject a

Re: [Python-Dev] longobject.c ob_size

2005-04-05 Thread Tim Peters
[Michael Hudson] Asking mostly for curiousity, how hard would it be to have longs store their sign bit somewhere less aggravating? Depends on where that is. It seems to me that the top bit of ob_digit[0] is always 0, for example, Yes, the top bit of ob_digit[i], for all relevant i, is 0 on

Re: [Python-Dev] longobject.c ob_size

2005-04-04 Thread Armin Rigo
Hi Michael, On Sun, Apr 03, 2005 at 04:14:16PM +0100, Michael Hudson wrote: Asking mostly for curiousity, how hard would it be to have longs store their sign bit somewhere less aggravating? As I guess your goal is to get rid of all the if (size 0) size = -size in object.c and friends, I

Re: [Python-Dev] longobject.c ob_size

2005-04-03 Thread Martin v. Löwis
Michael Hudson wrote: Asking mostly for curiousity, how hard would it be to have longs store their sign bit somewhere less aggravating? It seems to me that the top bit of ob_digit[0] is always 0, for example, and I'm sure this would result no less convolution in longobject.c it'd be considerably