Re: [boost] RFC: Separating Boost.Python from Boost

Subject: Re: [boost] RFC: Separating Boost.Python from Boost
From: Niall Douglas (s_sourceforge_at_[hidden])
Date: 2015-05-30 08:48:08

On 30 May 2015 at 2:22, Peter Dimov wrote:

> Stefan Seefeld wrote:
> On 29/05/15 06:31 PM, Peter Dimov wrote:
> > > As one data point, ASIO is an independent library that has its own 
> > > releases but is still part of the Boost release.
> >
> > What do you mean by "independent" ? How does an ASIO release relate to a 
> > Boost release ?
> 
> https://think-async.com/Asio/AsioAndBoostAsio

Standalone ASIO is also the proposed reference Networking TS 
implementation. I am unsure if that part will be contributed to 
Boost.

> It's an interesting relationship, but ASIO has existed before becoming part 
> of Boost, which is probably why Chris still maintains both forks.

Some corporations have explicit blanket bans for all Boost libraries 
except X, Y and Z due to the header only problem. Standalone ASIO 
explicitly does not mention Boost in its name to work around that 
fact.

Niall

-- 
ned Productions Limited Consulting
http://www.nedproductions.biz/ 
http://ie.linkedin.com/in/nialldouglas/