On Wed 17.Mar'10 at 15:03:38 +0100, Tamas TEVESZ wrote: > On Wed, 17 Mar 2010, Carlos R. Mafra wrote: > > > Having said that, I have a _unfinished_ patch (in fact two) to address > > this very same code duplication but I also wanted to get rid of lots of > > i'm wondering, is there really a need for "debug levels"? in an ideal > world, wm should be completely silent with all debug prints enabled, > and it's not like it is constantly receiving various things "from the > outside", ie. it is a pretty closed system all in itself. > > when you concentrate on some stuff to be fixed, you either want debug > prints, or not, but it's not like "this pixel in the background image > is bright yellow, action stations, action stations!!" and "oh, you > turned on sloppy focus, let me pat you on the back in the form of a > MESSAGE-level message". > > i think. > > what would be the use case for debug levels?
I guess I will remove all the #ifdef DEBUG constructs, as they are uglifying the code for no good reason. I think they made sense for whoever was working on those at some point in time, but not now. That also avoids the path I was trying to follow with the printw(WDEBUG, foo) stuff. -- To unsubscribe, send mail to [email protected].
