Folks,

In browsing through the recent 2.7 Squeak release, we noticed a bug in
Exception>>isNested.  That method is supposed to answer true or false to
indicate whether or not the active exception handler is enclosed in
another handler which
handles similar exceptions.  In the current release, the search for the
handler actually *sets* the active handler to be whatever outer handler
it finds.  From there, any further code execution would thus take place
in an incorrect exception environment with, let's just say, potentially
startling results at the application level.

The attached patch was installed in an up-to-date 2.7 image, and all
regression tests (see system category Exceptions-Tests) ran
successfully.  It should also be compatible with all versions of Squeak
back to 2.3.

Sorry for leaving that one in there,
Paul McDonough

on behalf of those at TFEI who sometimes write code too late at night
...