[Boost-bugs] [Boost C++ Libraries] #2252: Doc or design problem

Subject: [Boost-bugs] [Boost C++ Libraries] #2252: Doc or design problem
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2008-08-25 07:25:37

#2252: Doc or design problem
--------------------------+-------------------------------------------------
 Reporter:  dave          |       Owner:  t_schwinger   
     Type:  Bugs          |      Status:  new           
Milestone:  Boost 1.37.0  |   Component:  function_types
  Version:  Boost 1.36.0  |    Severity:  Problem       
 Keywords:                |  
--------------------------+-------------------------------------------------
 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 [http://www.boost.org/doc/libs/1_36_0/libs/mpl/doc/refmanual

 /integral-constant.html: MPL Integral Constant], but at ''least'' you need
 a nested {{{::type}}} member.

-- 
Ticket URL: <http://svn.boost.org/trac/boost/ticket/2252>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.