Lisandro Dalcin, 25.02.2010 00:07: > On 24 February 2010 18:58, Greg Ewing wrote: >> Currently I'm thinking of dropping the 'api' keyword and >> having a compiler option that would turn on api generation >> for the whole module for anything declared in the pxd, >> or maybe anything declared 'public', or both. > > Now that you said it, a similar approach could be this: > > 1) merge 'public' and 'api', perhaps by dropping 'api'. > > 2) Add a compiler directive/switch to decide the actual mechanism for > exporting stuff: the non-static way for visibility across compilation > units, the DL_EXPORT/D_IMPORT way, or PyObject/PyCapsule way, or both.
I don't think it would break anything to let 'public' imply 'api'. I'm not a big fan of compiler options, though. The decision should be taken in the code. I'd be ok with an option that /disables/ the generation of the public C-API, if it's generated by default for 'public' names. Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
