This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgcj/21869] We should to use StringBuilder instead of StringBuffer where appropriate.
- From: "tromey at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 2 Jun 2005 04:59:58 -0000
- Subject: [Bug libgcj/21869] We should to use StringBuilder instead of StringBuffer where appropriate.
- References: <20050601232446.21869.daney@gcc.gnu.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From tromey at gcc dot gnu dot org 2005-06-02 04:59 -------
See the follow-on discussion on java-patches.
StringBuilder requires a copy of the data;
gnu.gcj.runtime.StringBuffer does not. The latter could
be made vm-independent and used throughout Classpath.
The thread is here:
http://gcc.gnu.org/ml/java-patches/2005-q2/msg00606.html
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Last reconfirmed|0000-00-00 00:00:00 |2005-06-02 04:59:57
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21869