M
marian.edu
Guest
That’s a very good idea Rob, everyone with some OO background gets bite by this one when dealing with OO ABL 
I’m with Mike on having distinct errors for different causes: stop after, class(procedure) not found, I/O, lock timeout… but that will probably require more changes and there might not be many using that fine granularity level when catching errors. What intrigues me is you mention (several time) that this will work only for 'stop conditions that have error messages', what else is left out of this, something that we can still catch with on-stop or things that should never happen like GPF? Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212
Continue reading...
I’m with Mike on having distinct errors for different causes: stop after, class(procedure) not found, I/O, lock timeout… but that will probably require more changes and there might not be many using that fine granularity level when catching errors. What intrigues me is you mention (several time) that this will work only for 'stop conditions that have error messages', what else is left out of this, something that we can still catch with on-stop or things that should never happen like GPF? Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212Continue reading...