Lars Fosdal 1792 Posted March 8, 2023 I assumed any unmatched on-events would have been silenced. If E is nil - logging will be incomplete in some cases, since I pass the exception object to Eurekalog to capture a callstack for the log. It probably would be quite rare, though. Share this post Link to post
SwiftExpat 65 Posted March 8, 2023 1 hour ago, Lars Fosdal said: I am starting to wonder if they should be rewritten I did not blanket re-write my handlers. I started from the top down combined with refactoring. From a debugger session point of view, it gives you a place to set a break point. That means you have to set 2 breakpoints. Share this post Link to post
Marco V 3 Posted March 9, 2023 I'm in the same ballpark as Lars. Quite often these are toplevel handlers for tcp/udp ip/comport etc threads. Share this post Link to post