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

[Guillaume]

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

                 Summary: MEX file in a private directory of a class
                 Project: GNU Octave
            Submitted by: gyom
            Submitted on: Mon 07 May 2018 10:38:14 AM UTC
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error
                  Status: None
             Assigned to: None
         Originator Name: Guillaume
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

I observed errors by which M functions in a private directory are not
overshadowed by an associated MEX file. I have got plenty of examples where it
does work but it seems to fail with the toy example below.

Just compile the MEX file with mkoctfile --mex mysubfunction.c and run:


octave:1> a = myclass ();
octave:2> mymethod (a)
error: Calling the M-file!
error: called from
    mysubfunction at line 2 column 3
    mymethod at line 2 column 3



@myclass
├── myclass.m
├── mymethod.m
└── private
    ├── mysubfunction.c
    ├── mysubfunction.m
    └── mysubfunction.mex



function m = myclass
  m = class (struct ('a',1), 'myclass');
endfunction



function mymethod(a)
  mysubfunction ();
endfunction



function mysubfunction ()
  error ("Calling the M-file!");
endfunction



#include "mex.h"

void mexFunction(int nlhs, mxArray *plhs[], int nrhs, const mxArray *prhs[])
{
  mexErrMsgTxt("Calling the MEX-file!");
}





    _______________________________________________________

Reply to this item at:

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

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