> I am not sure what the point you are trying to make is, just by reading > a bit of the URL you pointed to. Maybe I should read more... :-/
neeh - i seem to have managed a sensible explanation just earlier today on pypy-dev, and i think also that people here have been exploring modifications to CPython already. > I should just point out that supporting C extension modules in PyPy has > been discussed, but the obvious conclusion was that you can't just > recompile the ones from CPython and hope that they work (unless you do > completely evil tricks, e.g. with the garbage collector). *sigh* yes i had forgotten about GC - thank you for reminding me. here's the thing: the unladen/swallow team, for phase 2, are _going_ to "unbox" the CPython base types (int, long, string, dict, list etc.). that means that they are _going_ to face the evil tricks, and more. the question i invite the pypy-dev team to consider is this: given that unladen/swallow team is going to tackle these issues, does the pypy-team want to leverage that opportunity, given that it faces exactly the same issue (as does the pyjs+pyv8 experiment) ? l. _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
