[pypy-dev] missing things for making PyPy "production" ready (for some value of production)
Carl Friedrich Bolz
cfbolz at gmx.de
Fri Nov 16 12:52:17 CET 2007
Neal Becker wrote:
> [...]
>>> Indeed. But there are tools to generate most of the painful code:
>>> Swig, boost::python, and others.
>>> With Swig, you can even subclass C++ classes and override virtual
>>> methods in python.
>>> I wish pypy could do the same.
>> Both methods involve parsing C++, which is not fun. For example,
>> concerning wxwidget, I for once think it would be much easier to wrap
>> gtk than wxwidget (if we think: would be good to have a GUI lib for
>> pypy); incidently, that's how pygtk is generated (some python + scheme
>> code generate the pygtk wrapper around gtk).
>>
>
> boost::python does not involve parsing c++.
yip, it does. The compiler parses C++, after all :-).
nitpickingly-yours,
Carl Friedrich
More information about the Pypy-dev
mailing list