If the
v60ExceptionCompatibility property
is
set to YES, it has the following effects:
- 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
V6 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.
EGL sets v60ExceptionCompatibility to
YES automatically
when migrating code from EGL version 6 or VisualAge® Generator.
You do not need
this property for new code. You can set this property to different
values
in different programs within a run unit, but this practice can cause
errors.