I had some additional comments, but because I'd already created a patch after reading
the first response, I've replicated the discussion within Bugzilla (so I could attach
the patch regardless of the final decision):
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23092
Please visit the bug and page down a bit :)
-AMT
-----Original Message-----
From: Stephen Colebourne [mailto:[EMAIL PROTECTED]
Sent: Wed 9/10/2003 2:34 PM
To: Jakarta Commons Developers List
Cc:
Subject: Re: [collections] MapUtils.debug/verbosePrint thread safety
I like the System.out theory. Its probably unintentional, but it true. So
only a documentation patch is required then...:-)
Stephen
----- Original Message -----
From: "Janek Bogucki" <[EMAIL PROTECTED]>
To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]>
Sent: Wednesday, September 10, 2003 11:12 PM
Subject: Re: MapUtils.debug/verbosePrint thread safety
<SNIP snipper="AMT" />
>
> These methods are synchronized so are currently thread safe.
>
> public static synchronized void verbosePrint (...)
>
> public static synchronized void debugPrint (...)
>
> I would guess that a second intentional benefit of the synchronization
> is to prevent overlapping invocations writing to System.out at the same
> time.
>
> -Janek
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
