Re: [Discuss-gnuradio] [GREP] Remove log4cpp

[Michael Dickens]

I'll second what Jared wrote, and add the following: I'd like -any- logging GR uses to provide protected printing, such that logged messages do not interleave. [Obviously, unlogged messages might interleave / intermix; all depends on the actual printing interface.] Trying to parse such interleaved messages is a total PITA. I've personally gone so far as to implement a mutex interface via SWIG from C++ to Python, to allow logged messages in both to not interleave. Ideally, all of stdout and stderr would be redirected to the logging interface, regardless of language source. Log4Cpp provides the printing blocking (non-interleaving) functionality, though it doesn't coerce both C++ and Python into the same printing interface (at least in my testing). - MLD

On Fri, Dec 28, 2018, at 7:08 PM, U L wrote:

I think many users, myself included, use logs for debugging.  I would hesitate to have the log messages propagate through the very system that you are trying to debug with said messages.  I would rather the logs be emitted from the system under test as simply and promptly as possible.  I think that hierarchical organization within the logs should be handled by log metadata.  It's not clear that one would want to impose the same naming hierarchy on logs as you do your flowgraph, but one could do so if desired.

Jared.