Sujet : Re: Code guidelines
De : vir.campestris (at) *nospam* invalid.invalid (Vir Campestris)
Groupes : comp.lang.cDate : 01. Oct 2024, 12:41:16
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vdgjkc$2mhpi$1@dont-email.me>
References : 1 2 3 4 5 6
User-Agent : Mozilla Thunderbird
On 03/09/2024 17:23, Thiago Adams wrote:
<snip>
but...maybe, is better to be a little redundant here?
I think I prefer to leave "obj->member1->member2 && " even if I know
it should not be null.
if (obj->member1 &&
obj->member1->member2 &&
obj->member1->member2->member3)
{
}
I think I'd prefer to _omit_ the check that obj->member1->member2 isn't null.
If the code is running correctly that check will never trigger, and is redundant, and will slow things slightly.
But if the code is not running correctly it will conceal the bug by preventing the crash.
But circumstances may vary. You probably don't want to crash an autopilot if at all possible!
Andy