On Mon, 11 Aug 2003, Leopold Toetsch wrote: > No, the exception object isn't around anymore in the handler, so you > don't C<clear_eh> 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 if that's the way to go, there ought to be a note in the docs. (see patch below) > > I don't care if it goes away after the exception is > > caught, but I need a way to clear the exception > > handler after I get out of the try/except or > > try/finally block... Otherwise later exceptions > > will bring me backward in the code. :/ > > Can you insert C<clear_eh> before you fall through to except/finally? Yep. That works perfectly. Thanks. :) Sincerely, Michal J Wallace Sabren Enterprises, Inc. ------------------------------------- contact: [EMAIL PROTECTED] hosting: http://www.cornerhost.com/ my site: http://www.withoutane.com/ -------------------------------------- Index: core.ops =================================================================== RCS file: /cvs/public/parrot/core.ops,v retrieving revision 1.316 diff -c -r1.316 core.ops *** core.ops 8 Aug 2003 08:15:05 -0000 1.316 --- core.ops 11 Aug 2003 23:30:55 -0000 *************** *** 479,485 **** =item B<clear_eh>() ! Clear out the most recently placed exception. =item B<throw>(in PMC) --- 479,486 ---- =item B<clear_eh>() ! Clear out the most recently placed exception. This also ! happens automatically if an exception is thrown. =item B<throw>(in PMC)
