+- MISRA Discussion Forums (https://forum.misra.org.uk)
+-- Forum: MISRA C++ (https://forum.misra.org.uk/forumdisplay.php?fid=18)
+--- Forum: MISRA C++:2023 guidelines (https://forum.misra.org.uk/forumdisplay.php?fid=188)
+---- Forum: General questions (https://forum.misra.org.uk/forumdisplay.php?fid=214)
+---- Thread: Documentation of reasoning to keep/modify/drop AUTOSAR rules (/showthread.php?tid=1674)
Documentation of reasoning to keep/modify/drop AUTOSAR rules - Rico Tilgner - 06-03-2024
We started looking at the new MISRA C++ 2023 guidelines and ways for us to migrate over from AUTOSAR C++14. However, since we have some embedded platforms for which C++17 compilers aren't available (yet), we'll have to apply some combination of AUTOSAR and MISRA until we can fully move over. In Loïc Joly's talk at NDC TechTown he mentioned e.g. the reasoning for getting rid of the single return rule. Does MISRA provide any documentation on such reasonings for other old MISRA/AUTOSAR rules? This would help us a lot in our effort to find an AUTOSAR C++14 subset which we could employ together with MISRA C++ 2023. Alternatively, do you know of any other efforts that are underway to apply MISRA C++ 2023 to C++14 platforms?
RE: Documentation of reasoning to keep/modify/drop AUTOSAR rules - misra cpp - 08-03-2024
As a general rule we don't provide detailed traceability from older standards to the latest version.
However, if you have a question about a specific rule, please post in either this forum or the Autosar C++:2014 forum