From: Giovanni Bajo (giovannibajo_at_[hidden])
Date: 2002-07-30 05:09:55
Why ::type has been preferred over a more natural ::result? I understand
that the result is always a type, but I think that using "result" is more
straightforward to learn and use, since what the type is holding is nothing
else but the result of the metafunction.
Also, at/at_c get (N, Seq) as parameters, in this order. Every other
algorithm in MPL get (Seq, ...), with the sequence being the first
parameter. This is very asymmetric, and also a bit hard to debug, since the
compiler just start producing complex errors when you try the natural
at<Seq, int_c<4> > (ok, at_c<> is easier do debug).
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk