On Saturday 09 April 2005 03:30 pm, Daniel Kristjansson wrote: > There are three solutions as I see it: > 1/ Construct the verbose string completely outside of the verbose lock. > The problem with this is it makes the verbose macro take longer to > execute.
Right, would: ostringstream blah; blah << dtime << " " << args; mutex.lock(); cout << blah << endl; mutex.unlock(); Really take that much extra time? > 2/ Examine every VERBOSE macro with redirects in it and either check if > it is calling a blocking function, or just transform it to use > QString().arg().arg().. Problem: lots of developer time.. Lots and lots.. So, not going to happen. =) > 3/ Disable verbose locking in release builds. This would work, too. Isaac _______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
