2012/4/3 Maciej Fijalkowski <fij...@gmail.com>: > I would like to point out that all the assumptions like "this type is not > subclassable" or "this field is read only" might work on cpython, but the > JIT will make assumptions based on that and it'll stop working or produce > very occasional segfaults
Fortunately pypy objects are not exposed to C code, only a copy of fields and slots; and all transfers are explicitly written in RPython by cpyext. But no need to invoke the JIT here; with cpyext there can be only one object at a given address (!) and even if we had a PyCFunction_Call, it would not receive the correct interpreter object. This could be done of course, but with another hack. -- Amaury Forgeot d'Arc _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
