Stefan Behnel wrote: > A good idea might be to actually > remove the string interning Option and *always* intern identifiers
That option will probably disappear from Pyrex at some point anyway. It's only there because I wasn't sure if string interning was going to work out, and I didn't want to remove the non-interning code completely until I had all the interning stuff working. But it seems to be okay, and there seems little point in keeping the old code around. > it > breaks the ".next()" method on the scanner, thinking that what we actually > meant was calling the new built-in "next()" function on an iterator. We might > even work around that by actually making it an iterator That wouldn't really be the right thing to do, because the next() method doesn't return a token -- rather it updates the instance variables of the scanner that hold information about the current token. However, it might be usable as a workaround for the 2to3 problem. -- Greg _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
