Given the attention this question / answer receives, and the valuable feedback from GManNickG, I have cleaned up the code a little bit. Two versions are given: one with C++11 features and another one with only C++98 features. In file type.hpp #ifndef TYPE_HPP #define TYPE_HPP #include <string> #include <typeinfo> std::string demangle(const char* name); template <class … Read more
It was sort of answered above, but I’ll try to put things into context. First, C came first. As such, what C does is, sort of, the “default”. It does not mangle names because it just doesn’t. A function name is a function name. A global is a global, and so on. Then C++ came … Read more
C and C++ are superficially similar, but each compiles into a very different set of code. When you include a header file with a C++ compiler, the compiler is expecting C++ code. If, however, it is a C header, then the compiler expects the data contained in the header file to be compiled to a … Read more
The standard tool for listing symbols is nm, you can use it simply like this: nm -gD yourLib.so If you want to see symbols of a C++ library, add the “-C” option which demangle the symbols (it’s far more readable demangled). nm -gDC yourLib.so If your .so file is in elf format, you have two … Read more
extern “C” makes a function-name in C++ have C linkage (compiler does not mangle the name) so that client C code can link to (use) your function using a C compatible header file that contains just the declaration of your function. Your function definition is contained in a binary format (that was compiled by your … Read more