| Re: [AD] TRACEs in xkeyboard.c |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] TRACEs in xkeyboard.c
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Thu, 22 Sep 2005 15:20:32 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=Fypkw1vNdw63R2ZVQ/+/fmcscWgCGVo81iHHa6bk8kmqeSIcWKb9m8tAh8IqiU7XXUf2de3e6P1X3zhqjnmEfgQ5+2zTrm2NhI9X59loiRuBU4J+TDybCTc97RcJkCzS2ng9SQW7B1EVxlj7YZyANd1nW0wkl9/6TX2kV1ncWyQ=
On Thursday 22 September 2005 03:05 pm, Evert Glebbeek wrote:
> > But since all other parts of Allegro have almost no runtime information
> > at all, and we have no way to have different debug classes and levels
> > (something we should add after 4.2), and user code also might use TRACE
> > and allegro.log, I wonder if those TRACE calls should be removed for
> > 4.2.0..
>
> Nah, why bother? Just leave them.
Because it unnecesarilly bloats allegro.log, getting in the way of a user's
TRACE statements. Isn't there debugmode verboseness levels? At level 2, or
something higher than the default I wouldn't really mind. At the very least,
it'd be nice if the lines were prepended with something like "Allegro:: ".
When you have multiple Allegro add-on libs, along with Allegro itself, all
writing to the same allegro.log, along with your own program, it gets very
confusing real fast.