x&y is a long when either x or y is a long. When it could/should be only when both are long.
In particular x&1 is a long whenever x is. Despite the fact that the numerical answer is either 0 or 1.
I’m not saying this is wrong, just… ugly.
Roll on Py3K.
2008-05-14 at 18:44:44
Does Py3K abolish longs? They should have done that long ago (make long a synonym for int).
2008-05-14 at 21:22:48
Apparently so. Scary reading, by the way.
They clearly should have done it long ago. My opinion on things like this generally is that Common Lisp is the roadmap, so just get with the program and implement it. Stop fumbling around in the dark.