1254389201.7656.3.ca...@localhost
Content-Type: text/plain; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
On Thu=2C 2009-10-01 at 03:29 +=2C Brian Bloniarz wrote:
I.e. why does an exception raised during exception handling get
propagated past the
Sorry for the garbled post, this should hopefully be plain text:
On Thu, 2009-10-01 at 03:29 +, Brian Bloniarz wrote:
I.e. why does an exception raised during exception handling get
propagated past the exception that triggered the handler?
Because it's the obvious and sensible thing to
Exception handling code should generally be assumed to work, so if
something goes wrong there you would normally like to know about it.
Also, there is nothing preventing you from wrapping the rescue code in
further exception handling, however, if the initial error were raised
upon encountering a
On Thu, 2009-10-01 at 03:29 +, Brian Bloniarz wrote:
I had a question about onException friends: what's the rationale
for having:
(error foo) `onException` (error bar)
give bar and not foo?
I.e. why does an exception raised during exception handling get
propagated past the exception
I had a question about onException friends: what's the rationale
for having:
(error foo) `onException` (error bar)
give bar and not foo? I.e. why does an exception raised during
exception handling get propagated past the exception that triggered
the handler?
Most examples I can think for
