Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
std::exception is not a catch-all
This is a catch-all

try {;} catch(...) {;}

This is not

try {;} catch(std::exception&) {;}

Our validation tool incorrectly triggers the second case as an embedded catch-all violation in a submodule.

Anyone care to debate?

My take is that the rule checker was implemented by python/java folks who think c++ follows the concept of a base exception class.  It does not, since in c++ any type can be an exception parameter.

FWIW, my design heavily leverages c++ shared library .so inclusions which violate autosar eight from sunday even without the erroneous flag.
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++
Posted by and on behalf of
the MISRA C++ Working Group

Forum Jump:

Users browsing this thread: 2 Guest(s)