MATLAB_version 7.3 (or whatever) to 7.5; use other
aspects of mex.h to figure out which one.

#else

this is MATLAB 7.2 or earlier, etc.

#endif

#else

this must be MATLAB 7.6 (or whatever) that has MATLAB_VERSION defined already

#endif

I’d write such a mex_version.h myself, but it would require some pretty deep analysis of the mex.h file and all the files it includes, to figure out what the best #if tests are. It would be best be done by someone at The MathWorks.

#if MATLAB_VERSION >= 7.3
#define Int mxSignedIndex
#else
#define Int int
#endif

…

Int *p = mxGetJc ( … ) ;

The new mx data type for an integer can’t be used in mexFunctions that attempt to port to older versions of MATLAB. Thus, I just use “long” and skip the use of mxSignedIndex that appeared in MATLAB 7.4 (or was it 7.3…? whichever …).

The lack of a MATLAB_VERSION makes porting a mexFunction for different versions of MATLAB (both 32-bit and 64-bit) very very tricky, particularly ones that deal with sparse matrices since the mexFunction needs to know how the integers are stored inside the sparse matrix (32 or 64 bits).

Those who write M-files don’t have to worry about this, but mexFunction authors do.

–Loren