Comments on: MISRA – More Irrelevant Software Requirements Again http://www.klocwork.com/blog/2010/03/misra-more-irrelevant-software-requirements-again/?utm_source=rss&utm_medium=rss&utm_campaign=misra-more-irrelevant-software-requirements-again >kloctalk is a blog and a community for software development professionals who create and maintain mission-critical software and the challenges they face on a daily basis. Tue, 24 Jan 2012 14:57:13 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Importance of MISRA | >kloctalk http://www.klocwork.com/blog/2010/03/misra-more-irrelevant-software-requirements-again/comment-page-1/#comment-6251 Importance of MISRA | >kloctalk Tue, 26 Jul 2011 13:00:35 +0000 http://www.klocwork.com/blog/?p=942#comment-6251 [...] pockets of adoption, but in Europe and even Asia it used quite a bit.  As we have mentioned in the past, it is not only automotive organization but all levels of [...] [...] pockets of adoption, but in Europe and even Asia it used quite a bit.  As we have mentioned in the past, it is not only automotive organization but all levels of [...]

]]> By: MISRA rules that don’t make sense | >kloctalk http://www.klocwork.com/blog/2010/03/misra-more-irrelevant-software-requirements-again/comment-page-1/#comment-2309 MISRA rules that don’t make sense | >kloctalk Thu, 13 May 2010 20:18:13 +0000 http://www.klocwork.com/blog/?p=942#comment-2309 [...] I posted the value of using coding standards, specifically MISRA C and MISRA C++.  This time I wanted to go [...] [...] I posted the value of using coding standards, specifically MISRA C and MISRA C++.  This time I wanted to go [...]

]]> By: Twylite http://www.klocwork.com/blog/2010/03/misra-more-irrelevant-software-requirements-again/comment-page-1/#comment-2078 Twylite Fri, 16 Apr 2010 07:54:15 +0000 http://www.klocwork.com/blog/?p=942#comment-2078 The point of MISRA is to improve quality of embedded software in the motor industry, to improve portability of code across platforms, and to reduce surprise errors from poorly understood corners of the C standard that you are more likely to encountered with embedded C compilers. Rule 2.2 for example suggests that you don't use // comments, which are not universally supported in the embedded world (IIRC they aren't a C standard, but a C++ one). Rule 19.1 reduces the chance of linking against the wrong function (if you have two functions with the same name, in different source files), which eliminates a class of subtle bugs. As you say, it depends on what you're trying to accomplish - a bunch of MISRA's rules offer little value for PC-based software and non-tiny processors. The point of MISRA is to improve quality of embedded software in the motor industry, to improve portability of code across platforms, and to reduce surprise errors from poorly understood corners of the C standard that you are more likely to encountered with embedded C compilers.

Rule 2.2 for example suggests that you don’t use // comments, which are not universally supported in the embedded world (IIRC they aren’t a C standard, but a C++ one). Rule 19.1 reduces the chance of linking against the wrong function (if you have two functions with the same name, in different source files), which eliminates a class of subtle bugs.

As you say, it depends on what you’re trying to accomplish – a bunch of MISRA’s rules offer little value for PC-based software and non-tiny processors.

]]> By: assistencia tecnica electrolux http://www.klocwork.com/blog/2010/03/misra-more-irrelevant-software-requirements-again/comment-page-1/#comment-2011 assistencia tecnica electrolux Mon, 05 Apr 2010 13:18:33 +0000 http://www.klocwork.com/blog/?p=942#comment-2011 good article, i will add my feeds. good article, i will add my feeds.

]]>