> > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On > > Behalf Of Blasche Alexander > > Sent: Friday, August 23, 2013 2:00 PM > > To: Robin Burchell; [email protected] > > Cc: Poenitz Andre > > Subject: Re: [Development] Tracing Qt > > > > Hi Robin, > > > > I am not sure whether you are aware of > > http://qt.gitorious.org/qtplayground/qlogger > > > > It is pretty much what you describe. It was even close to a merge into > > qtcore > > already (only rejected due to feature freeze). It gives you a complete API > > including ways to integrate with qDebug/qWarning, runtime activation, little > > to no overhead when deactivated and there was reasonably broad > > agreement already. Also see: > > > > http://lists.qt-project.org/pipermail/development/2012- > > December/008886.html > > > I actually started a patch back in January that I just revived: > > https://codereview.qt-project.org/#change,44430 > > There are certainly still rough edges, but IMO we should be able to > re-use some of it for a hypothetical tracing solution, too. The actual > data flow will be different from the logging case (you don't want to go > through QMessageLogger etc, and don't want to convert everything to a > QString in the first place), but the idea that you can > activate/deactivate categories at runtime through different means is the > same. > > Regards > > Kai
Hello, Just to throw another idea out there: you may be interested in checking out AspectC++ (http://aspectc.org/). One drawback is that you must recompile to update the pointcuts of the logger, however the regular expression-like syntax is very nice (plus you don't have to modify the Qt source code itself). Best, Alfonso _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
