[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: xassert in dispextern.h
From: |
Miles Bader |
Subject: |
Re: xassert in dispextern.h |
Date: |
Wed, 2 Mar 2005 07:50:53 +0900 |
The right answer is to change those xasserts (and _only_ those) which
cause a problem or test something silly or are insanely inefficient
[99% are quite efficient] to use some other macro, like "gdassert" or
something, and make gdassert dependent on GLYPH_DEBUG.
[I should note that the thing which caused me to originally enable
xassert by default is that it caught (I always have it enabled) a case
where iterator stacks could overflow -- something that otherwise would
just result in rare, hard to debug, memory corruption.]
-Miles
- xassert in dispextern.h, David Kastrup, 2005/03/01
- Re: xassert in dispextern.h, David Kastrup, 2005/03/01
- Re: xassert in dispextern.h, David Kastrup, 2005/03/01
- Re: xassert in dispextern.h, Jason Rumney, 2005/03/01
- Re: xassert in dispextern.h, David Kastrup, 2005/03/01
- Re: xassert in dispextern.h, Kim F. Storm, 2005/03/01
- Re: xassert in dispextern.h, David Kastrup, 2005/03/01
- Re: xassert in dispextern.h,
Miles Bader <=
- Re: xassert in dispextern.h, Luc Teirlinck, 2005/03/01
- Re: xassert in dispextern.h, Miles Bader, 2005/03/01
- Re: xassert in dispextern.h, David Kastrup, 2005/03/01
- Re: xassert in dispextern.h, Miles Bader, 2005/03/01
- Re: xassert in dispextern.h, David Kastrup, 2005/03/01
- Re: xassert in dispextern.h, Kim F. Storm, 2005/03/02
- Re: xassert in dispextern.h, Miles Bader, 2005/03/02
- Re: xassert in dispextern.h, Kim F. Storm, 2005/03/02
- Re: xassert in dispextern.h, Andreas Schwab, 2005/03/02
- Re: xassert in dispextern.h, Kim F. Storm, 2005/03/01