Alexander Belopolsky <belopol...@users.sourceforge.net> added the comment:
On Fri, Jan 2, 2009 at 10:54 AM, Marc-Andre Lemburg <rep...@bugs.python.org> wrote: > > Marc-Andre Lemburg <m...@egenix.com> added the comment: > > Also note that by removing the extern "C" declarations, you not only > change the exported symbol names of functions, but also those of > exported globals. > What are " exported globals" other than "exported symbol names of functions"? AFAIK, C++ does not mangle non-function symbols. > Those would also have to get declared in the header files, to prevent > their names from being mangled (causing the exported C API to change). I believe .c files should only contain static functions and functions that are declared in an included header file. If a function that is not advertised in a header, it is not part of API and it is a fair game to mangle it. The only exception is the module init functions that are part of the ABI rather than API. _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue4805> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
