Re: [boost] Re: Release schedule for 1.31.0

From: Tarjei Knapstad (tarjeik_at_[hidden])
Date: 2003-11-26 09:14:14

On Tue, 2003-11-25 at 16:24, Joel de Guzman wrote:
> Tarjei Knapstad <tarjeik_at_[hidden]> wrote:
> > On Sat, 2003-11-22 at 06:23, Joel de Guzman wrote:
> >> David Abrahams <dave_at_[hidden]> wrote:
> >>> David Abrahams <dave_at_[hidden]> writes:
> >> 

<snip>

> >> 
> > 
> > I just briefly browsed the code, and AFAICS this implementation limits
> > the number of elements in a tuple to 15 (correct me if I'm wrong
> 
> Nope. The limit is much higher than that: 50. And that's the limit of MPL's 
> vector. Care for a 100 tuple element? That's doable thanks to the boost
> preprocessor. If MPL can do it, so can Fusion.
> 
> << I think you looked at the phoenix tuple implementation. Try the
> sandbox >>
> 

D'oh, you're right. The implementation in the sandbox looks a lot more
like the business :)

<snip>

> > 
> > In any case, is there some short writeup somewhere about the significant
> > differences between the current tuple implementation and the one in
> > Spirit? I assume the compile time constants used in the Spirit tuple
> > implementation to limit the maximum number of elements are there for
> > efficiency reasons. Are there any other major changes?
> 
> The one used by Fusion is not the same as the one phoenix/spirit uses.
> It is based on the TR1 tuple specification:
>  http://www.osl.iu.edu/~jajarvi/publications/papers/tuple_proposal.pdf
> 

Thanks for clearing this up for me Joel!

Cheers,
--
Tarjei