23-08-2006, 11:15 AM
MISRA-C meeting 23-8-2006
It is the experience of members of the committe that rule 5.7 can be sensibly applied to and is common in safety-critical software.
Poor implementations can lead to unreadable long parameter names.
Good implementaion works, and is shown to avoid problems.
It is the experience of members of the committe that rule 5.7 can be sensibly applied to and is common in safety-critical software.
Quote:1. often identifieres are confused because their names are different (so misra compliant) but they closely match (only some characters differ), e.g.
srv, svr, etc... Some lint-like-tools have add-ons that catch such candidates.
2. If you make a (very) rigorous naming schema you easily end up with either unreadable names or very long names (which could violate R5.1)
Poor implementations can lead to unreadable long parameter names.
Good implementaion works, and is shown to avoid problems.
Posted by and on behalf of the MISRA C Working Group