[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
FYI: mx_inlines simplifications
From: |
Jaroslav Hajek |
Subject: |
FYI: mx_inlines simplifications |
Date: |
Fri, 26 Feb 2010 09:48:35 +0100 |
hi all,
based on the previous simplifications of the Array class hierarchy, I
was finally able to simplify the appliers in mx-inlines:
http://hg.savannah.gnu.org/hgweb/octave/rev/b47ab50a6aa8
All the appliers are now parametrized directly by value types instead
of array types, and are accepting & returning generic Arrays.
The code is now much cleaner and no longer cluttered by the AELEMT
macro. Also, there should be less distinct instances in total now,
so maybe the compiler could merge some of them.
Michael, I believe this could solve some of your compilation problems
with MSVC, because the function template parameter in do_mx_unary_map
no longer contains dependent names:
template <class R, class X, R fun (X)>
inline Array<R>
do_mx_unary_map (const Array<X>& x)
template <class R, class X, R fun (const X&)>
inline Array<R>
do_mx_unary_map (const Array<X>& x)
IIRC, according to your tests MSVC handled this simpler case
correctly. Can you confirm...?
regards
--
RNDr. Jaroslav Hajek, PhD
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz
- FYI: mx_inlines simplifications,
Jaroslav Hajek <=