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

From: David Abrahams (dave_at_[hidden])
Date: 2004-09-23 13:19:43

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

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

It's not that.  Python imposes the restriction that Python.h must be
included before any system header so it can set some configuration
macros, probably because POSIX requires it.  Boost.Python needs to
get in and wrap Python.h, ergo...

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