[Octave-bug-tracker] [bug #60237] Differente behaviour in anonymous function handling

[Markus Mützel]

Update of bug #60237 (project octave):

                  Status:               Need Info => In Progress            
        Operating System:       Microsoft Windows => Any                    

    _______________________________________________________

Follow-up Comment #6:

Nice detective work!

If I read the current code correctly, `feval` should be called with the
octave_value if it is not clear if the argument is an (inline) function or a
function handle.
I'd guess that `args(0).is_function()` would evaluate to false in the case
where it fails. It's possible that in previous versions the argument was an
inline function while it is a function handle now.

This is probably something that should be fixed in NLOpt rather than in
Octave. But I'll leave this report open in case someone with a better insight
has a different opinion.

Wrt preparing a changeset for NLOpt: Afaict, ever since `feval` is a member
function of the interpreter, it also has an overload for an octave_value
argument.
Fwiw, an overload of `octave::feval` with an octave_value argument was
introduced in this changeset:
https://hg.savannah.gnu.org/hgweb/octave/rev/55916f99b8b6
I believe this was for Octave 5.

I hope that helps.

    _______________________________________________________

Reply to this item at:

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

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