Quote:
Originally Posted by davidhorman
... with (what I assume is) the current procedure as fallback: if an array is expected next by the plugin, and an element of the correct type is found, place it in the array and continue reading parameters into the array until a named parameter is given.
|
I believe in the current procedure it will also stop reading if an argument incompatible with the array base type is found (whether named or not). This allows things like foo(1,2,3,true) when calling a function with a parameter type list of "i*b".
I agree it's the responsibility of the plugin writer to choose a parameter list that is unambiguously interpreted.