[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #57872] newly compiled function (.mex/.oct) wi

From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #57872] newly compiled function (.mex/.oct) with same name as m-file does not immediately override function file
Date: Mon, 24 Feb 2020 11:56:53 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Follow-up Comment #11, bug #57872 (project octave):

Interesting that Matlab notices the new file from within the invocation of a

I thought that we only needed to update the loadpath (or the cache of what is
in the loadpath) when the prompt is displayed.

Is the mex function triggering the update, or is it just the appearance of the
mex file?  What happens if you compile the mex file somewhere that is outside
of the loadpath and then do something like

  system ('cp testme.mex .')
  testme (varargin{:})

in the testme.m function?  No call to mex in the testme.m function, just a
system call to make it available.

For performance reasons, I don't think we want to be updating (or  checking
whether the loadpath needs to be updated) every time we are resolving a symbol
that could refer to a function.


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]