Message87933
| Author |
hfuru |
| Recipients |
ajaksu2, hfuru |
| Date |
2009年05月16日.21:12:36 |
| SpamBayes Score |
5.6980576e-09 |
| Marked as misclassified |
No |
| Message-id |
<hbf.20090516x2co@bombur.uio.no> |
| In-reply-to |
<1242502767.56.0.76309180668.issue2921@psf.upfronthosting.co.za> |
| Content |
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. |
|
History
|
|---|
| 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 |
|