The current state of logging is not adequate. If DEBUG is defined, some more printf()'s are added.
I am progressing on making the r3.0 update. It will add a lot of new features and it will modify existing ones. This will likely lead to bugs. Having good logging is crucial for diagnosing them.
A proper logging library should be used. I'll probably go with loguru because I have past experience with it, its features are nice and it uses printf() by default. j4-dmenu-destkop doesn't use iostream, so using a logging library which would use it would likely lead to problems.
The current state of logging is not adequate. If
DEBUG
is defined, some moreprintf()
's are added.I am progressing on making the r3.0 update. It will add a lot of new features and it will modify existing ones. This will likely lead to bugs. Having good logging is crucial for diagnosing them.
A proper logging library should be used. I'll probably go with loguru because I have past experience with it, its features are nice and it uses
printf()
by default. j4-dmenu-destkop doesn't useiostream
, so using a logging library which would use it would likely lead to problems.