Re: [Boost-bugs] [Boost C++ Libraries] #7769: BOOST_MPL_LIMIT_METAFUNCTION_ARITY > 8 causes compilation error on gcc

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #7769: BOOST_MPL_LIMIT_METAFUNCTION_ARITY > 8 causes compilation error on gcc
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2015-02-08 20:54:45


#7769: BOOST_MPL_LIMIT_METAFUNCTION_ARITY > 8 causes compilation error on gcc
------------------------------------+---------------------------------
  Reporter: Adam Lach <salvage@…> | Owner: agurtovoy
      Type: Bugs | Status: new
 Milestone: To Be Determined | Component: mpl
   Version: Boost 1.52.0 | Severity: Problem
Resolution: | Keywords: arity, metafunction
------------------------------------+---------------------------------

Comment (by brunocodutra@…):

 That was indeed just a tricky and dirty workaround to get it going for the
 end user. I've actually forked MPL and committed a cleaner version of it,
 which you may find on github: brunocodutra/MPL, branch Ticket7769. (I
 can't seem to find a way to post a link here).

 I managed to get rid of COUNT, but I could not find a way to get rid of
 the dependence on BOOST_PP_TUPLE_TO_SEQ without being forced to define a
 new macro, just like you proposed yourself. I was actually concerned about
 defining a new name to avoid breaking some naming convention rule or
 anything of the sort that I might be unaware of. I would certainly be glad
 to hear thoughts on that though.

 By the way, how should I proceed with the pull request? Should it be
 issued to the development branch?

 Regarding testing you are absolutely right, but I must confess I have no
 idea on how to proceed, any advice?

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

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:17 UTC