Hi Greg, Greg Ewing wrote: * I have streamlined the integer for-loop syntax. Instead > of the loop variable redundantly appearing in two places, > it's now just > > for x < i < y: > ...
while this is shorter, it also breaks existing code - although I assume you left the old syntax in? Also, I'm not sure this is more readable if x is non trivial. > * If you declare a variable as a list or dict, then calls > to some of its methods will be compiled into type-specific > Python API calls instead of generic ones. Cython has a bit of that also. This would be something to bring back in line. > * Most built-in constants are referenced directly instead of > via dict lookup. Again, something like that is in Cython as well, but I'm not up-to-date with the details. Probably works different... > * There are two new builtin functions, typecheck() and > issubtype(), for checking the types of arguments more safely > (since isinstance and issubclass can be fooled). Could you elaborate on the actual problem here? I also noticed you have a couple of new test cases. Could you imagine using our doctest based test runner as well? That way, we could at least share the test suites and see more easily which problems apply to both code bases. http://hg.cython.org/cython-devel/file/tip/runtests.py Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
