Re: [boost] Generic object construction

From: Andy Little (andy_at_[hidden])
Date: 2006-09-25 19:04:06

"Andy Little" <andy_at_[hidden]> wrote in message 
news:ef9m9h$lqg$1_at_sea.gmane.org...
>
> "Andy Little" <andy_at_[hidden]> wrote in message
> news:ef9lkt$k1l$1_at_sea.gmane.org...
>>
>> "Larry Evans" <cppljevans_at_[hidden]> wrote in message
>> news:ef98no$58f$1_at_sea.gmane.org...
>>
>>> AFAICT, This similar to the problem I ran into with the array extension
>>> to Andy Little's fusion matrix.  Andy wanted the ability to initialize
>>> with something like:
>>>
>>>   maxtrix<...whatever...> a_matrix
>>>     ( a0_0, a0_1, ... , a0_m
>>>     , a1_0, a1_1, ... , a1_m
>>>     ...
>>>     , an_0, an_1, ... , an_m
>>>     )
>>
>> Actually I think what I want is more like :
>>
>> matrix<..> ( view_sequence<Function1<seq1,seq1a>, Function2<...>,
>> Function3<...>, Function4<...>....>() );
>
> In fact this should probably be:
>
> matrix<...> m1;
> matrix<...> m2;
> matrix<...> (view_sequence<Function1<M1,M2>, Function2<M1,M2>,
> Function3<M1,M2.>,...> >(m1,m2) );

Question is, is that the same as transform_view?, but I don't think it is. 
transform_view is:

view_sequence<F<at<M1,1>,at<M2,1> > ,F<at<M1,2>,.at<M2,2> >,...> etc.

IOW each function gets to see only its elements, not the whole input sequence.

I think that is a difference

regards
Andy Little