David Abrahams wrote:
>  b. The code generated by Boost.Python isn't equivalent to the above in
>     any trivial sense. Almost everything in traditional 'C' extension
>     building is geared towards initializing arrays of (function)
>     pointers and constants which the Python core treats almost as a
>     program, interpreting elements of the array and generating Python
>     objects (e.g. callables) from them.  Boost.Python doesn't/can't
>     take advantage of these mechanisms, so it builds the Python objects
>     directly.  I guess what I'm saying is that the mapping is not very
>     direct so I don't see a comparison with the 'C' API extension is
>     going to help.

Could just be me, but I think the above is exactly the kind of thing 
we'd want in such a document. :)

I'd be happy to pitch in with the internal documentation after my exams 
btw. I'll have to dig deeper into Boost.Python to examine the 
Py_Finalize bug anyway.

Regards,
Dirk Gerrits



_______________________________________________
C++-sig mailing list
C++-sig@[...].org
http://mail.python.org/mailman/listinfo/c++-sig