Opened 9 years ago

Last modified 9 years ago

#2990 new Bugs

[fix in git] boost::python::detail::caller implementation should use mpl::deref while fiddling with the signature sequence

Reported by: LiJie Wong <lycheewlj@…> Owned by: Dave Abrahams
Milestone: Boost 1.39.0 Component: python USE GITHUB
Version: Boost 1.38.0 Severity: Problem
Keywords: Cc:

Description

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).

The solution is to use mpl::deref<Sig_iterator>::type instead of Sig_iterator::type.

Change History (2)

comment:1 Changed 9 years ago by buy cialas

Mal: "Don't f'in tell me what to goddamn do!"

Kaylee: (laughing) "Goddamn do?"

--"Serenity", outtakes

viagra comprare fioricet usa Cialis uk brand viagra propecia generico 7dv0K3n

comment:2 Changed 9 years ago by troy d. straszheim

Summary: boost::python::detail::caller implementation should use mpl::deref while fiddling with the signature sequence[fix in git] boost::python::detail::caller implementation should use mpl::deref while fiddling with the signature sequence

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.

Note: See TracTickets for help on using tickets.