Re: Mex API changes for 64bit

[Christopher Hulbert]

On 6/3/07, David Bateman <address@hidden> wrote:
> Christopher Hulbert wrote:
> > On 6/2/07, David Bateman <address@hidden> wrote:
> >> As documented in the Matlab release notes for R2006b at
> >>
> >> http://www.mathworks.com/access/helpdesk/help/techdoc/rn/bqt6wtq.html
> >>
> >> two new types have been introduced to allow for 64-bit indexing into the
> >> mex API. These are mwIndex for the indexing values and mwSize for sizes
> >> of arrays, etc. They suggest at least that both are "int" normally, but
> >> if the -largearraydims flag is used with mex or on a 64-bit platform,
> >> then they are of type "size_t". I'd suggest it probably makes sense for
> >> Octave to just typedef these to octave_idx_type.
> >
> > Should octave also support the Matlab backwards compatibility option?
> > In compiling MEX functions, defining MX_COMPAT_32 keeps the old
> > definitions, but doesn't allow 64-bit indexing.
> >
>
> I don't really see the point. These options only really make sense if
> you are compiling the mex files on one platform and using them on
> another. Is this type of cross-compiling really useful with matlab/octave?

Before matlab added mwSize, the API used integers. Some people (myself
included) have not had the chance to go back and change my code. And
if I did, I would need to test if the matlab header had mwSize
defined, and handle the case when it does not. That's the reason I
brought it up.

Chris

> D.