At least the wiki article on MISRA C cites multiple studies that consider the rules mostly pointless, in some cases outright counterproductive and basically accuses it of being only beneficial to companies selling compliance tools. If MISCRA C++ is anywhere as bad you might be better of avoiding it.
With strict rules anyone can write software that does not instantly fail horribly (e.g., if pointers are not allowed, there won't be a bad dereference (but that's not even in misra)). That helps outsourcing to the lowest bidder.
I recently watched this webinar[0] about it, presented by the company ParaSoft, which develops a static analysis tool and compliance reporting solution for businesses required to use MISRA C++[1].
It’s a standard for the use of c++ in critical systems. Basically a guide to techniques and language features you can and can’t use (or how) and still have very predictable/controllable system behavior.
Can someone give the gist of it?