[squeak-dev] able to resume non-resumable Errors in the Debugger

Eliot Miranda eliot.miranda at gmail.com
Thu Jun 25 02:08:23 UTC 2015

Hi Chris,

    it has ever been so and is very useful.  Personally I would prefer the proceed ability if exceptions to be changeable depending in circumstance.  eg initialise a canPeoceed inst car to the class default but allow knowledgeable clients to alter the status quo.  Often exception designers err on making errors not proceedable.  For example accessing a directory's contents.  If implementing find (1) it's useful to be able to proceed with an empty collection, to skip directories one doesn't have the permissions to read.

Eliot (phone)

On Jun 24, 2015, at 1:02 PM, Chris Muller <asqueaker at gmail.com> wrote:

> Error signal.  3   "Error, but then press Proceed ----> 3"
> [Error signal] on: Error do: [ : err | err resume: 3 ]
> "IllegalResumeAttempt, but then press Proceed -----> 3"
> This is not a regression from 4.5, but something to be aware of when
> using the debugger, because Error signalers assume the code that
> follows will not be run.

More information about the Squeak-dev mailing list