Displaying 2 results from an estimated 2 matches for "s_upsdebug_escapedascii".
2023 Jan 15
1
logging strategy
...ith escapes, because that's
what Fortress output smells like so far, rather than flipping to all
hex (if I read groovy right).
Totally fair point about not changing s_upsdebug_ascii (but I think we
shouldn't worry about forks as socially they should contribute back). I
will just add a new s_upsdebug_escapedascii and friends -- works for me.
2023 Jan 15
1
logging strategy
Cheers,
I don't think there is any particular strategy, at least not one I'd know
of either :) So it is mostly ad-hoc, to keep smaller verbosity numbers
reasonably quiet, and sufficient info to see the logic progression at a
given debug level (e.g. if major milestones of a routine are logged at
level N, further traces like "I saw value X here" would be N+1 or more).
De-facto