[Octave-bug-tracker] [bug #31392] fix for case insensitivity of optimset options

[Olaf Till]

Follow-up Comment #2, bug #31392 (project octave):

Not keeping it could slightly change the behavior intended to be seen by
users.

Before the fix, it was intended to be an error if two optimization-functions
registered the same option in different case (according to the error message
in __all_opts__.m).

It can't be an error any more after the fix if the originial list with the
"correct" case is not kept.

Since the optimization functions can be queried by the user for their
available options, in the same way as they are queried for registering them,
the user might then see the same option in different case if the programmer of
one optimization function was not careful to supply the "correct" case. This
might confuse the user if he is not aware of case-insensitivity.

This could be avoided if one gave up the notion of a "correct" case entirely
and provided that even in queries, by a user or for registration, only
lowercase is returned. But then some of the Matlab-compatible options are
possibly difficult to read in the result of a user query. Also, former Matlab
users might be used to see the option in the "correct" case. And the "correct"
case is used in the documentation of existing optimization functions.


    _______________________________________________________

Reply to this item at:

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

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