JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.
If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.
If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.
| CodeSonar® 28.0w | AdaCore Inc |
A file-local function is marked with dllexport, but its internal linkage prevents it from being exposed outside the translation unit.
| Class Name | DLL Interface Requires External Linkage |
|---|---|
| Significance | style |
| Mnemonic | PARSE.DLLIREL |
| Categories | None |
| Availability | Available for C and C++. |
| Enabling | Checks for this warning class are enabled by default.
However, warning instances of this class that are issued as parser
errors (rather than parser warnings)
will be discarded
when using factory configuration settings.
To prevent these instances from being discarded, add the
following WARNING_FILTER rule to the project configuration file.
WARNING_FILTER += allow class="DLL Interface Requires External Linkage" WARNING_FILTER += discard class="DLL Interface Requires External Linkage" |
static __declspec(dllexport) void local_service(); // 'DLL Interface Requires External Linkage' warning issued here
To reproduce this example, analyze it with the following configuration:
WARNING_FILTER += allow class="DLL Interface Requires External Linkage" # Recognize dllexport on the static function so its internal linkage # reaches the DLL-interface external-linkage requirement. # null-cc supplies the invocation on hosts without MSVC. COMPILER_MODELS += null-cc -> cl
null-cc -c example.cpp
The following configuration file parameters affect checks for this warning class.
To report problems with this documentation, please visit https://support.adacore.com/csm.