>The first expert, who did not see any of Toyota's source code, told the jury that others who had examined the code had determined that there were approximately 10,000 global variables in Toyota's one million lines of code. He told the jury that this was an indicator that "Toyota's source code is of poor quality." He further told the jury that "global variables are evil" and the "academic standard is there should be zero" global variables. He then said to the jury: "Well, I know that the right answer academically is zero. And in practice, five, ten, okay, fine. 10,000, no, we're done. It is not safe, and I don't need to see all 10,000 global variables to know that that is a problem."

>The second expert, who examined Toyota’s code, told the jury that he found more than 80,000 MISRA C violations in Toyota’s one million lines of code. Both experts told the jury that this was an indication that Toyota’s software was of poor quality.

>Both experts also testified that the number of MISRA C violations in a body of code is a predictor of the number of bugs in the code. They told the jury that for every 30 MISRA C violations, one can expect an average of three minor bugs and one major bug.

>The first expert told the jury that based on the number of MISRA C violations found in Toyota’s code, that code would be expected to have roughly 2,717 major bugs (81,514/30). He also told the jury that, based on this metric (but without actually seeing Toyota’s source code), Toyota “has far, far too many bugs.”

Yep, C programmers write good code have no need for the type checks or overheads of C++. This is why C is the choice de jure in the automobile industry.