[Octave-bug-tracker] [bug #48439] validateattributes throws errors without IDs

[Carnë Draug]

Follow-up Comment #10, bug #48439 (project octave):

> If the function validateattributes is not called correctly, that is a
general sort of error and can use the same general error set that is described
in error_ids. For example, ode45 uses "Octave:invalid-input-arg" when it is
called incorrectly.

So let's assume that the next m function I write uses validateattributes for
input check? Should I catch the error and change it to invalid-inpu-arg? Or
should I not use validateattributes in Octave?

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?48439>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/