Hehehe There are others out there either on another timezone, or not sleeping :) I put the code into VC71 and have been playing with it. I got the same error. (it WASN'T namespace weirdness with VC) (I get soo grouchy with VC I tend to blame the compiler too quickly) I then degenerated into digging through the MPL reference and trying different examples in the project. As of yet, though nothing useful to report. I think I am going to bed. I

-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Joel Sent: Thursday, May 05, 2005 10:54 PM To: boost@lists.boost.org Subject: [boost] Re: [MPL] is_sequence problem

Joel wrote:

...

Brian Braatz wrote:

...

Could it be as simple as missing the namespace on the is_sqeuence<> call?

Have you tried it? If it was, I wouldn't have bothered the list ;-) Try replacing int_<0> with int.

I think the problem is the way mpl::is_sequence is implemented. It tries to detect the presence of a "tag" typedef and a "begin" typedef and concludes that a type is an mpl::sequence if it has both. I've complained a long time ago about this. I think this behavior is error prone. It's quite easy to come up with a situation where I have a type T with a "tag" and a "begin" but is not an MPL sequence. There must be a better way. MPL should not monopolize on the usage of "tag" and a "begin" in a type.

Anyway, in any case, is_sequence<int_<0> >::value should never fail to compile.

Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost