Re: [boost] Moving the include directory to $BOOST_ROOT/include?(again)

Subject: Re: [boost] Moving the include directory to $BOOST_ROOT/include?(again)
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2015-06-02 09:28:56

> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Peter Dimov
> Sent: 02 June 2015 11:19
> To: boost_at_[hidden]
> Subject: Re: [boost] Moving the include directory to $BOOST_ROOT/include?(again)
> 
> Tom Kent wrote:
> > On Sun, May 31, 2015 at 7:30 AM, Peter Dimov <lists_at_[hidden]> wrote:
> >
> > > I want to reiterate my suggestion that we move Boost's include
> > > directory from $BOOST_ROOT to $BOOST_ROOT/include.
> >
> > Our organization has been following the example in the first pages of
> > the getting started guide [1][2] and using #include
> > <boost/header.path.hpp> with $BOOST_ROOT in our include path, so
> > changing that to 'include' would require major source changes to our
> > (and presumably lots of others') code bases.
> 
> The idea is that you'd change your include path to reference $BOOST_ROOT/include, without changing
a
> line of code.
> 
> I've been using this environment for a while and haven't encountered any breakages.

What about all the existing Visual projects and solutions?

I worry that even your extra environment variable for 'legacy stuff' will cause trouble.

Having been told by David Abrahams that environment variables are evil, and getting rid of
$BOOST_ROOT references,
it now seems that they will be essential.

I'm still struggling to understand the value of the benefits, compared with those risks.

Paul

---
Paul A. Bristow
Prizet Farmhouse
Kendal UK LA8 8AB
[phone]