Lisandro Dalcin wrote: > Greg, I would love to have some input from your side. This is > something where Pyrex and Cython should agree (probably by following > recommended, documented practices in core CPython).
I originally had static linking in mind when I invented 'public', but I didn't really think much about the issue at the time. I'm used to unix, where making a name visible makes it available for both static and dynamic linking. The idea that they might be different just seems weird and unnecessary to me. So I think that 'public' should probably make the name both statically and dynamically linkable if reasonably possible. I'm not sure about 'api'. I actually don't really like having two different keywords for exporting names, it's too confusing. But I haven't come up with a clear idea of what I want to do about it. 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. That doesn't really help to clear up the relationship between 'public' and 'api', though. -- Greg _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
