Re: [boost] [type_erasure] overloading macro

Subject: Re: [boost] [type_erasure] overloading macro
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2013-02-19 17:20:32

AMDG

On 02/19/2013 02:08 PM, Christophe Henry wrote:
>>> Oh I missed this :(
>>> I just tried your newer version and it works.
>>> Do you plan to support this also for C++03?
>>>
>>
>> No.
> 
> I'm pretty bad with Boost.Preprocessor but I suppose it'd be doable with
> a max number of arguments, right?
> 

It is doable, but I don't think I want
to expend the effort on something that
will be obsolete in a few years.

>>> Before I plan another useless workaround, do you plan to support anytime
>>> soon rvalue references in the concept map definition?
>>> It'd be something useful.
>>>
>>
>> I don't know exactly what you're referring to.
>> I don't remember off hand how complete my rvalue
>> reference support is.  I'll try to finish it
>> off after I implement a variadic BOOST_TYPE_ERASURE_FREE.
> 
> I mean something like this in a concept map:
> struct any_foo:
> ::boost::mpl::vector<
>    has_foo<void(Something&&), const boost::type_erasure::_a>
> ...>
> {};
> 
> This would avoid some very dirty workaround I am seriously considering.
> 

It may or may not work.  I've implemented
most of what's necessary, but I might have
missed a few things.  I should get around to
it within a few weeks.

In Christ,
Steven Watanabe