----- "Tigran Hayrapetyan" <tigran.human@gmail.com> a ?crit :
----- "Tigran Hayrapetyan" <tigran.human@gmail.com> 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 is not linear, but hierarchical instead, i.e. functions which call other functions, and so on. (...)
Have you tried Boost.Log and its attributes ?
http://boost-log.sourceforge.net/libs/log/doc/html/log/detailed/attributes.h...
http://boost-log.sourceforge.net/libs/log/doc/html/log/detailed/utilities.ht...
As I understand, that features of Boost.Log library are for managing attributes of log messages, and not log messages (or their placements) themselves. 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. http://boost-log.sourceforge.net/libs/log/doc/html/log/extension.html#log.extension.sinks<http://boost-log.sourceforge.net/libs/log/doc/html/log/extension.html#log.extension.sinks>
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 collection<http://www.boost.org/> . However, I think also that custom sink backends probably can provide same functionality as my header file. I will try it too. Thanks, Tigran