C++ MPL or_, and_ implementations
- by KRao
Hi,
I am trying to read the boost headers to figure out how they managed to implement the
or_<...>
and
and_<...>
metafunctions so that:
1) They can have an arbitrary number of arguments (ok, say up to 5 arguments)
2) They have short circuit behavior, for example:
or_<false_,true_,...>
does not instantiate whatever is after true_ (so it can also be declared but not defined)
Unfortunately the pre-processor metaprogramming is making my task impossible for me :P
Thank you in advance for any help/suggestion.