[Boost-users] Re: Bad interaction between boost::bind and Boost.Python?

From: David Abrahams (dave_at_[hidden])
Date: 2004-09-23 07:23:33

"Nat Goodspeed" <ngoodspeed_at_[hidden]> writes:

> I'm trying to upgrade from Boost 1.30.2 to 1.31.0 today, but this bug is
> turning into quite a problem because of deep nesting of our own #include
> files. It hasn't yet become a show-stopper; but it's certainly taking me
> a great deal of effort to try to propagate every #include
> <boost/python*> -- and every file that includes it! - higher in its
> includer's #include list than any #include <boost/bind.hpp>. Please tell
> me there's a better way.

In principle your boost/python header has to be #included first
anyway, at least if you intend your code to run on POSIX.  All I can
suggest is that you try the latest Boost CVS state, which doesn't have
this problem.  A new release of Boost is imminent anyway.

HTH,
-- 
Dave Abrahams
Boost Consulting
http://www.boost-consulting.com