David Abrahams escribió:
on Sat Nov 01 2008, Joaquin M Lopez Munoz <joaquin-AT-tid.es> wrote:
1. Seems like the tags functionality could take advantage of Boost.Parameter to provide a nicer interface and save some code.
I don't see how... Would you care to elaborate?
instead of:
employee_set::index<name>::type& name_index=es.get<name>();
you could have
employee_set::index<tag::name>::type& name_index = es[name];
I guess it's not a huge win.
I guess not. I'd rather leave it like it stands.
<shameless plug>For a very extensive and, IMHO, effective use case of Boost.Parameter have a look at the free-order template parameter interface of the (soon to be included in Boost) Boost Flyweight Library (http://tinyurl.com/6xxdkm ).</shameless plug>
Nice, but especially since those parameters are optional I wouldn't try to exhaustively list all the combinations; the doc gives the impression that they all need to be passed. If the point is to make it easy for the reader, I suggest you not overwhelm her with code ;-) The Boost.Python docs explain this stuff in a simple way that nobody *ever* asks me about, and doesn't require me to enumerate all the argument orders.
I've skimmed thru B.Py docs and can't seem to find the material you mention. Could you please provide me with a URL?
Thanks for keeping an open mind about that :-)
Thanks for challenging my assumptions. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo