Get from "unopened" stack

[Dar Scott]

On Jul 14, 2004, at 8:16 PM, Jeanne A. E. DeVoto wrote:

>>> How is accessing an unopened stack different than using "go 
>>> invisible"?
>>
...
> It's loaded into memory, but there's no window for it. (Just like a 
> stack whose destroyStack is false, after you close it... it's still in 
> memory even though it's closed.)

There seem to be some differences in compiling and loading externals, 
too.

Dar Scott