<?xml-stylesheet type="text/xsl" href="https://community.element14.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>It&amp;#39;s dangerous to go alone! Take MISRA-C</title><link>/members-area/personalblogs/b/blog/posts/it-s-dangerous-to-go-alone-take-misra-c</link><description>This post was written by chriswhite . In last article I posted here (“ Be Excellent to Each Other ”) I wrote about how a little compassion and respect for the future can make a big difference for code quality. I purposely avoided many specifics to...</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: It&amp;#39;s dangerous to go alone! Take MISRA-C</title><link>https://community.element14.com/members-area/personalblogs/b/blog/posts/it-s-dangerous-to-go-alone-take-misra-c</link><pubDate>Mon, 23 May 2016 21:29:19 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:871b0dd4-ccc1-4130-8598-6ce85c46fd34</guid><dc:creator>e14 Contributor</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Actually the MISRA C rules are not as comprehensive as some believe. In fact they came about almost by accident. In spring 1997 software engineers at the then Austin Rover Group (ARG) sent a draft C coding standard for review by Programming Research (PRL). At the time I was PRL&amp;#39;s senior consultant and was asked to undertake the review. I considered the rules in the ARG draft inadequate and suggested a replacement set. The review report was duly sent off to ARG and PRL got paid for the review. A few months later ARG sent a further document to PRL. It had my recommended rules in it but it was marked not as a revised ARG standard but as version 0.1 of the MISRA C rules. Version 1 of MISRA C slightly weakened those rules but they were essentially based on what I had suggested in my three-day review. All MISRA did was to write accompanying text around them.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;I never intended what I wrote to be used in that way. The rules I proposed were what I considered a bare minimum (and they have since been weakened further). MISRA C is not IMO the great accomplishment that some represent it as. I no longer participate in the MISRA C Working Group because as far as I can see, it is unable collectively to demonstrate a robust grasp of what language subsetting is actually for, leave alone how it should be done. It is in fact technically quite straightforward to define the language restrictions in a metalanguage such that parser generation techniques could be used to generate a checker automatically from the metalanguage rules. My impression is that a certain tool vendor represented on the working group found this rather alarming and wanted to suppress it. This, of course, is one of the conflicts of interest that can always arise in standardisation by sectoral bodies.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Even the best MISRA C checkers can&amp;#39;t match the quality of checking that, say, the SPARK examiner does for Ada. That&amp;#39;s because SPARK was designed with a specific set of verification processes in mind. The SPARK tools can now check over 100,000 lines of Ada overnight to *prove* freedom from run-time errors in all possible executions. With the right tools you can do *almost* as good for C as SPARK can do for Ada, but you need a language subset draconianly stricter than what I originally suggested. You also need proof annotations tailored to the verification algorithms you need to use. I see no clear sign that the MISRA C Working Group collectively acknowledges this - and much suggestive evidence that some commercial interests want to keep it that way.&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=20706&amp;AppID=293&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: It&amp;#39;s dangerous to go alone! Take MISRA-C</title><link>https://community.element14.com/members-area/personalblogs/b/blog/posts/it-s-dangerous-to-go-alone-take-misra-c</link><pubDate>Sat, 16 May 2015 12:21:44 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:871b0dd4-ccc1-4130-8598-6ce85c46fd34</guid><dc:creator>e14 Contributor</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;I was not having such deep knowledge for working on PC-Lint. With the help of this post I came to know various things about this software. Thanks for sharing.&lt;a class="jive-link-external-small" href="http://www.lightspeedgmi.com/" rel="nofollow ugc noopener" target="_blank"&gt;More such information&lt;/a&gt; about marketing surveys is available here .&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=20706&amp;AppID=293&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>