From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-06-03 06:16:37
On Thursday 02 June 2005 20:39, David Abrahams wrote:
> > Figured out and fixed. In several places, the global value of
> > BOOST_BUILD_PATH was manupulated. When loading user-config.jam and
> > site-config.jam, the value of BOOST_BUILD_PATH inside .ENVIRON was used,
> > and it did not include changes made to the global value, so some paths
> > (like root of Boost.Build) were missing.
> This was certainly my fault, but there's a design practice that could
> have prevented it: do not change the values of parameters to functions
> (or to programs).
> IOW, if you want to make something that's not quite the same as the
> BOOST_BUILD_PATH environment variable, call it something else. Using
> a functional style it's harder to make mistakes, and easier to keep
> track of how the state of the program evolves.
Noted, it probably would be better that have modules.load-path variable or
something. OTOH, that code was not written by me, so I've just applied the
simplest fix possible.
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk