Question - BuildDate 20171013 Passed Parameters

[Bogreaper]

Anyone having issues with Build 20171013 not making undefined parameters available through Param?

http://www.macroquest2.com/wiki/index.php/Subroutines_and_Functions
[h=2]Passed Parameters[/h]All macros accept parameters passed to them when called. The parameters can be defined in the Sub line, or if not defined, they are available through the Param0, Param1, Param2...ParamN local variables while in the sub. If you don't define the types of variables, they will default to strings. The following two examples will both output the same thing:

Peace

 

[kaen01]

if you use the param1, param2 stuff have a line that detects if tehy dfined, if they havent been define them witha default value, is how i get around it, or sdimply end your macro and echo that an option is lacking.

 

[Bogreaper]

Aye... Before 20171013

Sub Main

/call testingthis Yeah​

/return

Sub testingthis

/echo ${Param0}
​

/return

Worked....... Now it does not. Param0 is NULL.

Peace

 

[eqmule]

You are using it before you even know if it is declared...

Do /if (${Macro.Params}==1) {
echo ${Param0}
}