Re: bug: clear_eh patricide after catch

2003-08-14 Thread Leopold Toetsch
Michal Wallace <[EMAIL PROTECTED]> wrote: > Here's a new test case for t/pmc/sub.t > > output_is(<<'CODE', <<'OUTPUT', "set_eh - throw - clear_eh"); > print "start\n" > newsub P20, .Exception_Handler, _handler > set_eh P20 > new P30, .Exception > throw P30 > prin

bug: clear_eh patricide after catch

2003-08-14 Thread Michal Wallace
Here's a new test case for t/pmc/sub.t output_is(<<'CODE', <<'OUTPUT', "set_eh - throw - clear_eh"); print "start\n" newsub P20, .Exception_Handler, _handler set_eh P20 new P30, .Exception throw P30 print "not reached\n" end _handler: clear_eh print "

Re: bug: clear_eh patricide after catch

2003-08-14 Thread Michal Wallace
On Mon, 11 Aug 2003, Leopold Toetsch wrote: > No, the exception object isn't around anymore in the handler, so you > don't C there. > > This could of course be just my wrong implementation. No, it makes sense. You wouldn't want an exception in the catch: block to trigger an infinite loop. But i