21 Dec
2010
21 Dec
'10
6:42 a.m.
Michel MORIN wrote:
B. If boost::begin/end doesn't need to be found via ADL, then use ADL barrier technique to boost::begin/end.
Oooops, I made a mistake! Definitely, solution B is not a choice. It diables Boost-interfaced range from using in range-based for.
Oops, again. Solution B is not a choice, but the reason is wrong. B does not solve the problem, because there are still ambiguity between std::begin/end and boost::fusion::begin/end. Sorry for the noise. Regards, Michel