On Fri, 24 Jul 2015, nolan wrote:
Asserts are sometimes compiled out, so the redundant check is necessary. The optimizer will cull it if asserts are enabled, so it doesn't hurt the generated code.
Note that in Quagga asserts should always assert. We redefine assert to our own function (zassert.h included generally via zebra.h) precisely because we rely on it.
Sounds like coverity 'knows' the traditional assert() and assumes it? (I think I've run into that before with Coverity issues, I vaguely recall).
regards, -- Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A Fortune: "Even more amazing was the realization that God has Internet access. I wonder if He has a full newsfeed?" (By Matt Welsh) _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
