For compatibility with similar scoping features in Microsoft Visual C++ (MSVC++) for dynamic libraries, the following syntax is also supported:
|
When taking advantage of this syntax with Oracle Solaris Studio C++, you should add the option -xldscope=hidden to CC command lines. The result will be comparable to the results using MSVC++. With MSVC++, __declspec(dllimport) is supposed to be used only on declarations of external symbols, not on definitions. Example:
__declspec(dllimport) int foo(); // OK
__declspec(dllimport) int bar() { ... } // not OK MSVC++ is lax about allowing dllimport on definitions, and the results using Oracle Solaris Studio C++ will be different. In particular, using dllimport on a definition using Oracle Solaris Studio C++ results in the symbol having global linkage instead of symbolic linkage. Dynamic libraries on Microsoft Windows do not support global linkage of symbols. If you run into this problem, you can change the source code to use dllexport instead of dllimport on definitions. You will then get the same results with MSVC++ and Oracle Solaris Studio C++.