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

2019-01-07 Thread Martin Braun
I've started to summarize this thread in a GREP PR: https://github.com/gnuradio/greps/pull/16 On Sun, Jan 6, 2019 at 1:58 PM Martin Braun wrote: > Hi all, > > there's been a little discussion outside of this thread, and I'd like to > consolidate all the points. Marcus, I and some others have

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

2019-01-06 Thread Martin Braun
Hi all, there's been a little discussion outside of this thread, and I'd like to consolidate all the points. Marcus, I and some others have also discussed some things on chat, too, and of course there's Jared's and Michael's comments here. Let me summarize: - We would like to drop any kind of

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

2018-12-28 Thread 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

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

2018-12-28 Thread U L
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

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

2018-12-28 Thread Kevin Reid
On Fri, Dec 28, 2018 at 2:43 PM Müller, Marcus (IEH) wrote: > For them, that's very important, as they use that to supply resilient > infrastructure. I hope I'm representing the idea kinda correctly here: > They might want to log system events ("SUPERVISOR: INFO system load > surpassing 75%")

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

2018-12-28 Thread IEH
Hi Martin, hi Community, first of all: thanks for all the fish err GREPs! We need to kick off this discussion. So, this PR is very dear to my heart, because I consider log4cpp to be an especially problematic dependency. And I consider our logging to be subpar considering the size of the code

[Discuss-gnuradio] [GREP] Remove log4cpp

2018-12-27 Thread Martin Braun
This GREP was recently submitted here: https://github.com/gnuradio/greps/blob/master/grep-0013-remove-log4cpp.md We may or may not go through with this. However, we like to kill dependencies (hey there node.js developers :D ), and log4cpp has some issues of its own that we're currently