21 Feb
2011
21 Feb
'11
2:58 p.m.
I agree with Amine. The current debug log situation is not optimal.
Important messages can get missed and even finding your own additional
DPRINTs can be hard sometimes. I already use DPRINT1("#############
!!!!!!!! Message bla bla !!! #######\n") to be able to find my debug
prints ;-)
We have tons of hacks in our code, if each of them would do a dprint, ...
We should rather try to cleanup useless debug messages.
Timo