[Octave-bug-tracker] [bug #61789] new interpreter error for too many input arguments has no error-id (for too few arguments it has one)

[Rik]

Follow-up Comment #7, bug #61789 (project octave):

I think the extra specificity of the error message is important to keep.  If
the error message is made vaguely compatible then it might be something like
"Invalid call to function (too many input arguments)".  Calling print_usage()
is just not very clear in this case because the programmer then has to
decipher whether they called the function with the wrong inputs (char vs.
double for example) or whether they have made some other error (like too many
inputs).

At least for Octave core, we have already removed all BIST tests that tested
for extra arguments because that functionality is done by the interpreter.

I don't think it is much of a maintenance burden to push for these same BIST
tests to also be removed from packages and user code.  Mostly I think this
because most coders don't write BIST tests so there shouldn't be much code out
there to check.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61789>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/