[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Mex API changes for 64bit
From: |
David Bateman |
Subject: |
Re: Mex API changes for 64bit |
Date: |
Sun, 03 Jun 2007 08:51:33 +0200 |
User-agent: |
Thunderbird 1.5.0.7 (X11/20060921) |
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?
D.
Mex API changes for 64bit, John W. Eaton, 2007/06/02
Re: Mex API changes for 64bit, Christopher Hulbert, 2007/06/02
- Re: Mex API changes for 64bit,
David Bateman <=
- Re: Mex API changes for 64bit, John W. Eaton, 2007/06/03
- Re: Mex API changes for 64bit, Christopher Hulbert, 2007/06/03
- Re: Mex API changes for 64bit, David Bateman, 2007/06/03
- Re: Mex API changes for 64bit, Christopher Hulbert, 2007/06/03
- Re: Mex API changes for 64bit, David Bateman, 2007/06/03
- Re: Mex API changes for 64bit, John W. Eaton, 2007/06/03
- Re: Mex API changes for 64bit, Christopher Hulbert, 2007/06/03
- Re: Mex API changes for 64bit, David Bateman, 2007/06/03
- Re: Mex API changes for 64bit, John W. Eaton, 2007/06/05