I'm with Bob. When parameters are passed in a normal function call, they are completely local from both ends, and disappear after use. If you need to use values of some kind in order to work at all, and therefore have to extract them from somewhere, like a custom property, can you tell us why you do not want to simply use parameters in the first place?
-----Original Message----- From: Bob Sneidar <b...@twft.com> To: How to use LiveCode <use-livecode@lists.runrev.com> Sent: Tue, May 1, 2012 6:59 pm Subject: Re: Using handler local variables of caller If the handlers are in the same script, can't you use script local variables? If they are in different scripts, then Peter's suggestion of using properties may be the way to go. Seems like a lot to avoid passing parameters though. Bob On May 1, 2012, at 3:11 PM, Dar Scott wrote: > I'd like a function to use some variables of the caller without them being passed or being declared as globals. Is there a way to do that? > > Desktop externals can do that, but I don't see a way for a library in a function to do that. > > Dar > > > _______________________________________________ > 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 _______________________________________________ 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 _______________________________________________ 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
