Role of sequence points not being the point – and how MISRA helps

This article is about tangental discussions and how the C language can get even the most seasoned engineers off centered, and how using a good MISRA-C tool can help get us back on point. I joined this discussion a little bit late in the LinkedIn "Embedded C Programming" group: "Role of sequence points in deciding the value of...

Continue reading →

Soundy is the new Truthiness (when not MISRA-C 2012)

Static Code Analysis (SCA) technology has many flavors, and words can take on different nuances even though they have a specific meaning within mathematics for describing logical properties. SCA that enforces MISRA-C 2012 and properties of source code itself are an exception. This is because analysis of source code can only infer what the implementation will...

Continue reading →

An example why we need good tools

MISRA-C is only as good as the tools that enforce it and the activities of code inspection employed. Both go hand in hand as the ability of the tool to save developer review time as opposed to wasting time, is critical in making rigorous manual review practical. This just posted on a Friday evening to the MISRA-C/C++...

Continue reading →

Run time checks straw men and overhead vs. MISRA-C (Part II)

Continuation of discussion on run-time checking, or lack thereof in C and my advocacy of MISRA-C prevention being a key past of any solution. Continued from Part I. By my last count this thread was up to 237 responses. I am beginning to think  this idea of summarizing discussion thread conversations may have value.  The Signal to Noise ratio on these...

Continue reading →

Run time checks straw men and overhead vs. MISRA-C (part I)

As I mentioned in this post, there are many conversations I find myself contributing to, mostly about software engineering systems the right way. For C, this means rigorous code inspection prefaced by automatic enforcement of C subsetting standard, such as MISRA-C 2012 which focuses on prevention first, cure second. So here's my first step on a...

Continue reading →

On Being Very Loud and Clear with Systems Software Quality

Veriloud is about software verification beyond testing.  Actually before, during, above and beyond. Testing is only half the story with full verification. In fact testing is never enough.  Especially if the system is developed with a programming language called C, which is pretty much the majority of systems developed and will be develop in our lifetime.  So, I will very...

Continue reading →