On 5/29/06, Tim Peters <[EMAIL PROTECTED]> wrote:
> [Neal Norwitz]
> > * hash values
> > Include/abstract.h: long PyObject_Hash(PyObject *o); // also in
> > object.h
> > Include/object.h:typedef long (*hashfunc)(PyObject *);
>
> We should leave these alone for now. There's no real connectio
On 5/29/06, "Martin v. Löwis" <
[EMAIL PROTECTED]> wrote:
I agree using Py_ssize_t would be a "smaller" change, and one thatlikely has less performance impact. It would still be a large change,and should be only done if we know for sure we don't want it to be
a 64-bit type always the next day.Well
Thomas Wouters wrote:
> Neal Norwitz wrote:
> > minus comments, etc yields several questions about whether some
> > values should use Py_ssize_t rather than C longs. In particular:
>
> > * ints: Include/intobject.h:long ob_ival;
>
> As Tim says, this is way out of scope
On 5/29/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
Neal Norwitz wrote:> minus comments, etc yields several questions about whether some> values should use Py_ssize_t rather than C longs. In particular:> * ints: Include/intobject.h:long ob_ival;
As Tim says, this is way out of scope for
Neal Norwitz wrote:
> minus comments, etc yields several questions about whether some
> values should use Py_ssize_t rather than C longs. In particular:
>
> * hash values
> Include/abstract.h: long PyObject_Hash(PyObject *o); // also in
> object.h
> Include/object.h:typedef long (*hashfunc)
[Neal Norwitz]
> * hash values
> Include/abstract.h: long PyObject_Hash(PyObject *o); // also in object.h
> Include/object.h:typedef long (*hashfunc)(PyObject *);
We should leave these alone for now. There's no real connection
between the width of a hash value and the number of elements in
[Neal Norwitz]
>> * ints: Include/intobject.h:long ob_ival;
[Thomas Wouters]
> I considered asking about this before, as it would give '64-bit power' to
> Win64 integers. It's a rather big change, though (lots of code assumes
> PyInts fit in signed longs, which would be untrue then.)
I expec
On 5/29/06, Neal Norwitz <[EMAIL PROTECTED]> wrote:
* ints: Include/intobject.h:long ob_ival;I considered asking about this before, as it would give '64-bit power' to Win64 integers. It's a rather big change, though (lots of code assumes PyInts fit in signed longs, which would be untrue then.
$ grep long */*.h
minus comments, etc yields several questions about whether some
values should use Py_ssize_t rather than C longs. In particular:
* hash values
Include/abstract.h: long PyObject_Hash(PyObject *o); // also in object.h
Include/object.h:typedef long (*hashfunc)(PyObject *);
