[self-interest] Debugging in the presence of error blocks

David Ungar ungar at me.com
Wed Sep 18 02:17:30 UTC 2013

How about middle button on the stack to turn off frame filtering?

- David
Sent from my iPhone, tap tap

On Sep 17, 2013, at 6:35 PM, Russell Allen <mail at russell-allen.com> wrote:

> Without thinking about it too much, would 
> doSomething: 'something' IfFail: [halt]
> work differently?
> On 18/09/2013, at 10:57 AM, Chris Double <chris.double at double.co.nz> wrote:
>> I'm having issues with debugging and wonder if anyone as any tips. When
>> running code that uses error blocks, like this:
>> doSomething: 'something' IfFail: [|:e| error: e ]
>> If the method has an error and calls the error block in IfFail then the
>> debugger pops up with a stack that stops at the line where the error
>> blocks is created (ie. the one above). It doesn't show a stack inside
>> 'doSomething:IfFail:' where the error actually occured.
>> Is there a way to recover this information? At the moment if I run some
>> Self code that deep inside internals it does an [|:e| error: e] block
>> then I lose the context of where the error actually occured and only get
>> the context of where it is handled.
>> -- 
>> http://www.bluishcoder.co.nz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.selflanguage.org/pipermail/self-interest/attachments/20130917/1a0193ad/attachment.html>

More information about the Self-interest mailing list