From kde-core-devel Tue Dec 21 19:01:10 1999 From: David Faure Date: Tue, 21 Dec 1999 19:01:10 +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=94580289827788 On Tue, Dec 21, 1999 at 06:37:15PM +0100, Mirko Sucker wrote: > David Faure wrote: > > > This is mainly to support code not coming from KDE CVS. > > Huh ? > > Didn't get that. Which code ? > None, currently. But if we include kdebug and nana, it makes sense to > redirect messages from nana to kdebug. Non-CVS apps might use nana, and > would integrate well (maybe this is a better explanation of the same > idea). Ok, fine with me. [Although there is still the issue of non-gcc compilers] > > Ok. This means I can do the changes I suggested for kdebug, right ? > > (Mainly moving the dialog box to a separate app, providing > > default values for libs debug areas, and removing the first > > arg from the API [turned into the function name itself]). > > This looks independent from nana. > I think so. If you introduce some new debug areas, could you add a > general one, too? There has always been one. It's numbered 0. And shows the instance name. And now it's even not necessary anymore to specify 0 for apps that don't want debug areas. See kdebug.h for the new API. -- David FAURE david@mandrakesoft.com, faure@kde.org http://home.clara.net/faure/ KDE, Making The Future of Computing Available Today