[Octave-bug-tracker] [bug #40824] newly compiled mex / oct function in private subdirectory not detected

[Mike Miller]

Update of bug #40824 (project octave):

                Severity:              3 - Normal => 2 - Minor              
                 Summary: MEX functions in private folders not detected after
compilation => newly compiled mex / oct function in private subdirectory not
detected

    _______________________________________________________

Follow-up Comment #3:

It took quite a few tries to reproduce this, I thought this was about an
existing function being recompiled. But this *only* affects a new function
that has never been compiled before. To reproduce, the object files have to be
deleted before Octave is started, then the compilation done while Octave is
still running.

I can confirm this is still present when a dynamic mex or oct function is in a
private directory on the load path.

One workaround that solves this is


path (path ())


which forces a complete reload of the load path, more brute-force than rehash,
and the newly compiled private functions are found.

This is similar to bug #36230, in which new functions added to a class
definition @-directory are not loaded once the class has already been parsed,
until the path is altered or completely reloaded using the same workaround.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/