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 |
An explicit instantiation appears in a namespace that does not enclose the namespace where the template is declared.
| Class Name | Bad Scope for Explicit Instantiation |
|---|---|
| Significance | style |
| Mnemonic | PARSE.BAD.SFEI |
| 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="Bad Scope for Explicit Instantiation" WARNING_FILTER += discard class="Bad Scope for Explicit Instantiation" |
namespace A {
template<class T> void function(T) {}
}
namespace B {
template void A::function(int); // 'Bad Scope for Explicit Instantiation' warning issued here
}
template void A::function(double); // ok: instantiate at global scope, enclosing namespace A
To reproduce this example, analyze it with the following configuration:
WARNING_FILTER += allow class="Bad Scope for Explicit Instantiation"
g++ -c -std=c++11 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.