[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 22:33:00 +0200 |
User-agent: |
Thunderbird 1.5.0.7 (X11/20060921) |
John W. Eaton wrote:
> single precision data type
Just a question, since the double complex type has taken the name
"Complex" whereas normally it should have a name starting in "Z", what
would you call the single precision complex type? In any case, adding
the type itself is easy enough, its all the mixed operators and all of
the functions that currently accept double arrays that would also have
to be converted to accept single precision arrays where the real work
is.. Given increasing memory sizes, is this really worth it?
> profiler
> debugger
> interpreter performance
What happened to the discussion on a tree walker evaluator? It seemed
that that was a great idea that might impact all three of these...
D.
- Mex API changes for 64bit, (continued)
- 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, 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, 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 <=
- Re: Mex API changes for 64bit, John W. Eaton, 2007/06/05