Subject: Re: [boost] New name of bjam.exe
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-07-20 06:51:00
Brian Ravnsgaard Riis
> On 20-07-2010 12:05, Artyom wrote:
> > "build" is not good as it some kind of "namespace pollution",
> > and is very problematic for systems with single "bin" path
> > - as most Unix like OSs.
> > So you need something unique starting with boost prefix as
> > namespace.
> > For example all mysql utilities start with mysql prefix
> > thus I think boost build should be something like
> > boost_build or boostbld, not really matter, the point is
> > clear.
> It is indeed, but I don't actually think I agree... except
> that "build" is too generic. This command will be typed into
> a console a hundred times a day in some cases, so it should be
> rather short. "bjam" was good in this regard, but not really
> accurate any longer, as Volodya states.
I disagree with your rationale. First, command history is available in all shells, even cmd.exe on Windows, so one isn't likely to type the name hundreds of times per day. Second, there are numerous mechanisms available for shortening a long name when that proves desirable, without imposing a single short name on all.
My suggestion: build_boost. While "boost" isn't a prefix in that name, it reads very nicely in English. Furthermore, if "Boost.Build" remains as a library/project name, then the reversal in "build_boost" is useful to avoid conflation of the two names. That is, the binary isn't the library/project and vice versa, so distinct but related names are useful.
Rob Stewart robert.stewart_at_[hidden]
Software Engineer, Core Software using std::disclaimer;
Susquehanna International Group, LLP http://www.sig.com
IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.