JDK-4705328 : Add CharSequence constructor to StringBuffer
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.lang
  • Affected Version: 1.4.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2002-06-20
  • Updated: 2017-05-16
  • Resolved: 2003-05-16
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availabitlity Release.

To download the current JDK release, click here.
5.0 tigerFixed

Name: jl125535			Date: 06/20/2002

This issue is related to bug 4230604, which discusses making
String clonable.

Not only is StringBuffer copy-able like String, but it is also
writable.  So sharing a StringBuffer is more dangerous than sharing
a String, since a change to the original appears in the copy -
and vice versa.  Supporing StringBuffer.clone() would avoid
this problem more elegantly than the 
StringBuffer(stringBuffer.toString()) approach.

(Review ID: 153790) 

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b07

EVALUATION We will consider adding a new constructor StringBuffer(CharSequence) in Tiger which will address this issue. ###@###.### 2003-02-04