tag:blogger.com,1999:blog-5704901458470135557.post3935680096768467252..comments2023-09-19T05:59:21.189-07:00Comments on Code Integrity Blog: Power of 10 for Safety Critical CodeAndyhttp://www.blogger.com/profile/06705630945588101293noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5704901458470135557.post-85352105379753188622010-11-01T18:22:21.411-07:002010-11-01T18:22:21.411-07:00I'm reading those rules and not sure if they a...I'm reading those rules and not sure if they are really good - or even possible to follow in some cases. Mind you, I'm very serious about safety - but those rules seem to me doubtful.<br /><br />For example, rule 1 proposes to get rid of setjmp and longjmp. It's possible to implement exceptions and coroutines without them - or even write programs without exceptions and coroutines - but it may be more cumbersome, thus violating the purpose of rules. Or rule 3 proposes to not use the dynamic memory management other than in initialization parts. Some tasks may become impossible to solve with this limitation, because the amount of memory couldn't be known in advance..https://www.blogger.com/profile/00587777695322622118noreply@blogger.comtag:blogger.com,1999:blog-5704901458470135557.post-72810875437286256672010-09-15T16:06:56.080-07:002010-09-15T16:06:56.080-07:00Yep, Holzmann's always worth reading. He got ...Yep, Holzmann's always worth reading. He got it down to 10 rules, you picked 1. A while back I had picked that same one, and added another, to make a <a href="http://talkaboutquality.wordpress.com/2006/07/09/very-short-coding-standard/" rel="nofollow">Very Short Coding Standard</a>.Anonymousnoreply@blogger.com