Non-synchronized StringBuffer

Fri Nov 9 08:26:00 GMT 2001

Tom Tromey <tromey@redhat.com> writes:
> I didn't try stack-allocating the StringBuffer object itself. This is
> possible, but it was more work than I was willing to do tonight.

I'm curious -- will gcj stack-allocate an object whose lifetime is
obviously no longer than that of the function allocating it? (ie no
references to the object are passed to other functions, nor are any
returned)?
 - a