Re: [boost] boost::log review (printf style api)

Subject: Re: [boost] boost::log review (printf style api)
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-03-15 08:26:56

Vladimir Batov wrote:
> > From: "Tom Brinkman" <reportbase2007_at_[hidden]>
>
> > This boost::log library should not be approved without a simple
> > "C" friendly api. That being a printf style api.
>
> I second that. If we want the library to be anything beyond an
> academic toy, it has to be practical and deployed, it should to
> be easy to retrofit such new library into *existing*
> projects. The ovewhelming majority of the projects I've been
> involved in use printf-style formating for logging. On a large
> scale the std::stream-style formatting failed miserably and
> programmers (well, at least those I worked with) voted with
> their feet/hends/whatever.

Steven noted support for Boost.Format, so this library effectively supports streaming and printf-style formatting.  I'll add that our own long lived logging API supports both styles and both are used regularly, often by the same developer.  Consequently, while I think Tom over generalizes from his specific experiences, it is valuable to have efficient support for both formatting styles.

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