assert, NDEBUG and you

[Henri Verbeet]

On 26 October 2015 at 02:28, Daniel Santos <daniel.santos at pobox.com> wrote:
> In light of this, I'm thinking that we may need a standard wine macro for
> asserts that we *really* only want when we're making changes and debugging
> and are activated by -DDEBUG or some such. Many of the asserts I use aren't
> something that I would ever expect to fail after development and testing is
> completed and shouldn't be in release, but can fail when me or somebody else
> makes a change or uses the function incorrectly. Hot code paths and inline
> functions are other examples of where such an assert would be useful when
> developing, but we would not want to pay for it in a release build.
>
> Thoughts?
>
I'd put something like that inside an ERR_ON block.