|
Boost : |
Subject: Re: [boost] [log] Boost.Log formal review
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2010-03-13 10:55:30
On 03/12/2010 02:53 PM, Stewart, Robert wrote:
>
> The solution is for libraries that wish to communicate such
> information -- which would otherwise be logged by the library -- via
> a callback API. Such an API is reasonably within the scope of
> Boost.Log (even if that turns out to not be Andrey's library). IOW,
> Boost.Log can define an API and some functionality to standardize the
> mechanism for reporting information that would be logged, such that
> an application can tie that reporting into any logging system.
>
> Thus, Boost libraries should not log via Boost.Log but should report
> loggable information via a Boost.Log-provided callback API that can
> be connected to Boost.Log or any other logging library of the
> application's choice. Then, all Boost libraries that wish to report
> loggable information use one API for reporting and an application
> makes just one call to connect them all to its preferred logging
> library.
You may be right. I just wanted to make it clear that the proposed
library is not a proposal of such API.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk