M
marian.edu
Guest
Laura, Stefan’s case might not be a high priority (error status set on EOF/ENDKEY condition) but it is a bug and probably not very hard to get it fixed either, there is no note in documentation that error status should only be check right after the statement where no-error was used
While we are at it I think the documentation is also misleading about NUM-MESSAGES, I mean it does make sense when it says ”The NUM-MESSAGES attribute indicates the total number of errors that occurred during that statement.” only that, as others mentioned before, is not true if ERROR option is used with RETURN statement - there error status is set to true but NUM-MESSAGES is left zero
I do know there might be code out there that relies on using RETURN-VALUE but would it be an option to consider adding the error expression also as an error message when RETURN ERROR is being used? Subsequently the AppError thrown if NO-ERROR isn’t used will still have the ReturnValue property set but there will also be a error message - NumMessages will be one and GetMessage (1) will return the same message. Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212
Continue reading...
Continue reading...