Real-Time Java: An Introduction
Subject:   heap or stack
Date:   2006-05-16 03:23:56
From:   simon_massey
Response to: heap or stack

i was thinking that such a @Stack annotation could be ignored by java implimentations that don't understand it - in which case it all goes on the heap. an implimentation that did understand it could do compile time checks to ensure that objects so marked and allocated on the stack are not assigned object variables on the heap. thus giving you cheap and cheerful scoped memory. the sole purpose being to minimise gc activity at the expense of having to constrain your code to not reference object on the stack from the heap.

1 to 2 of 2
1 to 2 of 2