Osvaldo Doederlein wrote:
Looks like good stuff. And it remembers me from another old issue:
patterns of code that demand data copying that could often be avoided.
Every StringBuffer/StringBuilder is ultimately consumed by a toString()
invocation to produce the result String, and in 99% of all
Rémi Forax wrote:
Le 21/11/2009 07:48, Paulo Levi a écrit :
But i'm wondering why there isn't a global jvm system option for the
new Thread(runnable).start() to perserve stack traces at least until
the start method.
You don't need the VM for that, something like that should work:
public cla
2009/11/20 Osvaldo Doederlein :
> Hi Goktug,
>
> Looks like good stuff. And it remembers me from another old issue: patterns
> of code that demand data copying that could often be avoided. Every
> StringBuffer/StringBuilder is ultimately consumed by a toString() invocation
> to produce the result S
Le 21/11/2009 07:48, Paulo Levi a écrit :
But i'm wondering why there isn't a global jvm system option for the
new Thread(runnable).start() to perserve stack traces at least until
the start method.
Seems like a no brainer so that tools (like the netbeans debugger) can
find where the misbehaving
