Hmm, I can't see that working, as the stack for one thread will not be available to others. The optimiser would have to satisfy itself that such an object was only accessible by one thread at a time, and it would have to move the object around between stacks as the parent came into scope in different threads. Heap sounds safer, simpler and more performant.
On Apr 23, 1:45 am, mP <[email protected]> wrote: > Does the JVM ever put non local Objects on the stack, as this would satisfy > the comment about reusing memory as soon as possible but not earlier ? Then > again its probably very difficult to determine if this is possible which > might be the reason for the distinction in dotnet. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
