On 02/03/2016 03:38 AM, Mark Waddingham wrote:
On 2016-02-02 17:05, Bernard Devlin wrote:
I know the params can be called to find out what parameters were
passed to
the handler when it is called. However, I'm wondering if a handler has a
way of knowing what parameters it had at the time it was
Hi Hermann
Even with the "LC handler" it's not quite giving me what I'd like. It's
still providing data from params(), rather than, for example, returning
mouseUp pNumberOfMouseButtonClicked.
I was hoping that a handler could provide information about itself at
compile time, rather than simply
Hi Pierre
I think we might be talking about different things.
For a few minutes, I thought you were saying that "get function
someFunctionName()" would return the "signature" of that function (in Java
the "signature" of a handler is "name param1 paramN"). But in LC it
appears we can't ask the
On 2016-02-02 17:05, Bernard Devlin wrote:
I know the params can be called to find out what parameters were passed
to
the handler when it is called. However, I'm wondering if a handler has
a
way of knowing what parameters it had at the time it was defined.
There isn't currently a way to get
Bernard wrote:
> I know the params can be called to find out what parameters were
> passed to the handler when it is called. However, I'm wondering
> if a handler has a way of knowing what parameters it had at the
> time it was defined. I don't think so. Regards Bernard
Yes, that's my opinion
I know the params can be called to find out what parameters were passed to
the handler when it is called. However, I'm wondering if a handler has a
way of knowing what parameters it had at the time it was defined.
I don't think so.
Regards
Bernard
___
Bernard,
It’s the way most AI programs are running (functional programming +
lambda-calcul => 24/7 enabled recursive call-backs)
1.- as a startup example :
on idle
if var1 and var2 is « » then
get function function_1
else
get function function_n
end if
end idle
or more
