Re: [boost] Candidate logging library and static initialization/destruction

From: John Torjo (john.groups_at_[hidden])
Date: 2007-11-27 03:14:35

Emil Dotchevski wrote:
>>> The way I solved that in a (far more limited!) logging library for our
>>> own use was the following:
>>>
>>> - Never destroy the logging data structures -- allow them to leak. No
>>> risk of static ordering issues.
>>>       
>
> Why not provide initialization and clean-up functions and let the user
> call them explicitly?
>
>   
In v2, this is handled quite differently. So it doesn't apply - but I 
have to come up with a solution :)

Best,
John

-- 
http://John.Torjo.com -- C++ expert
... call me only if you want things done right