Community
Participate
Working Groups
Write a clean up to convert StringBuffer usage to StringBuilder
for real, you'd need to do analysis to see if the buffer can escape the current thread. if yes, don't convert - you're risking race conditions (StringBuilder is unsynchronized). (BTW, a similar refactoring would convert Vectors to ArrayLists - a similar concurrency problem arises) An easy approximation is to check if the buffer can live longer than the current method. Most don't.
Sorry, has to wait post 3.2
This is fixed in 3.4M4, isn't it?
Oops, sorry, I misunderstood the description. Bug 36350 is something else.
*** Bug 328354 has been marked as a duplicate of this bug. ***
duplicated/implemented by Bug 572261 please close this
*** This bug has been marked as a duplicate of bug 572261 ***