&& is subject to shortcut evaluation, so the second test will not run

if the first failed.  The ultimate outcome is the same, but using &
instead ensures that, when in verbose mode, we also get output from
the second test.
This commit is contained in:
Dag-Erling Smørgrav 2014-07-19 15:34:49 +00:00 committed by des
parent 063197ed28
commit c658232e3e

View file

@ -144,7 +144,7 @@ t_strlcat(char **desc CRYB_UNUSED, void *arg)
}
ret = t_compare_sz(t->sz, sz);
if (t->out != NULL)
ret = ret && t_compare_str(t->out, buf);
ret &= t_compare_str(t->out, buf);
return (ret);
}