make_argpack(vec_kwd, make_vector(arg[0], ..., arg[n-1]))

Hi All,
Any suggestion for this?
typedef typename mpl::transform
make_argpack(vec_kwd,make_vector(arg[0],...,arg[n-1])){ // Step 1: get a vector of tagged_argument vec_tagged_arg_t vec_tagged_arg = fusion::transform( kwds, args, binary_f() ); //OK // Step 2: // recursively construct args_list_t from vec_tagged_arg using // arg_list(TaggedArg arg, Next const& tail) // : Next(tail) // // , arg(arg) // // {} // // A little tedious. Before I go ahead : is this the proper way? // A better solution altogether? } Thanks.

AMDG er wrote:
Any suggestion for this?
I'm afraid I don't understand what you are trying to do. Can you explain in English rather than posting code that doesn't work?
<snip code>
In Christ, Steven Watanabe

Can you explain in English rather than posting code
Sorry, I was confused. I think I wanted to simplify
fun(
(
kwd<1>::value = arg1, // parameter::keyword
spec;
fun(
spec(arg1,...,argn)
)
So now, how to I create spec automatically?
template

Upon reflexion, my problem boils down to finding a metafunction that
maps an mpl sequence, such as
typedef mpl::vector
output;
The implementation of parameter::parameters uses a macro so unless I'm willing to/can generate input with macro it seems like a dead end. Correct?

er wrote:
Upon reflexion, my problem boils down to finding a metafunction that maps an mpl sequence, such as
typedef mpl::vector
input; to the template class boost::parameter::parameters instantiated with the elements of that sequence, each wrapped with required:
typedef parameter::parameters< required<tag1>, ... require<tagn>
output;
The implementation of parameter::parameters uses a macro so unless I'm willing to/can generate input with macro it seems like a dead end. Correct?
Does mpl::unpack_args sound like a valid starting point?
participants (2)
-
er
-
Steven Watanabe