Rules governing stack purging

[Trevor DeVore]

On Oct 31, 2006, at 7:59 AM, Richard Gaskin wrote:

> That this would be the case with stacks whose destroyStack property  
> is FALSE makes sense, but when a stack's destroyStack is TRUE this  
> is inconsistent with other behaviors we've come to expect from the  
> engine.
>
> Given that this has caused confusion for yourself, Jacque, Ken,  
> myself, and other experienced Rev programmers, it seems reasonable  
> to request that the destroyStack property be honored consistently,  
> which I've done in BZ#3937:

Richard,

I'm not sure I understand why a stack should not be brought into  
memory and stay in memory until told otherwise when accessing it  
using the complete filenmae.  destroyStack docs state that it applies  
when a stack is closed.  Since the stack is never officially opened  
(no go stack, no msg sent) it is not closed so in my mind it should  
remain in memory.

-- 
Trevor DeVore
Blue Mango Learning Systems - www.bluemangolearning.com
trevor at bluemangolearning.com