Unhandled classic exception
unhandled_classic_exception
Description
Finds calls that do not map every classic exception the callee can raise
Extended Information
A classic exception that is raised with RAISE and not mapped in the EXCEPTIONS addition of the call
ends in the runtime error RAISE_EXCEPTION. TRY ... CATCH cx_root does not catch it.
missingOthers: reports CALL FUNCTION and method calls with an EXCEPTIONS list without OTHERS.
Not reported if the function module or method is known and every exception it declares is listed,
for CALL FUNCTION ... DESTINATION this includes SYSTEM_FAILURE and COMMUNICATION_FAILURE.
CALL FUNCTION ... STARTING NEW TASK, IN UPDATE TASK and IN BACKGROUND are not checked.
missingExceptions: reports calls without EXCEPTIONS of a method or function module that declares classic exceptions,
this includes functional calls, which cannot have EXCEPTIONS.
With allowLiteralArguments, a method call whose arguments are all literals or me is not reported.
missingErrorMessage, off by default: reports every CALL FUNCTION that does not list the predefined exception error_message,
the policy "always list error_message". Any function module can send a MESSAGE without RAISING, directly or from a
function module it calls, and OTHERS does not catch it. Outside dialog, in HTTP handlers, RFC and background jobs,
a message of type E or A ends the processing. Use it together with check_subrc, otherwise error_message turns a
visible abort into a silent failure. Not reported: DESTINATION, STARTING NEW TASK, IN UPDATE TASK, IN BACKGROUND,
EXCEPTION-TABLE, and function modules in the registry with class-based exceptions.
Signatures are taken from the registry, including dependencies. Methods and function modules that are not
found (void) are only checked by missingOthers.
Does not report any issues if the code contains syntax errors