* On Thu, 15 Jul 2010, Michael Stefaniuc wrote:
Saulius Krasuckas wrote:
TRACE_ONCE probably could help in some cases too. There I see another
I fail to see how TRACE_ONCE could make any sense. TRACE is used to trace the important parts of the code flow. Just printing a TRACE once is less than helpful; it is waay better to not print the TRACE at all.
I was in a hurry a bit and I am persuaded now :), thanks.
Of course TRACE_ONCE should be defined for symmetry and preventing somebody wasting time to send a patch with an implementation for it. Too bad that Alexandre is too nice else that would be something like:
#define TRACE_ONCE TRACE_ONCE_Misguided_developer_detected
I am away from development now, but you will never know :). Such define sounds OK. Or has it already been decided on IRC to not exist?
S. PS: Congrats to all the folks for Wine-1.2!