Understanding 'the defaultStack'

[Graham Samuel]

Yes, but the way I think of it is if you do a ‘go’ to another stack, then the defaultStack changes so that you can make shorter references to objects in what is most likely then the current stack of interest. I got in a muddle  because that isn’t always true. I suppose I rubbed along for a few years before I got hit by that particular gotcha, so in a way Richard you’re right. Good documentation is probably all that’s needed, rather than trying to alter the engine’s behaviour.

My two Brexit-influenced, over-valued, eurocents.

Graham
> On 14 Oct 2016, at 23:08, Richard Gaskin <ambassador at fourthworld.com> wrote:
> 
> Monte Goulding wrote:
> 
> >> On 15 Oct 2016, at 8:01 AM, Richard Gaskin wrote:
> >>
> >> I can't recall the last time I needed defaultStack.  It may well
> >> have been quite recently, but it must being doing what I expected
> >> it to do since I've never had to think about it before this thread.
> >
> > Every time you use an object reference that doesn’t contain an
> > explicit stack reference you are using the defaultStack. You might
> > not be getting or setting the value but you would be depending on
> > it in a large part of your code.
> 
> Exactly.  It must be working pretty well as it is or we would have had many more confused posts for decades rather than just a dozen only very recently.
> 
> -- 
> Richard Gaskin
> Fourth World Systems
> Software Design and Development for the Desktop, Mobile, and the Web
> ____________________________________________________________________
> Ambassador at FourthWorld.com                http://www.FourthWorld.com
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode