"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 out my error?
>
> Well...yeah. :) It wasn't meant as an attack.
Wasn't taken that way.
> I honestly was confused about what you presented.
Understandably.
> Your correction above makes everything clear to me now.
So do you feel you need an additional library feature? ;-)
>>>g++ 3.2. The MPL paper and docs don't say anything about
>>>using placeholders or binders with classes that aren't
>>>metafunctions. How would the binders know what to typedef
>>>as apply::type?
>> I don't know... well, it could detect whether there was a ::type
>> member, and if it were not present, it could just give you the outer
>> class. I think that's a bit of a hack, though.
>
> Agreed. Urk...I'm not sure how to get around this problem without
> requiring template template parameters (beyond what's used for
> placeholders currently).
There's no way. So what? Your compiler supports them.
--
David Abrahams
[EMAIL PROTECTED] * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
