Safer C++: MISRA-C++ : 202X Rules and Beyond
summary
MISRA C++ 202x aims to codify a safer C++ subset for C++17 targets, with rules enforced by static analysis and a public GitHub vulnerability draft for community feedback. Examples include enum class vs unscoped enum where compilers drop a default branch because of undefined-value assumptions, forbidding volatile for thread communication and promoting the rule of zero and smart pointers instead of raw new/delete. Mandatory, required and advisory rule categories guide deviations and tool-driven warnings.
AI-written summary · about
chapters (17)
- 0:00Introduction to safety
- 2:58Safety critical systems
- 7:22V-model and safety levels
- 10:07Fault tolerance concepts
- 13:39Undefined behavior risks
- 15:29Coding standards evolution
- 19:03Guideline objectives
- 23:05Static analysis tools
- 27:59Rules and exceptions
- 32:20AUTOSAR and MISRA details
- 36:56Deviation and documentation
- 40:00Modernizing guidelines
- 45:07Writing safer code
- 59:00Resource management
- 1:02:03Language vulnerabilities
- 1:07:52Summary and future work
- 1:11:19Q&A session
related talks
01h 05mSafer C++ with MISRA-C++ 2023
57mMISRA C++202x: It ain't your grandpa's MISRA any more
57mThe Misra C++:2023 Guidelines
58mMisra Parallelism Safety-critical Guidelines for C++11, 17, Then C++20, 23
53mFrom Chaos to Control: Overcoming C and C++’s Inherent Unsafety
01h 29mC++ Safety And Security Panel 2024
51mMISRA C and C++ in OSS: Yes, We Can!
01h 02mHow to deal with static analysis findings: MISRA