$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
From: Jonathan Turkanis (technews_at_[hidden])
Date: 2005-07-06 17:42:15
Rob Stewart wrote:
> From: Vladimir Prus <ghost_at_[hidden]>
>> Jonathan Turkanis wrote:
>>> Vladimir Prus wrote:
>>>> Jonathan Turkanis wrote:
>>>>
>>>>> My rational is simple: in "Boost build system," Boost is an
>>>>> adjective (a proper one) and "build system" is a noun modified by
>>>>> the adjective. Capitalizing "Boost" and "build" but not "system"
>>>>> obscures the structure.
>>>>
>>>> I think "Boost.Build" is a name of software product. OTOH, "Boost
>>>> build system" means "a build system used by Boost", and says
>>>> nothing specific about that build system at all. So, just pick the
>>>> semantics you want to convey in each specific case.
>>>
>>> This sounds right to me.
>>>
>>> But there was a third choice: the Boost Build System. My current
>>> impression, from the various comments so far, is that this term
>>> doesn't properly name anything: the correct proper name is
>>> Boost.Build. Is that right?
>>
>> Yea, the "brand name" is Boost.Build, as far as I'm concerned.
>
> I'll weigh in, too. Dave's position that "Boost.Build" is to
> "the Boost Build" system as "Boost.Bind" is to "the Boost Bind
> library" is compelling.
I still don't see it, but I've stopped worrying about it.
> "Boost Build System" is akin to "Boost
> Bind Library."
That's just stating a conclusion.
> I'll grant that we don't have many "systems" in
> Boost (installation system? documentation system?), but leaving
> room for the future argues for keeping "system" lower case.
Boost.Build is a "system" only because it's a "build system," and build systems
are (apparently) systems.
> I suggest using "Boost.Build" and "the Boost Build system."
I'm going to avoid the issue by using "Boost.Build."
Jonathan