D
dbeavon
Guest
@peter thanks for letting me know that there have already been discussions around the "escaping" errors (they may be handled by the remote client but they are unhandled in the PASOE agent.) Ideally we could hook into first-chance errors as well as the escaping errors. In .Net we have an appdomain with events for both: System.AppDomain.FirstChanceException System.AppDomain.UnhandledException Also, the individual U/I technologies may have some similar events as well, eg. Windows.UI.Xaml.Application.UnhandledException I would definitely hook into errors if there was a mechanism (and providing it performed reasonably well). @Laura, thanks for the pointer to -undothrow. I had seen that option in the past but it seemed that it was best suited to compiling at runtime, IE. for legacy programs that are compiled dynamically and don't otherwise have a default error handling declaration. I don't think I would trust our code to run without the explicit BLOCK-LEVEL directives anymore. As I recall, when omitting that directive we had to override the ON ERROR phrase of every loop that exists in our code, because otherwise the default error handling was so problematic. Thankfully those days are behind us.
Continue reading...
Continue reading...