Function call

[Anachron]

Hey guys!

How do I save a function and make a call, with parameters, later?

call ExecuteFunc()

This does not work with parameters.

call Function(pamaters)

This can not be stored :S

 

[Element of Water]

This is all vJass...

function interface TwoReals takes real a, real b returns nothing

This creates a function interface, which is basically like defining a new type of variable. Functions can be saved to it. Now, you can just do something like:

function interface TwoReals takes real a, real b returns nothing //define the function interface (or type)

globals
    TwoReals MyFunc //define the global function variable
endglobals

function Multiply takes real a, real b returns nothing
    call BJDebugMsg(R2S(a*b))
endfunction

function Add takes real a, real b returns nothing
    call BJDebugMsg(R2S(a+b))
endfunction

function Test takes nothing returns nothing
    set MyFunc = Multiply //save the Multiply function to the variable
    call MyFunc.execute(1.5, 2.5) //run the function with parameters

    set MyFunc = Add //save the Add function to the variable
    call MyFunc.execute(1.5, 2.5) //run the new function with parameters
endfunction

This will output:

3.750
4.000


The only limitation is that the functions you save in the variable must all have the same parameters and return type. Note that if you want to store the returned value of the function in a variable you can do local <type> r = MyFunc.evaluate(<params>)

 

[Anachron]

Oh hell, yeah. I tried interfaces before, but I didn't get the rid of them.

I am at the moment making an OnMyEvent Unit Event Handler, which lets you use any conditional event for every unit on map to trigger something with stored functions.

 

[Element of Water]

So what's your problem now?

 

[Anachron]

Problem was the function call which is an Array of the interface, I will check it at home, maybe I got it.

 

[Element of Water]

Function interface variables are just stored as integers internally, so there should be no problem making an array of them (or even storing them in hashtables).

 

[Anachron]

Hashtables.. Are you joking? Everybody is talking about 'em, but I doubt Blizzard will stay at those, because as we see now, they also fix the return bug, which was a praise for the mapper community. I think sooner or later they will need to fix hashtables aswell, or remove them again.

 

[Element of Water]

What's wrong with hashtables that needs to be fixed? They're great!

 

[Anachron]

What I mean is that you shouldn't bet on the hashtables, but stay on the old stuff instead.

 

[Element of Water]

No. Hashtables should be used. If Blizzard released them in a beta patch, they will release them in the final version.

 

[Anachron]

Yeah, I know that blizzard will release them, but how long? I mean a new system also has new mistakes, errors, security points.

 

[Sophismata]

Huh?

You're confusing an intended feature (hashtables), with an unintended bug (unsafe typecasting).

Blizzard would not implement hashtables only to take them away in the next patch. That would be stupid.

Blizzard never intended for the return bug to happen, nor be so critical for mapmakers. The gamecache was never designed to be used the way most maps use it.

 

[Dr Super Good]

You do that by saving the parameters to globals before hand and then executing the function via the function name string.

 

[Element of Water]

If a feature is available for use, and it does something you want it to do, it is stupid not to use it.

 

[Dr Super Good]

Basically what I mentioned is how I believe JNGP does it.

 

[Element of Water]

I think JassHelper uses TriggerEvaluate.