cvsuser 03/07/02 14:36:42
Modified: docs/pmc subs.pod
Log:
Fix a couple of typos, minor rewording
Revision Changes Path
1.2 +8 -8 parrot/docs/pmc/subs.pod
Index: subs.pod
===================================================================
RCS file: /cvs/public/parrot/docs/pmc/subs.pod,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -w -r1.1 -r1.2
--- subs.pod 30 Jun 2003 09:08:38 -0000 1.1
+++ subs.pod 2 Jul 2003 21:36:42 -0000 1.2
@@ -55,8 +55,8 @@
=head2 All together now
-The following scheme can be uesd, if a subroutine is called once or
-performance doesn't matter:
+The following scheme can be used if a subroutine is called once or
+if performance doesn't matter:
newsub P0, .Sub, _sub_label # create subroutine
set I5, 42 # pass an argument
@@ -66,9 +66,9 @@
print I5 # do something with parameters
invoke P1 # return
-If a subroutine is called several times e.g. inside a loop, the creation of
-the return continuation shall be done outside the loop, if performance
-is an issue:
+If a subroutine is called several times, for instance inside a loop,
+the creation of the return continuation can be done outside the loop if
+performance is an issue:
newsub .Sub, .Continuation, _sub_label, ret_label
set I16, 1000000
@@ -85,9 +85,9 @@
# do_something
invoke P1
-If items in the interpreter context are changed between creation of
-subroutine/return continuation and invocation, the C<updatecc> opcode
-should be used.
+If items in the interpreter context are changed between creation of the
+subroutine/return continuation and its invocation, the C<updatecc> opcode
+should be used:
newsub .Sub, .Continuation, _sub_label, ret_label
...
