Boost logo

Boost :

From: Jeff Flinn (TriumphSprint2000_at_[hidden])
Date: 2005-05-26 08:18:50


"David Abrahams" <dave_at_[hidden]> wrote in message
> "Hendrik Schober" <SpamTrap_at_[hidden]> writes:
>> Caleb Epstein <caleb.epstein_at_[hidden]> wrote:
>>> [...]
>>> I really think the Getting Started guide is more than adequate, and is
>>> concise and easy to follow. There are gigantic yellow numbers next to
>>> the important steps. [...] really how much more hand-holding
>>> does one need?
>> OK, so I went to the that guide, downloaded boost
>> 1.32, downloaded bjam.exe, unzipped everything,
>> and typed, IMHO according to the guide,
>> C:\Temp\Download\boost\boost_1_32_0>..\bjam.exe bjam
>> "-sTOOLS=VC71_ROOT" stage
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Surely you didn't type any of that stuff?


> But where did you get the idea that VC71_ROOT was a legal toolset
> name?

Is there a reason that all of the xxx_ROOT variables couldn't just be ROOT?
Isn't the context defined by the "-sTOOLS=..." parameter? Removing these
additional names would certainly reduce the users conceptual load.

As I stated elsewhere, the lack of consistency in the TOOLS naming
convention for VC Toolset adds confusion as well.

msvc // VC6.5 can we add vc6_5?
vc7 // VC7 would vc7_0 be better?
vc-7_1 // VC7.1 why the dash? why not vc7_1?

These variations add unnecessary perceptual complexity. Kind of like having
different handles in different places on each cabinet in your kitchen. If
they were all:


the pattern is readily visible when viewing the table. The first time users
comfort level goes up magnitudes. Additionally the Toolset table would be
better placed immediately after the Item 5 example: 'bjam "-sTOOLS=vc7_1"
stage'. Also the two different terms 'Toolset' and 'TOOLS' adds complexity
as well. Using a single term for the concept and the command line parameter
would further reduce conceptual load.

By the way, many of these 'opinions' are based on reading the book "The
Design of Everyday Things" by Donald A. Norman. Oddly enough, most(if not
all) of the boost library interfaces follow guidelines discussed in the
book. :-)

Jeff Flinn

Boost list run by bdawes at, gregod at, cpdaniel at, john at