Re: [boost] [mpl] bug: mpl::is_sequence< mpl::int_<1> > fails to compile

From: Tobias Schwinger (tschwinger_at_[hidden])
Date: 2006-05-09 06:14:56

David Abrahams wrote:
> Tobias Schwinger <tschwinger_at_[hidden]> writes:
> 
> 
>>>foo<is_sequence<int(int,long)>::value>::bar() calls one function in TU
>>>#1 and another function in TU #2.  
>>
>>True. foo<true> and foo<false> are two different classes...
>>
>>
>>>Clear yet?
>>
>>Sorry, not quite. Where is the redefinition?
> 
> 
> Look up the definition of ODR in the standard and you will see that
> this qualifies.
> 

Right, it worked [ 3.2-5-2 ]. Thanks for the hints!

But is it a good idea to have a builtin type model a sequence in the first place?
I don't think so, because there can be a PoI before the specialization is defined!
It's just as error prone without 'is_sequence'...

Regards,

Tobias