[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: assert() vs. return(error)

From: Daniel Berlin <dberlin_at_dberlin.org>
Date: 2006-02-14 17:36:53 CET

On Tue, 2006-02-14 at 16:21 +0000, Julian Foad wrote:
> Daniel Berlin wrote:
> > On Tue, 2006-02-14 at 15:13 +0000, Julian Foad wrote:
> >>Stuart Celarier wrote:
> >>
> >>>The rest of the C world uses the assert macro to compile assertions in
> >>>to the debug version, and to remove assertions in the release version.
> [...]
> >>
> >>You're over-simplifying.
> >
> > He's also wrong.
> > GCC, for example, specifically keeps asserts on in the release builds
>
> Does it? <searching...> Aaargh! I've just spent twenty minutes searching for
> any documentation that says that GCC does that. Now I realise you mean the GCC
> developers keep asserts on when building GCC.

Yes. All packaged gcc releases are built with asserts enabled.

We can't control whether people pass -DNDEBUG, etc, or not
>
> Yes, sure, some people do that.
>
> - Julian
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 14 17:38:06 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.