[Octave-bug-tracker] [bug #64525] optimset/optimget issues warning, rather than error, when short name matches multiple possible options

[Nicholas Jankowski]

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

I'm ok with set issuing an error, but would it make more sense for optimget to
still issue a warning? it will return empty if it's ambiguous unless it's an
exact match, at which point it will issue an warning but return the exact
match value as well. Perhaps the warning message could be updated to mention
the ambiguity and clearly re-state the name of the field being returned?


    _______________________________________________________

Reply to this item at:

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

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