Doc or design problem

[Dave Abrahams]

The library is designed to work well with other Boost libraries and uses well-accepted concepts introduced by Boost and TR1.

Templates that encapsulate boolean or numeric properties define a static member constant called value.

is_function_pointer< bool(*)(int) >::value // == true 
function_arity< bool(*)(int) >::value // == 1

The problem is that having a nested static member constant called value is neither necessary nor sufficient to work with MPL. The approach that makes it work the most smoothly would derive the template specialization from an MPL Integral Constant, but at least you need a nested ::type member.