I recently noticed that the current implementation of the debugPrint and verbosePrint 
methods in MapUtils is not thread safe - in fact, these are the only items that are 
not thread safe because the indentation state for the output is preserved in a static 
variable.  
 
I think it would be fairly simple to make this thread safe, but it would require a 
change to the signature of a protected member function printIndent(PrintStream out) -> 
printIndent(PrintStream out, int indentDepth).  I'm not really clear as to why this 
method is protected rather than private (can anyone clarify?).  Does it need to be 
protected?  
 
Looking forward to input from others.
-AMT  
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to