Subject: Re: [boost] Logging library
From: Tigran Hayrapetyan (tigran.human_at_[hidden])
Date: 2011-07-09 12:24:20
>----- "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
> I would try writing a new sink backend that handles a named_scope
I'm also new to Boost.Log library. I didn't knew that such library exists in
Boost as it is not an official part of Boost libraries
However, I think also that custom sink backends probably can provide same
functionality as my header file. I will try it too.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk