Re: [boost] [log] Comments

Subject: Re: [boost] [log] Comments
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-03-15 13:58:30

Andrey Semashev wrote:
> On 03/15/2010 01:45 PM, Vladimir Prus wrote:
> >
> > Looking at the proposed libraries, I see two major issues:
> >
> > * There's no default setup that is comparable with the two
> > mechanisms above.
> > BOOST_LOG_TRIVIAL has only severity and it appears adding
> > component information
> > is complicated. In a sense, it looks like the library
> > provides building blocks,
> > but not a solution I can immediately use.
>
> Right. There is no silver bullet for everyone. I learned that

[snip]

> Therefore, it's useful to provide a flexible library with a few most
> obvious and frequent cases available at hand and a great potential of
> extension and configurability.

Certainly a good approach.  The issue is determining the common use cases you should support.

> > * It appears that out of the box, the proposed library does
> > not address
> > this component/severity style of logging that I've
> > explained above. The proposed solutions at:
> >
> >     http://permalink.gmane.org/gmane.comp.lib.boost.devel/200793
> >
> > sound relatively complex.
>
> I can't provide logger features for every case. Sometimes users will
> have to extend the library. Writing a class template with a couple
> constructors and a trivial method doesn't look very complex to me.

Vladimir's point is that severity/component is a very common use case that you should support out of the box.  That's how our logging works, so Vladimir and I would have to recreate the same wheel if you don't provide direct support.

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