17 Jul
2011
17 Jul
'11
6:02 a.m.
On 17/07/11 04:58, Jeffrey Lee Hellrung, Jr. wrote:
* I *think* all generated metafunctions should also expose a nested "type" typedef in addition to a nested "value" static bool in order to be fully Boost.MPL compatible, but...I'm not sure on this one. For some reason, I've always followed this practice, I think because it allows has_type_xxx<T> to be used as a nullary Boost.MPL metafunction. Can someone comment on this?
Yes, could be nice to have as it will make the metafunction proper nullary MPL one. I suggest findign a way to inherit from boost::mpl::bool_ whenever possible.