[Octave-bug-tracker] [bug #64516] optimset silently replace user defined "n" with "niter_check_tolfun"

[Markus Mützel]

Update of bug #64516 (project octave):

                Category:         Octave Function => Documentation          
              Item Group:        Incorrect Result => Documentation          
                  Status:               Need Info => Confirmed              
        Operating System:       Microsoft Windows => Any                    

    _______________________________________________________

Follow-up Comment #11:

I'm not quite sure where that should be documented. Any package could add any
number of options. Documenting all of them in the function inside Octave core
is probably not feasible (or even desirable).
A short note that it is *possible* that packages might add to the list of
options would probably a good idea though.

I don't think emitting a warning in case of an option being expanded is
desirable. That would probably lead to a lot of noise in existing code.

Afaict, options expand only if they aren't ambiguous. I.e. with the set of
options from Octave core, `Max` would not expand, but `maxf` would. I gathered
that from reading the code. But that could probably also be better
documented.

Documentation patches are always welcome.



    _______________________________________________________

Reply to this item at:

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

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