RE: [Boost-users] Re: Bad interaction between boost::bindandBoost.Python?

From: Nat Goodspeed (ngoodspeed_at_[hidden])
Date: 2004-09-23 08:13:25

> -----Original Message-----
> From: David Abrahams [mailto:dave_at_[hidden]]
> Sent: Thursday, September 23, 2004 8:24 AM
> To: boost-users_at_[hidden]
> Subject: [Boost-users] Re: Bad interaction between
> boost::bindandBoost.Python?
> 
> In principle your boost/python header has to be #included first
[before boost/bind]
> anyway, at least if you intend your code to run on POSIX.  

[Nat] ? I don't understand why that would be? Shouldn't each header
#include everything to make it self-sufficient, rather than depending on
the includer's prior #includes?

> 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.

[Nat] That's fair, and thanks for testing it. But given the amount of
time I've spent so far on this 1.31.0 upgrade, I'm going to lay low for
a few days before announcing that I intend to upgrade to yet another
version of Boost... ;-)