24 Feb
2023
24 Feb
'23
4:07 p.m.
On Fri Feb 24 15:55:57 2023 +0000, **** wrote:
Paul Gofman replied on the mailing list:
On 2/24/23 08:46, Rémi Bernon (@rbernon) wrote: > > And I don't think renaming the functions is a solution, it can only be done after you've discovered the ambiguity. > > In the end having `class_name_interface_name_method_name` function vs `file_name:interface_name_method_name` in the log is exactly the same. It makes the code little less verbose, which, when interface names or function names alone get close to 200 char, is desirable, > while making the one class per file (imho is a good practice) more useful. > Yes, sure. But maybe another macro then? Or, maybe, same macro TRACE can check another define macro enabling extended context and add this info to the message itself instead of header?
It seems overly complicated when we can just add the context. Many other projects just do this, I think it's quite straightforward.
I would be okay with a specific channel to have it only optionally enabled, but I'm not sure to see why it'd bad to print it all the time and it defeat a bit the purpose of getting more context in logs upfront.