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 11:26:48

#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):

 Nevermind the #9693, I found out that I forgot to specialize is_nullary
 for my terminal. I wonder how it worked before.

 Regarding the macro. I kind of agree with the quote you presented in
 comment 13 because now in Boost.Log I apparently have to support both
 configurations. I.e. the old code with multiple is_nullary specialization
 don't disappear but potentially is made conditional, which is worse. Can
 this macro be removed and the new code be always in action?

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