Re: mapper functions for 3.1

[David Bateman]

I see one issue with the charNDArray class. There the typedef for all
the mapper functions are the same (i.e. int (*) (int)) but the return
type of the mapper method itself might be different (cf isalpha to
tolower). This is likely to cause issue with your scheme, and is in fact
why the charNDArray mapper methods have different maps (dmap, smap,
bmap) in my patch.. I'm not sure how to deal with that in your scheme,
other than keeping the map names different. So you'll end up with 6
different mapper methods in the Array<T> class at least.

As for the rest I see no issues, and the sparse type could be done in
the same manner..

D.