From kde-core-devel Tue Dec 21 18:58:19 1999 From: David Faure Date: Tue, 21 Dec 1999 18:58:19 +0000 To: kde-core-devel Subject: Re: RFC: Strategy for integrating the Nana debugging library X-MARC-Message: https://marc.info/?l=kde-core-devel&m=94580272827687 On Tue, Dec 21, 1999 at 06:43:16PM +0100, Mirko Sucker wrote: > David Faure wrote: > > > > 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 ? > Yes, it uses preprocessor statements. > Nana lacks one main feature of kdebug, the debug areas. So there are two > ways of integrating: > ° rewriting a part of nana or wrapping it to support areas - lots of work > ° redirecting nana messages in the kdebug buffers - nearly no work I'll let you or somebody else do that - I don't enough about nana > BTW, adding file and line number to kdebug statements is a matter of seconds Done for kDebug. But it's not as simple as you suggest. It only works with function calls, not with macros. Unless we restrict to gcc only. > Nana remains independant from kdebug. Its message handler is defineable, > that is what I will do. We need integration of it in KDE anyway. > It is a matter of taste, in the end. We may simply forget about the > messages from nana, too. Yup. -- David FAURE david@mandrakesoft.com, faure@kde.org http://home.clara.net/faure/ KDE, Making The Future of Computing Available Today