[Python-Dev] Re: More int/long integration issues
David Abrahams
dave@boost-consulting.com
Thu, 20 Mar 2003 16:43:51 -0500
Thu, 20 Mar 2003 16:43:51 -0500
- Previous message: [Python-Dev] Re: More int/long integration issues
- Next message: [Python-Dev] Re: More int/long integration issues
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Guido van Rossum <guido@python.org> writes: > The bytecode compiler should be clever enough to see that you're > writing > > for i in range(...): ... > > and that there's no definition of range other than the built-in one > (this requires a subtle change of language rules); it can then > substitute an internal equivalent to xrange(). Ouch! What happens to: def foo(seq): for x in seq: ... foo(xrange(small, really_big)) if xrange dies?? -- Dave Abrahams Boost Consulting www.boost-consulting.com
- Previous message: [Python-Dev] Re: More int/long integration issues
- Next message: [Python-Dev] Re: More int/long integration issues
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]