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 overloaded member function call has matching arguments, but the object has type qualifiers that prevent a match.
| Class Name | No Matching Function Due to Selector |
|---|---|
| Significance | style |
| Mnemonic | PARSE.NO.MATCHINGFUNCTIONDUETOSELECTOR |
| 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="No Matching Function Due to Selector" WARNING_FILTER += discard class="No Matching Function Due to Selector" |
struct Device {
void reset(int);
void reset(double);
};
void f(const Device &device)
{
device.reset(1); // 'No Matching Function Due to Selector' warning issued here
}
void reset_fixed(Device &device)
{
device.reset(1); // ok: mutable object matches the nonconst member function
}
To reproduce this example, analyze it with the following configuration:
WARNING_FILTER += allow class="No Matching Function Due to Selector"
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.