Bob Sneidar wrote: > On Aug 9, 2018, at 11:45 , Richard Gaskin wrote: > Yes, the stackFiles property is every bit as global as any other use > of stack names. > > Not to belabor the point, but the stackfiles is a property of a STACK, > not a global system property.
A stack's name is also a property of a stack, but anything involving stack names has global effects.
The stackFiles property allows us to use the short name of a stack file to easily access that stack.
Once the stack with the stackFiles list is loaded, all those references are loaded with it. The same mechanism that allows scripts in that stack to call other stacks by short name allow any other scripts anywhere else to use that same name, because stack names have global effects.
Besides, even if you had two stacks whose stackFiles had the same stack short name assigned to different stackFiles, one of them wouldn't work anyway because as soon as it tried you'd get a stack name conflict warning.
Simpler to just remember that stack names have global scope, then you can plan accordingly with consistent simplicity.
-- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ____________________________________________________________________ ambassa...@fourthworld.com http://www.FourthWorld.com _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
