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

[anonymous]

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

In DynamicModelCaller using only dlopen/LoadLibrary to load a mex function may
not work. Each mex function requires its own workspace/context to manage its
memory. The function 'call_mex' in 'libinterp/corefcn/mex.cc' shows how the
mex_context (memory manager) works. Instead of loading mex by dlopen calling
the mex by its name and letting Octave to properly find and call the function
I think is a better option. 'addpath' may be needed to help the interpreter to
find the function.

    _______________________________________________________

Reply to this item at:

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

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