Subject: Re: [boost] Logging library
From: Ivan Le Lann (ivan.lelann_at_[hidden])
Date: 2011-07-06 04:59:19
----- "Tigran Hayrapetyan" <tigran.human_at_[hidden]> a Ã©crit :
> >----- "Tigran Hayrapetyan" <tigran.human_at_[hidden]> a Ã©crit :
> >> Hello dear Boost community
> >> Existing logging libraries which I used, are writing log messages
> >> linearly,
> >> just one after another.
> >> In contrast, as we know, almost any application's working structure
> >> not
> >> linear, but hierarchical instead, i.e. functions which call other
> >> functions,
> >> and so on.
> >Have you tried Boost.Log and its attributes ?
> As I understand, that features of Boost.Log library are for managing
> attributes of log messages, and not log messages (or their
> So the log messages are still placed linearly, and my proposal is to
> place them hierarchically.
NB: I'm not a Boost.Log expert at all. I was only curious.
And my understanding is that how to handle attributes is left to the sink backend.
I would try writing a new sink backend that handles a named_scope attribute.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk