Sujet : Re: Code guidelines
De : Keith.S.Thompson+u (at) *nospam* gmail.com (Keith Thompson)
Groupes : comp.lang.cDate : 04. Sep 2024, 08:22:45
Autres entêtes
Organisation : None to speak of
Message-ID : <87y147zxve.fsf@nosuchdomain.example.com>
References : 1 2 3 4 5 6 7
User-Agent : Gnus/5.13 (Gnus v5.13)
David Brown <
david.brown@hesbynett.no> writes:
[...]
Before you put any check in code, think about the circumstances in
which it could fail. If there are no circumstances, it is redundant
and counter-productive.
[...]
One thing to consider is that if a check can never actually fail the
recovery code *cannot be tested* (and you can't get 100% code coverage).
p = NULL; // assume p is not volatile
if (p != NULL) {
do_something(); // can never execute this
}
Of course not all such cases are so easily detectible (
-- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.comvoid Void(void) { Void(); } /* The recursive call of the void */