D
dbeavon
Guest
The problem with that suggestion is that you would have to implement it on the "first-chance" occurrence of the error (the top of the callstack), if you do it after the callstack starts to unwind, you lose the details. Similarly, in order to capture the details yourself as you suggested, you would have to know *exactly* in which part(s) of the code you need the custom CATCH 'es. But most of the time you don't even know exactly what part of the code is failing, only that it happens somewhere during a round-trip to appserver (which is enclosed in an outer DO/CATCH block). In practice a developer normally needs a *single* DO/CATCH block to wrap the nested business logic. The CATCH section would be where you place the consistent behavior for any failure that occurs at *any* time within the block. The "consistent behavior" that I mentioned often may need to save the original callstack details (which are not available by default in ABL).
Continue reading...
Continue reading...