This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Patch: MAXPATHLEN usage - PR21821

From: Tom Tromey <tromey at redhat dot com>
To: Bryce McKinlay <mckinlay at redhat dot com>
Cc: Per Bothner <per at bothner dot com>, David Daney <ddaney at avtrex dot com>, java-patches at gcc dot gnu dot org
Date: 02 Jun 2005 09:50:04 -0600
Subject: Re: Patch: MAXPATHLEN usage - PR21821
References: <429E3E31.4000503@redhat.com> <429E3F00.1070406@avtrex.com><429E40E4.2050506@redhat.com> <429E48D7.20404@bothner.com><m3ekblcz45.fsf@localhost.localdomain> <429F1C60.5010504@redhat.com>
Reply-to: tromey at redhat dot com

Bryce> Why couldn't StringBuilder do sharing with copy-on-write, like
Bryce> java.lang.StringBuffer does?

StringBuilder is unsynchronized, and StringBuilder.toString() doesn't
have "hand-off" semantics -- it keeps the data in the StringBuilder.
So, if you avoid copying there will be a window where the user could
potentially mutate a String.  There was a thread about this a while
back on classpath-patches.

Tom

References:
- Patch: MAXPATHLEN usage - PR21821
  - From: Bryce McKinlay
- Re: Patch: MAXPATHLEN usage - PR21821
  - From: David Daney
- Re: Patch: MAXPATHLEN usage - PR21821
  - From: Bryce McKinlay
- Re: Patch: MAXPATHLEN usage - PR21821
  - From: Per Bothner
- Re: Patch: MAXPATHLEN usage - PR21821
  - From: Tom Tromey
- Re: Patch: MAXPATHLEN usage - PR21821
  - From: Bryce McKinlay

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]