Yes, the bug was about conversion of `upsdebugx()` and friends to macros,
so actual methods (and their parameter evaluations) only waste CPU cycles
when the verbosity level is high enough. Otherwise lots of logic was
executed to prepare method arguments only for it to bail out in the first
line.
On 7/5/23 03:17AM, Jim Klimov wrote:
Ah, I thought you missed in my earlier reply the part about a bug with debug printouts in 2.8.0 (fixed on master since),
did not comment on that when you replied with quoting... So, for now options are to bump debugging to 3+ or to build
your own in one of
Ah, I thought you missed in my earlier reply the part about a bug with
debug printouts in 2.8.0 (fixed on master since), did not comment on that
when you replied with quoting... So, for now options are to bump debugging
to 3+ or to build your own in one of many ways possible :\
On Wed, Jul 5,
