[Octave-bug-tracker] [bug #59597] bogus result returned by mexCallMATLAB

[John W. Eaton]

Follow-up Comment #15, bug #59597 (project octave):

Rik: Yes, if you already have access to the interpreter object, then it is
best to call feval directly through that instead of using the global
octave::feval function.  The global function will just look up the interpreter
object and then call the member function.  See the feval function definitions
in oct-parse.yy.

I haven't tagged those as deprecated yet because they are widely used and I
don't think we really want to eliminate them (yet).  But their use should be
discouraged.  It might be good if we had a way to distinguish between "this
function is deprecated and will be removed in two releases" and "using this
function is discouraged but it will remain available".

    _______________________________________________________

Reply to this item at:

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

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