[boost] Re: Update of the (not yet officially proposed) FunctionTypeslibrary

From: Tobias Schwinger (tschwinger_at_[hidden])
Date: 2005-03-11 10:04:07

Pavel Chikulaev wrote:
> "Tobias Schwinger" <tschwinger_at_[hidden]> wrote in message 
> news:d0rs1h$22j$1_at_sea.gmane.org...
> 
>>>is_same<
>>>    function_type_parameters< void(int,float) >::signal_type,
>>>    signal2<void, int, float>
>>
>>It is possible already:
> 
> No. You can unpack arguments, but you can't choose signal2
> or signal3 and so on.

You're right - unpack_args won't help, here. OK, then let's say:

    signal< function_type<plain_function,Seq>::type >

>>IIRC there is no version of signal taking an MPL-Sequence.
>>'signal<my_function>' should work, though.
> 
> 
> I meant a bit another thing.
> 
> //From your examples:
> typedef void my_function(int);
> 
> typedef function_type_signature<my_function> my_signature;
> 
> typedef mpl::push_back<my_signature,float>::type my_modified_signature;
> 

> boost::signal<my_modified_signature::representee>. == boost::signal<void (int, 
> float)>
^^^ This is invalid code and not part of my example (can't compare types 
with '==').

> //You can't do the same for signalN!!!!!

I already explained why, in my previous post!

Regards,

Tobias