Dave, David Abrahams wrote:
Thomas Witt <witt@acm.org> writes:
For the record I don't think it's irritating at all. It very clearly states what is going on. I can see it being cumbersome though.
Cumbersomeness is irritating ;-)
You are missing my point ;-)
The user can always call the hook unqualified. That's _going_ to be a public part of the library's interface.
Well, if you look at it this way then the _only_ functionality boost::begin provides is a syntactic shortcut. I.e. boost::begin(r); and using boost::range_begin; range_begin(r); are functionally equivalent. Did I miss something? In this case we have the real name in the helper and some artificially uglified name in all class interfaces. This doesn't feel right to me. You could also argue that boost::begin's name does not really describe what it's doing. Having a namespace qualified call disguise an unqualified call is another issue that gives me headaches. Thomas -- Thomas Witt witt@acm.org