Paolo,
Look at this bug evaluation
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6219959 to get further
information about what Tom told you yesterday.
I'm afraid that there is nothing to do here... because an optimization based
on buffer-sharing + copy-on-write has several problems (although
Paulo Levi wrote:
Since CharSequence is obviously flawed in that it doesn't allow
efficient read-only views because of a missing method, there are various
methods in the jdk where a stringbuilder/buffer is built, populated and
then toString()-ed and left to be garbage collected. I'm seeing plac
