From @ilyabelikin

Hi there,

example​:

try{
  foo;
  CATCH { die 1 }
}

S04, L800​:

A C<CATCH> block sees the lexical scope in which it was defined, but
its caller is the dynamic location that threw the exception. That is,
the stack is not unwound until some exception handler chooses to
unwind it by "handling" the exception in question. So logically,
if the C<CATCH> block throws its own exception, you would expect the
C<CATCH> block to catch its own exception recursively forever. However,
a C<CATCH> must not behave that way, so we say that a C<CATCH> block
never attempts to handle any exception thrown within its own dynamic scope.
(Otherwise the C<die> in the previous paragraph would never work.)

Ilya

From @kyleha

There's now a test for this in S04-statements/try.t​:

{
  my $catches = 0;
  try {
  try {
  die 'catch!';
  CATCH {
  die 'caught' if ! $catches++;
  }
  }
  }
  is $catches, 1, 'CATCH does not catch exceptions thrown within it';
}

From @jnthn

On Tue Jun 30 12​:33​:03 2009, KyleHa wrote​:

There's now a test for this in S04-statements/try.t​:

{
my $catches = 0;
try {
try {
die 'catch!';
CATCH {
die 'caught' if ! $catches++;
}
}
}
is $catches, 1, 'CATCH does not catch exceptions thrown within it';
}

Which Rakudo now passes after a fix. I didn't find the test in the test
file though...oddness. Anyway, added it and it passes. :-) Closing ticket.

Thanks,

Jonathan

The RT System itself - Status changed from 'new' to 'open'

@jnthn - Status changed from 'open' to 'resolved'

@moritz - Status changed from 'resolved' to 'open'

From @moritz

The test fails again (and has been doing that for quite some time, so
I'm reopening the ticket).

From @bbkr

still broken in NOM branch

From @moritz

Finally fixed thanks to mls, tested in catch.t

@moritz - Status changed from 'open' to 'resolved'