https://svn.boost.org/trac10/ticket/2990 <p> In boost/python/detail/caller.hpp, to get at the various elements of the call signature sequence, the code directly uses Sig_iterator::type to access the element. This has a side effect of not allowing mpl::list to be used as the sequence, even though it is an MPL front extensible sequence (stated as required for the signature argument of, say, make_function). </p> <p> The solution is to use mpl::deref&lt;Sig_iterator&gt;::type instead of Sig_iterator::type. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/2990 Trac 1.4.3 buy cialas Tue, 11 Aug 2009 18:27:33 GMT https://svn.boost.org/trac10/ticket/2990#comment:2 https://svn.boost.org/trac10/ticket/2990#comment:2 <ul> <li><strong>summary</strong> <span class="trac-field-old">boost::python::detail::caller implementation should use mpl::deref while fiddling with the signature sequence</span> → <span class="trac-field-new">[fix in git] boost::python::detail::caller implementation should use mpl::deref while fiddling with the signature sequence</span> </li> </ul> <p> just marking this 'fix in git' as I assume I'll merge my entire branch to trunk at some point, and therein detail/caller.hpp has been completely overhauled to use fusion sequences throughout. </p> Ticket