This is the mail archive of the java@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: Non-synchronized StringBuffer

From: Anthony Green <green at redhat dot com>
To: tromey at redhat dot com
Cc: Adam Megacz <gcj at lists dot megacz dot com>, Java Discuss List <java at gcc dot gnu dot org>
Date: Mon, 26 Nov 2001 06:51:09 -0800
Subject: Re: Non-synchronized StringBuffer
Organization: Red Hat, Inc.
References: <87itc0dehz.fsf@creche.redhat.com> <m3wv0epptr.fsf@megacz.com> <873d328u62.fsf@creche.redhat.com>

Tom Tromey wrote:

> It isn't as easy as it sounds.  For one thing, a reference is passed
> to any methods invoked on it, and these methods might save `this' (for
> that matter, a constructor might save `this' somewhere).

We could annotate class files with this information.  It wouldn't be 
perfect, but my guess is that it would still be very useful (esp. with 
String and the like).

AG

References:
- Non-synchronized StringBuffer
  - From: Tom Tromey
- Re: Non-synchronized StringBuffer
  - From: Adam Megacz
- Re: Non-synchronized StringBuffer
  - From: Tom Tromey

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