View source for Talk:ScalarNext/Version History

It seems that when an object is allocated in a function, and never escapes that, Java would replace the allocation to stack if the reference is not modified, which means Java would not reuse previously allocated memory for new objects in this case. 

e.g. 

<syntaxhighlight>
void stack() {
  Point2D.Double a = new Point2D.Double(0, 0);
  a.setLocation(1, 1);
}
</syntaxhighlight>
<code>a</code> could be allocated on stack, while

<syntaxhighlight>
void heap() {
  Point2D.Double b = new Point2D.Double(0, 0);
  b = new Point2D.Double(1, 1);
}
</syntaxhighlight>
<code>b</code> can not be allocated on stack.