mapper functions for 3.1

[David Bateman]

In the "goals for 3.1" thread there were the points

8. Make mapper functions work like other built-in functions?

9. Mapper functions like real, imag, and mod should preserve type (are
there others?)

I can see easily how to address point 9 in ov-mapper.cc itself, though
in might involve some if/else blocks. However, I'm not sure I see what
is meant by point 8. John what was your thoughts for point 8? Does this
mean that you wanted to get rid of the ov-mapper class and duplicate the
mapper loops in the functions themselves? The nice thing about the
current code is that it the loops aren't duplicated for each function.
How can we make the mapper functions more like other functions without
massive code duplication? Should the mapper functions migrate to the
octave_value, Array<T> and Sparse<T> classes?

D.

-- 
David Bateman                                address@hidden
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary