Re: [evolution-patches] debugging for GW messages
- From: Not Zed <notzed ximian com>
- To: Rodrigo Moya <rodrigo ximian com>
- Cc: JP Rosevear <jpr ximian com>, evolution-patches lists ximian com
- Subject: Re: [evolution-patches] debugging for GW messages
- Date: Mon, 29 Mar 2004 23:50:18 +0800
ahaaah, yeah, it sounds beneficial, although i did misread it the first
time. But its really up to you, since i wont be debugging it :)
On Mon, 2004-03-29 at 16:54 +0200, Rodrigo Moya wrote:
> On Thu, 2004-03-18 at 09:00 +0800, Not Zed wrote:
> > I think ... you should still make it a compile time option. Even if it
> > isn't run, it makes the code bulkier and slower (sometimes by quite a
> > lot - the g* assert stuff can be a significant overhead). And it
> > shouldn't be needed to be compiled in forever.
> so, should I leave it as it was, having --enable-debug enable all g_*
> checks, and no debug stuff at all if not specified?
> What I removed was:
> dnl --- Debug
> [ --enable-debug=[no/yes] turn on debugging [default=no]],
> if test "x$enable_debug" = "xyes"; then
> DEBUG_CFLAGS="-DG_DISABLE_ASSERT -DG_DISABLE_CHECKS"
> so, we could have it set the -DG_DISABLE/ENABLE flags to CFLAGS instead of
> DEBUG_CFLAGS, thus working for all components at once.
> does that sound ok?
] [Thread Prev