"JOAQUIN LOPEZ MU?Z" <joaquin@tid.es> wrote:
IMHO nth_iterator_type and familiy are user-level facilities (similar vg to Boost.Tuple get<>) and accepting mpl integral constants instead of raw constants does not make much sense here. Please somebody correct me if I'm wrong.
One positive thing that could result from this would be the possibility of specializing the class to determine the type of the index, such as instead of nth_index_type<1>::type to use index_type<mpl::int_<1> >::type //rather clumzy, but doesn't clash with index_type<tag>::type If you then create some typedefs (possibly with the preprocessor), something like: typedef mpl::int_<1> _1; ... typedef mpl::int_<10> _10; This might look like: index_type<_1>::type; Regards, Arkadiy