On Thu, May 22, 2014 at 4:31 PM, Andres Freund <and...@2ndquadrant.com> wrote: > Since there seem to be multiple static checkers (coverity, clang > checker) having problems with assert_enabled can we just optionally > disable it? > I am thinking of replacing it by a AssertionsEnabled() macro which then > is unconditionally defined when DISABLE_ENABLE_ASSERT is defined.
Uh, probably. But I think you need a better name; specifically, one that doesn't contain two words which are antonyms. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
