Re: [Boost-bugs] [Boost C++ Libraries] #7730: Generic specializations of is_nullary for custom terminals are not possible

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #7730: Generic specializations of is_nullary for custom terminals are not possible
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2014-02-04 02:42:40

#7730: Generic specializations of is_nullary for custom terminals are not possible
-------------------------------+---------------------
  Reporter:  andysem           |      Owner:  theller
      Type:  Bugs              |     Status:  new
 Milestone:  To Be Determined  |  Component:  phoenix
   Version:  Boost 1.52.0      |   Severity:  Problem
Resolution:                    |   Keywords:
-------------------------------+---------------------

Comment (by andysem):

 Replying to [comment:1 John Fletcher <J.P.Fletcher@…>]:
 > I have implemented your test and am putting it onto develop.
 >
 > I have set it up so that for the moment it is necessary to do this
 before the header to use this.
 > {{{
 > #define BOOST_PHOENIX_SPECIALIZE_CUSTOM_TERMINAL
 > }}}
 >
 > There is a test bug7730 which will test the header with the define.
 >
 > Please let me know if this works for your case.

 Since this bug affects Boost.Log (a library), I cannot define the macro in
 my code, so it doesn't really help me. In order to work, this has to be
 the default (and the only) behavior of Boost.Phoenix. To my understanding,
 it should be safe enough to enable it by default the way I described in
 the ticket, although, of course, I may be missing something.

 Replying to [comment:2 John Fletcher <J.P.Fletcher@…>]:
 > Note: I have not implemented this part of your example because as I read
 it this part will go into your client code. Is that correct?

 Yes.

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