Re: [Boost-bugs] [Boost C++ Libraries] #7300: Custom terminals are always nullary

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #7300: Custom terminals are always nullary
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2012-08-29 06:04:03

#7300: Custom terminals are always nullary
-------------------------------+--------------------------------------------
  Reporter:  andysem           |       Owner:  theller
      Type:  Bugs              |      Status:  closed 
 Milestone:  To Be Determined  |   Component:  phoenix
   Version:  Boost 1.52.0      |    Severity:  Problem
Resolution:  fixed             |    Keywords:         
-------------------------------+--------------------------------------------
Changes (by theller):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 Sorry for the delay ... looks like there is something wrong with my mail
 client ... I replied to your message to the mailing list already ...

 The solution is here:
 {{{
 namespace my { template <typename> class output_terminal; }

 namespace boost { namespace phoenix { namespace result_of {

     template< typename T >
     struct is_nullary< custom_terminal< my::output_terminal<T> > > :
         public mpl::false_
     {};

 }}}

 }}}

 Put this at the beginning of your file and it compiles and runs. The
 is_nullary specialization needs to be wrapped inside another
 custom_terminal template in order to disambiguate from other rules.

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