Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Proposal: Rule 0-1-4 exception
Exception: Variables which are written by the program but read by an external entity (e.g. ASAM MCD tools like Vector CANape) are not considered a violation of this rule.
This rule reports (e.g.) dead stores as they may be the sign of a defect.

As with your proposal for an exception to 0-1-3, there would be no way for a tool to know that the intent is for the value to be read by something other than the program.

You would, of course, also have to ensure that any objects have volatile qualification to ensure that the compiler does not optimise out what it sees as dead stores.

Looks like another candidate for a permit / deviation (which needs to include a requirement for volatile qualification).
We agree with mishak, whilst a valid reason for a deviation, there is no way of expressing this as a checkable exception to the rule, as a static analysis tool cannot know what use other software is going to make of a variable
Posted by and on behalf of
the MISRA C++ Working Group

Forum Jump:

Users browsing this thread: 1 Guest(s)