Call with CallArgArray regression in beta

[J-Paul Mesnage]

I found the following script does nt behave the same

Dim $args[1]
$args[0] = "CallArgArray"
$n = Call("Test1", $args)
MsgBox(262144,'Debug line ~' & @ScriptLineNumber,'Selection:' & @lf & '$n' & @lf & @lf & 'Return:' & @lf & $n & @lf & @lf & '@Error:' & @lf & @Error & @lf & @lf & '@Extended:' & @lf & @Extended) ;### Debug MSGBOX

Func Test1()
	Return 1
EndFunc

[Jon]

For reference, revision 7126 broke this.

[J-Paul Mesnage]

one more ...

[Jon]

Actually, this is a change from 3.3.8.1 but it seems to be ok behaviour as I would expect it.

$args[0] contains "CallArgArray" which signifies that it will pass some additional parameters but doesn't declare any, but the function declaration doesn't accept any parameters so this triggers the error.

The fact that 3.3.8.1 didn't error on that because CallArgArray was missing the actual parameters, and now it does is not a problem for me.

It's also exceptionally hard to change the behaviour with the way that Call() was rewritten

[anonymous]

What should I do if a script I'm using doesn't know how many arguments it should pass to Call and simply prepends a "CallArgArray"? Should I rewrite every function with an empty argument list to Func name ($bugFix = Default)?

[Jon]

Fixed by revision [10513] in version: 3.3.13.13