Mex Extensions

[John W. Eaton]

On  9-Jan-2007, Thomas Treichl wrote:

| my posting here
|     http://www.cae.wisc.edu/pipermail/help-octave/2006-December/002587.html
| has never been answered therefore I send it modified again to this list:
| 
| - Is it possible to add #defines for
|      mwSize (=int), mwIndex (=int), true and false
|    to the mex sources (the mex.h file) for compatibility with LabMat?
|    If I only use #include <mex.h> I cannot see these defines.
| 
| - I miss one of the great octave features in the mex-interface that I could
|    imagine to be added: The help string implementation like that one I can
|    use with the DLD. I could imagine to either use something like
| 
|      #ifndef MATLAB
|        mexSetHelpOctave ("help-string and tests and demos");
|      #endif
| 
|    or something more complicated like
| 
|      #ifndef MATLAB
|        mexOctave (int nlhs, ...mxArray* prhs[], const char *octavehelptext)
|      #else
|        mexFunction (int nlhs, ...mxArray* prhs[])
|      #end
| 
|    to be able to use the "help"-, the "test"- and the "demo"-command in octave
|    (and none of these commands in LabMat - cause I am coding octave). I could
|    imagine to compile one and the same written mex function with octave
|      mkoctfile --mex file.c
|    and with LabMat
|      mex -DMATLAB file.c
| 
|    or something that way. Of course you could say that this has nothing to
|    do with the original mex-interface from LabMat, but does it make sense
|    to not add support for this great octave feature?

LabMat?

I'm definitely not interested in extending the MEX interface in any
way.

If you want help for a MEX file, use a corresponding .m file in the
same directory that just contains the help text.

jwe