In the last post, we recapped the emergence of C as the dominant programming language for embedded automotive systems. From its roots in Unix in the early 1970s up to its gathering criticism around its relative eccentricities, this platform has greatly matured over the years. We also covered the emergence of safety standards in ISO 26262 and IEC 61508, as well as the launch of MISRA C.
In this post, we’ll examine the scope that C gives a developer to generate problematic code. We’ll also outline the kind of rigor and mindset necessary to safely harness the power of the language and to avoid those conflicts of intent and execution that have garnered C some critics, from a safety standpoint, over the last few decades.
from DZone.com Feed https://ift.tt/2tDGwGc
No comments:
Post a Comment