Daniel Frey wrote:
Peter Dimov wrote:
You've considered
bind(f, bind(g, _1, _2), bind(h, _1, _2))
right? ;-)
Sure. But still compose.hpp is in itself incomplete. And it completes the standard's parts on function objects so I think it might be desirable to supply compose_f_gxy_hxy.
The standard is moving towards 'bind' - http://std.dkuug.dk/jtc1/sc22/wg21/docs/papers/2003/n1455.htm.
If we take bind into account here, we could just as well remove
compose.hpp completly, couldn't we?
We might, in a couple of years. Seriously, 'bind' is superior here; it takes some learning to switch over from the 'compose_*' family, but it's worth it.
Well, I'm already using the lambda-library, so I'm no longer bound to compose_*. I just thought that completing compose.hpp might be a good idea. But if it's deprecated, this doesn't really make sense. Never mind... :)
Regards, Daniel
-- Daniel Frey
aixigo AG - financial training, research and technology Schloß-Rahe-Straße 15, 52072 Aachen, Germany fon: +49 (0)241 936737-42, fax: +49 (0)241 936737-99 eMail: [EMAIL PROTECTED], web: http://www.aixigo.de
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
