Re: [boost] [transaction] New Boost.Transaction library under discussion

Subject: Re: [boost] [transaction] New Boost.Transaction library under discussion
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-01-29 08:17:34

vicente.botet wrote:
> From: <strasser_at_[hidden]>
> > Zitat von "vicente.botet" <vicente.botet_at_[hidden]>:
> >
> >>> any ideas for a namespace?
> >>
> >> transactions?
> >
> > hmm, I assumed that was against some boost naming
> > guideline, but I see there are a number of libraries
> > that use the plural (for no apparent reason?).

As already noted, it isn't against the guidelines, but is discouraged when another, suitable alternative exists.

> > better. if we can come up with with something to the effect of
> > "transaction processing library" (but not "tpl") I'd prefer
> > that but I guess "transactions" is ok.

I'm no fan of library names that include the word "library," even in abbreviated form.  Besides, as noted elsewhere, short names can be produced via aliases.  The full name should be distinct so as to avoid conflicts with future libraries.

transact?

> I'd also prefer a short name, but we need one that is enough
> significant to be adopted by the Boost community. Quite often
> transaction is abreviatted as "tx", what about "txl"?

Again, no "l" on the end.  I've never seen "tx" as the abbreviation, though I have seen "txn."  Still, I wouldn't want either to be the namespace name.

I think "transactions" is fine, but "transact" is shorter and seems appropriate.

_____
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.