Marc-Andre Lemburg <m...@egenix.com> added the comment: On 2009-01-03 04:38, Alexander Belopolsky wrote: > 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 >> changes 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.
GCC doesn't appear to do so, but there's no guarantee that other C++ compilers won't touch these symbols: http://en.wikipedia.org/wiki/Name_mangling >> 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. That's right, but I was referring to non-function globals. These would have to be declared in the header files as well to prevent their names from being mangled. OTOH, those globals will often not be accessed directly from other object files - only through functions providing an interface to them. Still, this would have to be checked. _______________________________________ 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
