Re: [boost] [serialization] new STATIC_ASSERTION_FAILURE

From: David Abrahams (dave_at_[hidden])
Date: 2005-06-23 01:35:05

"Robert Ramey" <ramey_at_[hidden]> writes:

> In order to get desired behavior regarding invocation of auto-linking only
> when necessary I had to impose some restriction regarding sequening of
> #include statements.  The rule is:
>
> "all #includes from the boost/archive directory should preceed all #includes
> from the serialization directory."

Ouch, that's pretty scary.  #include order is notoriously hard to
control and maintain.  I'm not sure what's at play here, but I'm
guessing it's some phase-1 name lookup issue?  Can't you move it to
phase 2 (usually by using an unqualified call or specialization)?
-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com