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-22 09:47:46

#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 John Fletcher <J.P.Fletcher@…>):

 I believe I have provided a solution to this problem and also provided the
 user with a way to have the previous behaviour by defining
 BOOST_PHOENIX_NO_SPECIALIZE_CUSTOM_TERMINAL.

 I am now being criticised for defining such things.

 >This kind of switches make it difficult to use together
 >different libraries which themselves use phoenix, unless the macro is
 >dragged and honored to every piece of code defining a custom terminal.

 I don't believe that is true. You don't need to use it unless you need the
 old behaviour.  Because all the tests for it are negative it does not have
 to be defined at all.

 I want to resolve this and close this bug as soon as I can.  John

 I thought that was a good thing to do but could remove it and force the
 new behaviour.

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