Rule Definition
V60ExceptionCompatibility property must be set to YES
You can have only a single onException block within a try block, and you cannot specify an exception type.
You can use the sysLib.currentException variable to determine the nature of the problem. This variable is only available in V60 compatibility mode.
Exceptions do not propagate beyond the part in which they occur—for instance, if an error occurs within a function called by a try block, the try block never receives an indication that the exception was thrown.
Hard I/O errors terminate the application unless you set the handleHardIOErrors program property to YES. In that case, EGL throws an exception so the program can handle the hard I/O error itself.
You cannot throw your own exceptions.
Remediation
Try to always have the V60ExceptionCompatibility set to YES.
Related Technologies
Technical Criterion
PCI-DSS4-Requirement-6.2.4 - Software engineering techniques or other methods are defined and in use by software development personnel to prevent or mitigate common software attacks and related vulnerabilities
About CAST Appmarq
CAST Appmarq is by far the biggest repository of data about real IT systems. It's built on thousands of analyzed applications, made of 35 different technologies, by over 300 business organizations across major verticals. It provides IT Leaders with factual key analytics to let them know if their applications are on track.