On Wed, 22 Nov 2000, Sam TH wrote:
> On Wed, Nov 22, 2000 at 09:45:38PM +0400, Vlad Harchev wrote:
> > On Wed, 22 Nov 2000, Sam TH wrote:
> >
> > > On Wed, Nov 22, 2000 at 08:39:01PM +0400, Vlad Harchev wrote:
> > > >
> > > > Hi,
> > > >
> > > > I'm curious whether release build will be compiled with debug enabled or
> > > > not. I think that in order to improve perceived quality of AW all asserts
> > > > should be turned to noops (that don't ask for confirmation and don't
> > > > terminate AW). Otherwise I think AW will get bad reputation terminating each
> > > > time excessive assert is violated.
> > > >
> > > > What do you think about this?
> > >
> > > Binary releases never have debug options enabled. Therefore, no one
> > > who uses a binary release will see the asserts.
> >
> > Will AW just terminate if assert if violated or it will just ignore assertion
> > violation (2nd is much more preferred IMO)?
>
> The relevant code from ut_assert.h
>
> # ifdef NDEBUG
>
> // When NDEBUG is defined, assert() does nothing.
> // So we let the system header files take care of it.
>
> # include <assert.h>
> # define UT_ASSERT assert
>
> It does nothing.
Thank you for info. I was for some reason sure that UT_ASSERT calls abort in
non-debug builds (oh my corrupted memory :) and was so sure that I didn't try
to check what UT_ASSERT expands to.
Best regards,
-Vlad
