Author: allison Date: Tue May 6 12:07:13 2008 New Revision: 27353 Modified: branches/pdd25cx/docs/pdds/pdd23_exceptions.pod
Log: [exceptions] Merging 'throw' and 'throwcc', the one-argument versions were identical anyway. Modified: branches/pdd25cx/docs/pdds/pdd23_exceptions.pod ============================================================================== --- branches/pdd25cx/docs/pdds/pdd23_exceptions.pod (original) +++ branches/pdd25cx/docs/pdds/pdd23_exceptions.pod Tue May 6 12:07:13 2008 @@ -72,9 +72,13 @@ Throw an exception consisting of the given I<EXCEPTION> PMC. Active exception handlers (if any) will be invoked with I<EXCEPTION> as the only parameter. -Throwing an exception with C<throw> is a one-way trip (unless you have made -other arrangements) because Parrot does not take a continuation after this -opcode. (But see B<throwcc> below.) + +=item B<throw I<EXCEPTION> [ , I<CONTINUATION> ]> + +Throw an exception consisting of the given I<EXCEPTION> PMC after taking +a continuation at the next opcode. When a I<CONTINUATION> is passed in, +it will use that instead. Active exception handlers (if any) will be +invoked with I<EXCEPTION> and the given continuation as parameters. Any type of PMC can be thrown as an exception. However, if there's any chance of cross-language calls -- and in a Parrot environment, cross-language @@ -85,17 +89,6 @@ possibly escape your private sandbox should meet the minimal interface requirements of the C<parrot;exception> class, described below. -=item B<throwcc I<EXCEPTION> [ , I<CONTINUATION> ]> - -Throw an exception consisting of the given I<EXCEPTION> PMC after taking -a continuation at the next opcode. When a I<CONTINUATION> is passed in, -it will use that instead. Active exception handlers (if any) will be -invoked with I<EXCEPTION> and the given continuation as parameters. - -Except for the continuation which is passed to exception handlers, -C<throwcc> is just like C<throw>. This opcode is useful for exceptions -that are more like warnings or notices than errors. - Exception handlers can resume execution immediately after the C<throwcc> opcode by executing the C<handled> opcode, and then invoking the given continuation which they receive as a parameter. That continuation must be
