Eric Niebler wrote: > Proto ships with a very small collection of callables for use in Proto > transforms: wrappers for fusion algorithms like reverse and pop_front > and the like. For 1.46, there will be a few more: make_pair, first, > second, and wrappers for a few more Fusion algorithms. It's woefully > incomplete, though. > > I have an idea. Phoenix3 defines *all* these juicy callables under the > stl/ directory. I can't #include them in Proto because that would create > a circular dependency. Why don't we just move the definitions of the > function objects into Proto and make them Proto callables? Phoenix3 can > just #include 'em and use 'em. > > Thoughts?
I just saw that you added functional::at. I was wondering about the rationale of your decision to make it a non template. My gut feeling would have been to have proto::functional::at<N>(seq) and not proto::functional::at(seq, N). _______________________________________________ proto mailing list proto@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/proto
