[reSIProcate] More problems with `assert'

[Jason Fischl]

On 11/6/06, Daniel Pocock <daniel at readytechnology.co.uk> wrote:
>
>
> There is also a side issue on the use of assert: perhaps it would be
> useful to have a configure option at compile time to decide if we want
> to use assert() in a strict manner, or we would prefer to use `lazy'
> alternative code that just logs an error and tries to carry on where
> genuinely feasible.
>
> This already exists. If you build with optimization CODE_OPTIMIZE=1, the
asserts are compiled out. Only the debug builds have assertions enabled.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20061106/eb39226f/attachment.htm>