Aleksey Gurtovoy wrote:
David A. Greene wrote:
Thanks for considering this. I think it will be quite
useful. I look forward to seeing what you come up with!
Well, it turned out to be a little bit more complicated than
I had foreseen, so it's not there yet. Please stay tuned!
Okay,
Aleksey Gurtovoy [EMAIL PROTECTED] writes:
Aleksey Gurtovoy wrote:
David A. Greene wrote:
Thanks for considering this. I think it will be quite
useful. I look forward to seeing what you come up with!
Well, it turned out to be a little bit more complicated than
I had foreseen, so
Aleksey Gurtovoy wrote:
That's because the MPL's lambda works only with metafunctions which template
parameters are _types_, and only types:
That's what I suspected.
3) a metafunction with template template parameter, can't be used in lambda
expressions:
Again, what I suspected.
It _is_
David A. Greene wrote:
[Posted to boost because MPL is not yet released. At what
point should these questions go to boost-users?]
It's mainly the content of the message that determines whether it should be
posted here or to the Boost Users list; the status of the library - is it in
David Abrahams wrote:
I suppose not. What I really wanted was the ability to take a
regular old template class and create a generator out of it:
templatetypename T, typename U, typename V
struct my_type { ... } // Note: no ::type member
typedef SHAZAMmy_typeint, _1, _2 generator;
typedef
David A. Greene [EMAIL PROTECTED] writes:
template class T, class U, class V
struct my_type_generator
{
typedef my_typeT,U,V type;
};
lambdamy_type_generator does it
Oops, I meant
lambdamy_type_generatorBound,mpl::_1,mpl::_2
of course!
, unless of course
David Abrahams wrote:
template class T, class U, class V
struct my_type_generator
{
typedef my_typeT,U,V type;
};
lambdamy_type_generator does it
Oops, I meant
lambdamy_type_generatorBound,mpl::_1,mpl::_2
of course!
Ok, that makes more sense now. :)
, unless of
David A. Greene [EMAIL PROTECTED] writes:
So do you feel you need an additional library feature?
That's what I'm trying to find out. It seems like most of the
stuff is there already in MPL placeholders and binders.
Plus your solution here doesn't bind T to a type. :)
Are you just pointing
David Abrahams wrote:
Your correction above makes everything clear to me now.
So do you feel you need an additional library feature? ;-)
I suppose not. What I really wanted was the ability to take a
regular old template class and create a generator out of it:
templatetypename T, typename
David A. Greene [EMAIL PROTECTED] writes:
David Abrahams wrote:
Your correction above makes everything clear to me now.
So do you feel you need an additional library feature? ;-)
I suppose not. What I really wanted was the ability to take a
regular old template class and create a
10 matches
Mail list logo
