[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: RFC: Strategy for integrating the Nana debugging library
From:       David Faure <faure () kde ! org>
Date:       1999-12-19 20:32:33
[Download RAW message or body]

On Sun, Dec 19, 1999 at 09:22:49PM +0100, Dirk A. Mueller wrote:
> On Son, 19 Dez 1999, Mirko Sucker wrote:
> 
> > - implement the kdebug-based message handler for Nana logging output and
> 
> Well, this sounds like inverse logik to me. From what I've read up to now,
> the Nana logs seems to contain the source file name and line from where the
> logging was called
Even when compiled without debug info ?

> It seems to be more reasonable to do the opposite - make kdebug a subset of
> nana. 

I think we should forget about making any relation between kdebug and nana.
They are two completely different things.
kdebug is for verbose debug output, just checking where I am and
what the values of some variables are.
nana is for assertions, and any other kind of checks.

The first one produces a lot of debug output, that's why we need
debug areas, some being off by default, whereas the second one produces
a message only when some check or assertion failed, and doesn't
need debug areas, nor really syslog IMHO.

Just my two cents.

-- 
David FAURE
david@mandrakesoft.com, faure@kde.org
http://home.clara.net/faure/
KDE, Making The Future of Computing Available Today

[prev in list] [next in list] [prev in thread] [next in thread]