QVT12 — Issue 19178 resolution is rubbish

The proposed resolution for Issue 19178 'clarifies' nested exceptions.

It is wrong. The confusion arises from C++'s problem with a nested exception in a destructor not in a handler. QVTo has no destructors so there is no problem.

Issue 19178 should be closed without change.

Do not apply chnages from Issue 19178 resolution.

For ease of reference, the erroneous 19178 revised text was:
In 8.2.2.13 TryExp add
The selected exceptClause completes before the TryExp completes. Consequently if an exception is
raised during execution of the exceptClause, the execution of the exceptClause cannot complete and so
execution of the transformation terminates without any further changes occurring. The trace records
may be examined to determine what actions the transformation performed prior to termination.
We just need to make clear that the handling of nested exceptions is normal.