[Octave-bug-tracker] [bug #53856] MEX file in a private directory of a class

[Rik]

Follow-up Comment #5, bug #53856 (project octave):

Boy, that's weird.  I have re-confirmed that I get the print out from the MEX
file with 5.0.0 which is installed, and also using run-octave in a development
directory.  The HG ID for this is


parent: 25360:bc5f225bc578 tip
 eliminate some global accesses to the breakpoint table


from today.

If I start with no .mex file in the private directory, then I get the output
from the m-file.  With Octave still running, if I then use a shell and
mkoctfile to compile the .mex file, I still get the output from them-file.  No
amount of 'clear -f' or 'clear -a' will make Octave see the new .mex file. 
However, if I quit Octave and re-start then the printout is from the .mex
file.

So, it may be something about scanning for .mex files only once at startup.  I
also tried 'rmpath mex_private; addpath mex_private' hoping to force a
re-scan, but it didn't work.

If the .mex file is present, however, when you start Octave then you are
seeing a different issue.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53856>

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