alfC a écrit :
can you illustrate a little bit your design? Is the policy part of the state of the class?
Sample code for example : // 3D matrix with no-realloc semantic and base index of [1 1 1] matrix< float, settings(3d_, no_realloc, base_index<1,1,1>)> m( ofSize(4,4,4) ); Policy is part of the type signature and modify how the internals of the matrix works. The settings(...) is a shortcut to gather a large number of parameters. This type is then introspected internally using boost::parameters. ofSize(a0,...,an) is a function returning a nD extent object carrying the matrix dimensions size.
Is your multi_array class written on top of Boost.MultiArray. If not did that require small amount of code or basically another gargantuan sized library ?
It is "gargantuan" as it's basically a large compilation of tools for quickly turning Matlab code into C++ with fewest change possible. But I think the core of this thing can be extracted.
why the "interface changes"? (except for the a redefined operator= I guess I was thinking of the changes of the type signature sorry
-- ___________________________________________ Joel Falcou - Assistant Professor PARALL Team - LRI - Universite Paris Sud XI Tel : (+33)1 69 15 66 35