Author: allison Date: Wed Apr 5 15:24:24 2006 New Revision: 12125 Modified: trunk/docs/pdds/clip/pddXX_exceptions.pod trunk/docs/pdds/clip/pddXX_io.pod
Changes in other areas also in this revision: Modified: trunk/ (props changed) Log: A few PDD tweaks. Modified: trunk/docs/pdds/clip/pddXX_exceptions.pod ============================================================================== --- trunk/docs/pdds/clip/pddXX_exceptions.pod (original) +++ trunk/docs/pdds/clip/pddXX_exceptions.pod Wed Apr 5 15:24:24 2006 @@ -18,7 +18,7 @@ An exception system gives user-developed code control over how run-time error conditions are handled. Exceptions are errors or unusual -conditions that requires special processing. An exception handler +conditions that require special processing. An exception handler performs the necessary steps to appropriately respond to a particular kind of exception. @@ -33,7 +33,7 @@ C<push_eh> creates an exception handler and pushes it onto the control stack. It takes a label (the location of the exception handler) as its only argument. [Is this right? Treating exception handlers as label -jumps rather than full subroutines seems error-prone.] +jumps rather than full subroutines is error-prone.] =item * @@ -178,7 +178,7 @@ [I'm not convinced the control stack is the right way to handle exceptions. Most of Parrot is based on the continuation-passing style of -control, shouldn't exceptions be based on it too?] +control, shouldn't exceptions be based on it too? See bug #38850.] =head2 Opcodes that Throw Exceptions Modified: trunk/docs/pdds/clip/pddXX_io.pod ============================================================================== --- trunk/docs/pdds/clip/pddXX_io.pod (original) +++ trunk/docs/pdds/clip/pddXX_io.pod Wed Apr 5 15:24:24 2006 @@ -1,4 +1,4 @@ -# Copyright: 2001-2006 The Perl Foundation. All Rights Reserved. +# Copyright: 2001-2006 The Perl Foundation. # $Id $ =head1 NAME