The error(s) thrown from using named arguments on built-in procs that do not support them differ based on the position of the expected argument. Was the named argument supposed to be the first, there are two errors thrown ('arglist() or named arguments cannot be used here' and 'missing expression'). If the named argument is not supposed to be the first, the error becomes ''expected 2 to 3 arguments (found 1)'.
Code Snippet (if applicable) to Reproduce Problem:
mob
verb
Test()
var/h = "test"
h = copytext(h, Start=1) // throws 'expected 2 to 3 arguments (found 1)'
h = copytext(h, 1, End=0) // see abouve
h = copytext(Start=1, h) // see abouve
h = roll(ndice=1, 3) // throws both 'arglist() or named arguments cannot be used here' and 'missing expression'
h = roll(3, ndice=1) // throws the same two errors
src << "[h]"
Expected Results:
Regardless of the expected position of the argument, named arguments in built-in procs that do not support them should throw one error, namely 'arglist() or named arguments cannot be used here', which should contain a link to the reference page on named arguments.
Actual Results:
Depending on the position of the argument, different errors and a different amount of errors is being thrown.
Does the problem occur:
Every time
In other user accounts - Verified on the Developers forum
On other computers - Verified on the Developers forum
When does the problem NOT occur? Never
Workarounds:
Non