This fixes a cosmetic precedence bug in the tests along with some type warnings.
It also adds a dummy cast to the CHECK macro to avoid hundreds of statement with no effect warnings on compilers that warn about such things.
This fixes a cosmetic precedence bug in the tests along with some type warnings.
It also adds a dummy cast to the CHECK macro to avoid hundreds of statement with no effect warnings on compilers that warn about such things.
This fixes a cosmetic precedence bug in the tests along with some
type warnings.
It also adds a dummy cast to the CHECK macro to avoid hundreds
of statement with no effect warnings on compilers that warn about
such things.
It appears that VERIFY_CHECK is only used with a side effect once in the codebase. I somewhat question the wisdom of using a side-effect preserving macro elsewhere... simply because it'll be a bunch of dead code for the compiler to eliminate (which non-optimizing compilers won't).
Perhaps we could split VERIFY_CHECK into a side effect preserving and one not?