M
marian.edu
Guest
Not that I’m arguing wether or not framework components should/could ‘pollute’ the error status or anything but the question is why do you even check the error-status if you don’t have any statement with NO-ERROR in that piece of code? The documentation is pretty clear on that one (imho)… “ERROR-STATUS - A handle to error information on the last statement executed with the NO-ERROR option.” If you have framework components that might throw errors (please add the throws options to methods) then either use catch block (the new way) or stick to NO-ERROR/ERROR-STATUS but what you try there is probably not what you want anyway, if one of the methods throws an error you don’t even get to the point where you check ERROR-STATUS. Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212
Continue reading...
Continue reading...