[Octave-bug-tracker] [bug #62420] inputParser fails due to interpreter changes in 7.1.0

[Georg Wiora]

Follow-up Comment #6, bug #62420 (project octave):

Hi Markus, your minimal example is perfect.

I think your suggestion of querying _nargout_ would be superior to the
try-catch-construct because it does not catch other errors and helps keeping
code simple. The problem I see is that throwing the exception inside the
validation function would not allow to display additional information in
inputParser about the reasons.

Your suggested change of inputParser looks good so far. I would recommend
testing the the error id of the exception to distinguish between "too few
output values" and any implementation or runtime error inside the validation
function. You may have a look on my comment #2 for this.




    _______________________________________________________

Reply to this item at:

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

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