M
Marian Edu
Guest
[quote user="Laura Stern"] First the simple answer: No - there is no way to trap the error message of a STOP condition. [/quote] Laura, then that's the first thing that can be fixed... thing everyone agree that we should be able somehow to catch the message (might be file not found, invalid parameters, not compiling - yeah, include parameters anyone??), since we can catch the stop would be nice to know why the stop occurred in the first place isn't it? 
Then, it was a discussion not so long ago about having a 'catch-all' or 'catch the not caught' errors/exceptions... not that much can be done if that happens but at least get the chance to log it and maybe the stacktrace will give one some useful information to help fixing the code.
Continue reading...
Then, it was a discussion not so long ago about having a 'catch-all' or 'catch the not caught' errors/exceptions... not that much can be done if that happens but at least get the chance to log it and maybe the stacktrace will give one some useful information to help fixing the code.Continue reading...