Am 04.01.10 16:52, schrieb Gabriel M. Beddingfield: > But otherwise it looks nice. Now you just need to go through and > replace stuff like this: > > INFOLOG( QString( "Pan: %1L, %2R" ) > .arg(pan_L) > .arg(pan_R) ); > > With stuff like this: > > INFOLOG( "Pan: %.4gL %.4gR", pan_L, pan_R ); > > In the 842 places that it occurs. :-) Hi Jérémy and Gabriel!!
I've just read all the other mails concerning the logger class and a few questions popped out of mind.. If i understand it correct, the new proposal uses something like INFOLOG( const char* , .. ) instead of INFOLOG( const QString ). Why is this faster? Is it just the fact the we don't have to pass the QString by value, which results in an expensive call to the copy constructor ? If my assumption is correct, we have to do now some casts ( QString -> char ) in the gui / audio threads *before* we call the logger, but we save the copy constructor calls. Is this faster for the non-logger threads? I'm very unexpierenced when it comes to all this low-level speed considerations, but i'm trying to learn :) And a last, related Question: You mentioned speed-tests.. How do you measure the speed of those operations? Are you using dedicated profiling tools or C internals like those out of time.h? I hope that's not asked too much in one mail :) Thanks, Sebastian ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Hydrogen-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
