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

[Mike Miller]

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

I still get the following behavior (with Rik's mex_private example posted
here, freshly extracted):


$ cd mex_private/private/
$ mkoctfile-4.4.0 --mex myprivfcn.c
$ cd  ..
$ octave -q
>> version -hgid
ans = c8f49ee7a687
>> tst_privfcn
error: Calling the m-file!
error: called from
    myprivfcn at line 2 column 3
    tst_privfcn at line 4 column 3
>> unlink private/myprivfcn.m;
>> tst_privfcn
error: myprivfcn: Calling the MEX-file!
error: called from
    tst_privfcn at line 4 column 3


And after restoring the m-file function, I looked at the '__dump_load_path__'
function you mentioned:


>> __dump_load_path__
…

*** private functions in ./private:

  myprivfcn (m)

…



    _______________________________________________________

Reply to this item at:

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

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