Gregory P. Smith writes:
> heh good point. ignore that thought. python is a signed language. :)
For what little it's worth, I object strongly. The problem isn't
Python, it's C. Because the rules give unsigned precedence over
signed in implicit conversions, mixed signed/unsigned arithmetic i
heh good point. ignore that thought. python is a signed language. :)
On 8/25/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> I look at it from another POV -- does anyone care about not being able
> to represent dimensionalities over 2 billion? I don't see the
> advantage of saying unsigned in
I look at it from another POV -- does anyone care about not being able
to represent dimensionalities over 2 billion? I don't see the
advantage of saying unsigned int here; it just means that we'll get
more compiler warnings in code that is otherwise fine. After all, the
previous line says 'int read
Anyone mind if I do this?
--- Include/object.h(revision 57412)
+++ Include/object.h(working copy)
@@ -148,7 +148,7 @@
Py_ssize_t itemsize; /* This is Py_ssize_t so it can be
pointed to by strides in simple case.*/
int readonly;
-
