[SystemSafety] C for OSs

Olwen Morgan olwen at phaedsys.com
Sun Sep 15 21:25:28 CEST 2019


On 15/09/2019 16:13, Chris Hills wrote:

-<snip>-
>
> As Derek Jones said early on in this “Another way of looking at this 
> is as a statistical sampling problem. If the most heavily used OSs are 
> written in X, then X will experience the most faults.” So we should be 
> careful what, and how we are measuring these things.
>
-<snip>-

 >>> It depends on what things you count how you count them. Several 
instances of failure may all be due to a single copied fault. Then there 
is fault density, to take account of differing code sizes. The 
statistically inept can screw things up every bit as well as bad 
programmers in this area.


Olwen


PS: Also, a propos of what was snipped out of the above, I've never said 
you can make C as good as SPARK - only that if you are sufficiently 
obsessional, you can make C code quality approach SPARK levels - so I 
disagree slightly with Chris here.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20190915/d299ac2a/attachment.html>


More information about the systemsafety mailing list