I want to make a few commands and functions that work like some built-in 
functions.

For example, the built-in commands 'read' and 'ask...' both set 'it'.  If I 
make my own version of 'ask', I'd like for the command to set 'it'.

For example, the built-in "function" 'value()' works in the local context.  I'd 
like to make my own version of 'value()'.

There are ways around these problems, but I wanted to keep things simple for 
the user.  

Dar


On May 1, 2012, at 6:03 PM, [email protected] wrote:

> 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 <[email protected]>
> To: How to use LiveCode <[email protected]>
> 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
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to