Message87933
Daniel Diniz writes:
> Would this break existing code?
Source code? Not if you use the PYTHON_NAMESPACE_ONLY trick. Old
programs will receive all old definitions in addition to the new
autoconf symbols, since they didn't #define PYTHON_NAMESPACE_ONLY.
Programs that do #define PYTHON_NAMESPACE_ONLY will lose symbols you
can't offer because you couldn't be bothered to make them independent
of autoconf. BTW, another "reduced API" variant would be to throw
autoconf-independent symbols out to separate .h files. #include those
files from the .h files they come from, and document that programs can
#include them instead of Python.h. |
|
Date |
User |
Action |
Args |
2009-05-16 21:12:37 | hfuru | set | recipients:
+ hfuru, ajaksu2 |
2009-05-16 21:12:36 | hfuru | link | issue2921 messages |
2009-05-16 21:12:36 | hfuru | create | |
|