2 Jul
2005
2 Jul
'05
6:30 p.m.
On 6/30/05, Greg Landrum <greg.landrum@gmail.com> wrote:
martin.ecker@tab.at wrote: This was exactly the problem; adding a call to boost::logging::set_log_caching(false) cleared up the ordering problems.
I had misunderstood the purpose of log caching.
It is a behaviour described in documentation. The caching is turned on by default, in order to allow the entries logged _before_ log initialisation not to be lost. -- Best regards, Zigmar