Java 8 Stack Allocation
From Talk:ScalarNext/Version History
← Thread:Talk:ScalarNext/Version History/Java 8 Stack Allocation
Jump to navigation
Jump to search
← Thread:Talk:ScalarNext/Version History/Java 8 Stack Allocation
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.
void stack() {
Point2D.Double a = new Point2D.Double(0, 0);
a.setLocation(1, 1);
}
a
could be allocated on stack, while
void heap() {
Point2D.Double b = new Point2D.Double(0, 0);
b = new Point2D.Double(1, 1);
}
b
can not be allocated on stack.
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page.
Return to Thread:Talk:ScalarNext/Version History/Java 8 Stack Allocation/reply.