[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: A GNUNET_log oddity
From: |
Christian Grothoff |
Subject: |
Re: A GNUNET_log oddity |
Date: |
Tue, 31 Aug 2021 19:52:54 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 |
On 31.08.21 15:41, Alessio Vanni wrote:
>> As for applications using libgnunetutil, well, they again need to copy
>> that mechanism into their configure-scripts, or they won't get
>> DEBUG-level logging. I think that's OK. That said, we _may_ be able to
>> improve the (developer) handbook documentation on logging on this point.
>
> Then if no one minds, I'm going to flip the value given to
> GNUNET_EXTRA_LOGGING when the configure script doesn't define it, from 0
> to 1, so that third-party application developers can leverage the full
> range of error levels during development (e.g. me, while I test things
> out in my application and decide to get swamped by messages only when
> something strange happens.) I'm not sure if giving larger values, like
> GNUnet does, is meaningful when the goal is to get debug messages. If
> even more verbosity is required, developers should probably use their
> own mechanism.
Sounds good to me.
-Christian