Understanding 'the defaultStack'

[J. Landman Gay]

On 10/9/16 3:25 PM, Jeanne A. E. DeVoto wrote:
> I don't think it's feasible to actually make major changes in the way
> the defaultStack works, but possibly a new property could be designed
> that acts in such a way that workarounds like this aren't normally
> needed. Setting and re-setting the defaultStack to make sure it's right
> is almost as annoying as specifying the stack every time you refer to an
> object (which I sometimes do anyway, for fear of the defaultStack
> changing from under me).
>
> If it were being designed from scratch, what would the ideal behavior be
> for a targetStack property? Should it remain unchanged while a script is
> running (unless set explicitly)?

What about a "lock defaultstack" command?

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com