On 08/07/2014 11:13 AM, Tom Breton (Tehom) wrote: > Ted, I noticed you changed the debug printing to go to std::cerr.
Yeah, I couldn't think of anything better. > Is there some way we can handle what you need thru the RG_DEBUG idiom? Or > perhaps some way to have the best of both? I like to have two things: 1. Debug output that is present while I'm debugging, but always committed turned off so it doesn't get in anyone else's way. For this, I went with RG_DEBUG and RG_NO_DEBUG_PRINT to turn it off when I commit. I saw in other places #ifdef being used, but that's pretty cumbersome. 2. Debug output for error situations to help users troubleshoot. This would always be enabled, for a debug build anyway. For this, I went with std::cerr since RG_NO_DEBUG_PRINT would have no effect on it. (Neither would a release build for that matter. So, it's a bit extreme.) It would be nice to have an RG_ERROR that acts like RG_DEBUG, but isn't affected by RG_NO_DEBUG_PRINT. I didn't notice anything like that in Debug.h. (Qt has qDebug() and qWarning() which I think roughly correspond to what I would use.) But this is just the way I work. I wouldn't impose this on anyone else. Though I will admit that the deluge of RG_DEBUG output during a run does make it more difficult for me to get my work done. I would love to have a "Please don't commit live RG_DEBUG statements" rule. But I've mentioned it in the past, and the idea met with some resistance. Ted. ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
