24 Feb
2023
24 Feb
'23
2:46 p.m.
On Fri Feb 24 14:28:34 2023 +0000, **** wrote:
Paul Gofman replied on the mailing list:
Yes, isn’t it better to just name the functions differently or put some info in the message itself? If it is a problem for winrt maybe we’d better introduce a new trace macro with extra context? Note that if the log is from slightly different version the line numbers won’t match. I think at very least this should be enabled by special debug channel, making it always there will increase the log size with a noise which is not needed most of the time.
I think even if the line numbers don't match exactly it is still helpful.
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.