Gennaro Prota wrote:
> On Thu, 6 Feb 2003 06:05:23 -0600, Aleksey Gurtovoy
> <[EMAIL PROTECTED]> wrote:
> > It has 'next'/'prior' members because it's the easiest/most
> > efficient way to implement 'next/prior< integral_c<T,n> >::type'
> > functionality on compilers that don't support partial template
> > specialization.
>
> However, if we agree that when having autonomous next/prior we will
> only use them to access next/prior< .. >::type and that the user
> *must* specialize them for everything else
Nope, we don't. This should work out-of-box:
struct her_iterator
{
typedef /* unspecified */ next;
};
typedef mpl::next<her_iterator>::type t;
Aleksey
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
