[Seaside-dev] Issue 160 in seaside: halts not caught by error
handlers
codesite-noreply at google.com
codesite-noreply at google.com
Wed Sep 17 17:08:26 UTC 2008
Issue 160: halts not caught by error handlers
http://code.google.com/p/seaside/issues/detail?id=160
Comment #6 by da... at teleport.com:
I like the idea of #inContextDo: (how about #handleErrorsDuring:?). There
is a tight
coupling between the ExceptionSet and the exception handlers so making both
the
responsibility of the error handlers makes mucho sense.
You can avoid the nested #on:do: by using an ExceptionSet, but then inside
the
handler block you will end up using #isKindOf: or some other type checking
technique.
I think the rationale basically goes, 'you're in an error handler under
exceptional
conditions, so efficiency is not a priority' - this is used to justify both
the use
of #isKindOf: and nested #on:do:).
The good news is that with #inContextDo: the code is inside the error
handler and we
don't have to provide Seaside protocol.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
More information about the seaside-dev
mailing list