Graham Samuel write:
> I have a situation where I want to close a stack and then delete it,
> so that it no longer exists in memory and so that no naming
> conflicts occur when I load a fresh stack with the same name. This
> used to work - part of a script running in a different stack to the
>
Can any IDE experts out there explain exactly how the IDE does ‘Close and
Remove from Memory’? I am having trouble trying to recreate this code for my
standalone, and I am fairly sure that the code has to be different for LC8.x
compared to earlier versions. To be clear, I’m trying to remove all
Should have said, yes it’s a mainstack. I am beginning to think that the issue
is that when I close the stack it is also purged from memory (as it says in the
Dictionary, with provisos that I think I have obeyed), so that the following
‘delete’ doesn’t have anything to delete - this should
Phil, thanks for the suggestion. I timed out last night and tried it this
morning. Strangely it didn’t work - got the same error as before (347). So I’m
still investigating. I am fairly sure that there is an obscure bug (or at the
very least, a change of behaviour) in LC 8.1.x compared to
My comment wrapped. Sorry.
Phil
On 10/13/16 10:32 AM, Phil Davis wrote:
Hi Graham,
What happens if you do only this?
lock messages -- assuming you don't want any handlers to be
triggered by the stack's closing
delete stack "myDataStack"
I'm also assuming "myDataStack" is a mainStack
Hi Graham,
What happens if you do only this?
lock messages -- assuming you don't want any handlers to be
triggered by the stack's closing
delete stack "myDataStack"
I'm also assuming "myDataStack" is a mainStack and not a substack. (As
you know, you can't remove a substack from
I have a situation where I want to close a stack and then delete it, so that it
no longer exists in memory and so that no naming conflicts occur when I load a
fresh stack with the same name. This used to work - part of a script running in
a different stack to the one being deleted:
set the
