22-03-2022, 11:19 AM
As currently written A15-3-4 regards both catch(...) and catch(std::exception&) as 'catch-all's
Options © and (d) of the headline would allow the use of a catch-all in a function other than 'main' or a thread entry, but these are completely undecidable. Your analysis tool is therefore at liberty to raise a violation.
Currently, we are not expecting this rule to appear in the next version of MISRA C++
Options © and (d) of the headline would allow the use of a catch-all in a function other than 'main' or a thread entry, but these are completely undecidable. Your analysis tool is therefore at liberty to raise a violation.
Currently, we are not expecting this rule to appear in the next version of MISRA C++
Posted by and on behalf of
the MISRA C++ Working Group
the MISRA C++ Working Group