Re: [boost] [log] Boost.Log formal review closing down

Subject: Re: [boost] [log] Boost.Log formal review closing down
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2010-03-17 17:53:43

----- Original Message ----- 
From: "Andrey Semashev" <andrey.semashev_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Wednesday, March 17, 2010 10:39 PM
Subject: Re: [boost] [log] Boost.Log formal review closing down

> 
> On 03/18/2010 12:33 AM, vicente.botet wrote:
>>
>>> On 03/17/2010 05:52 PM, Steven Watanabe wrote:
>>>> AMDG
>>>>
>>>> vicente.botet wrote:
>>>>> * Severity: I would like that any sink filters thie severity the
>>>>> log_record is not added at all. Could this optimization be taken in
>>>>> account. For example if severity must be GT error to be logged, the
>>>>> following will not evaluate the ineficient_function().
>>>>> BOOST_LOG_SEV(slg, normal)<<  ineficient_function();
>>>>
>>>> I'm pretty sure that if no sink is going to accept the
>>>> record, then inefficient_function will indeed not
>>>> be called.
>>>
>>> I confirm.
>>
>> Yes I see, but the log record will be build with all its attributes which will take more time than just checking for severity.
> 
> No, it won't. Only the attributes involved in filtering will be used.

Well all the attributes involved on filtering + creation of the log record. Is this not enough saving for 99% of the logs?

Vicente