# New Ticket Created by Brad Bowman # Please include the string: [perl #60364] # in the subject line of all future correspondence about this issue. # <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=60364 >
Hi, The pdd19_pir.pod is no longer a draft, this patch corrects the L<> references. -L<docs/pdds/draft/pdd19_pir.pod>. +L<docs/pdds/pdd19_pir.pod>. There's also a typo and missing "=item". I've tried to address this XXX comment, please check it's correct. =head2 How do I create nested subroutines? -Please refer to L<docs/pdds/pdd20_lexical_vars.pod> for details: look for -C<:outer>. - -XXX Fix L syntax here. +Please refer to L<pdd20_lexical_vars.pod|docs/pdds/pdd20_lexical_vars.pod/Nested Subroutines Have Outies; the ":outer" attribute> +for details. $ diffstat pod_2008-11-06.patch CREDITS | 3 +++ docs/art/pp001-intro.pod | 4 ++-- docs/compiler_faq.pod | 8 +++----- docs/faq.pod | 2 +- docs/pct/gettingstarted.pod | 2 +- docs/pmc/subs.pod | 4 ++-- docs/stm/howto.pod | 2 +- 7 files changed, 13 insertions(+), 12 deletions(-) Thanks, Brad
diff --git a/CREDITS b/CREDITS index eea9d13..b125ee7 100644 --- a/CREDITS +++ b/CREDITS @@ -129,6 +129,9 @@ N: Bob Wilkinson D: Numerous document typos. E: [EMAIL PROTECTED] +N: Brad Bowman +D: pod fixes + N: Brad Gilbert D: Add test for sysinfo op. E: [EMAIL PROTECTED] diff --git a/docs/art/pp001-intro.pod b/docs/art/pp001-intro.pod index 754a48d..781df9a 100644 --- a/docs/art/pp001-intro.pod +++ b/docs/art/pp001-intro.pod @@ -88,7 +88,7 @@ executing this subroutine. By the way, I could use C<.sub foo :main> and Parrot will use the C<foo> subroutine as the main body of the program. The actual name of the subroutine does not matter as long as it has the C<:main> pragma. The full set of pragmas are defined in -L<docs/pdds/draft/pdd19_pir.pod>. +L<docs/pdds/pdd19_pir.pod>. Before going into more details about subroutines and calling conventions, let's compare some PIR syntax to the equivalent PASM. @@ -297,7 +297,7 @@ Alberto Simões =over 4 -* Jonathan Scott Duff +=item * Jonathan Scott Duff =back diff --git a/docs/compiler_faq.pod b/docs/compiler_faq.pod index 299a271..a55f641 100644 --- a/docs/compiler_faq.pod +++ b/docs/compiler_faq.pod @@ -50,7 +50,7 @@ If the function name might collide with a Parrot opcode, quote it: i = 'new'(42) You can also use the full PCC for these calls. See -L<docs/draft/pdd19_pir.pod/Parameter Passing and Getting Flags> and other +L<docs/pdd19_pir.pod/Parameter Passing and Getting Flags> and other quesitons below for more information. =head2 How do I generate a method call in PIR? @@ -179,10 +179,8 @@ Use the C<:optional> and C<:opt_flag> pragmas: =head2 How do I create nested subroutines? -Please refer to L<docs/pdds/pdd20_lexical_vars.pod> for details: look for -C<:outer>. - -XXX Fix L syntax here. +Please refer to L<pdd20_lexical_vars.pod|docs/pdds/pdd20_lexical_vars.pod/Nested Subroutines Have Outies; the ":outer" attribute> +for details. =head1 Variables diff --git a/docs/faq.pod b/docs/faq.pod index 5f725e7..3562d21 100644 --- a/docs/faq.pod +++ b/docs/faq.pod @@ -33,7 +33,7 @@ Yes. Although Parrot is currently still under development, Parrot has been usable for a long time. The primary way to use Parrot is to write Parrot Intermediate -Representation (PIR), described in L<PDD19|docs/pdds/draft/pdd19_pir.pod>. +Representation (PIR), described in L<PDD19|docs/pdds/pdd19_pir.pod>. PIR is a high-level assembly language. See the L<examples> directory. =head2 When can I expect to use Parrot with a I<real> programming language? diff --git a/docs/pct/gettingstarted.pod b/docs/pct/gettingstarted.pod index f8da103..3a51fb9 100644 --- a/docs/pct/gettingstarted.pod +++ b/docs/pct/gettingstarted.pod @@ -203,7 +203,7 @@ implementation of a simple yet non-trivial language. =item * L<docs/pdds/pdd26_past.pod> -=item * L<docs/pdds/draft/pdd19_pir.pod> +=item * L<docs/pdds/pdd19_pir.pod> =item * F<http://dev.perl.org/perl6/doc/design/syn/S05.html> diff --git a/docs/pmc/subs.pod b/docs/pmc/subs.pod index ba7d351..b4a2717 100644 --- a/docs/pmc/subs.pod +++ b/docs/pmc/subs.pod @@ -132,7 +132,7 @@ subs, B<:init> subs are also run when compiling from memory. B<:load> subs are run only in any source or bytecode files loaded subsequently. These markers are called "pragmas", and are defined fully in -L<docs/pdds/draft/pdd19_pir.pod>. The following table summarizes the behavior +L<docs/pdds/pdd19_pir.pod>. The following table summarizes the behavior of the five pragmas that cause Parrot to run a sub implicitly: ------ Executed when -------- @@ -309,7 +309,7 @@ F<t/pmc/sub.t> =head1 SEE ALSO F<docs/pdds/pdd03_calling_conventions.pod> -F<docs/pdds/draft/pdd19_pir.pod> +F<docs/pdds/pdd19_pir.pod> =head1 AUTHOR diff --git a/docs/stm/howto.pod b/docs/stm/howto.pod index beb6681..d15c223 100644 --- a/docs/stm/howto.pod +++ b/docs/stm/howto.pod @@ -93,7 +93,7 @@ STMLog PMC type. =head2 Starting and ending transactions The runtime library C<transaction> runs a supplied subroutine (with -optional supplied arugments) in a separate transaction commiting the +optional supplied arguments) in a separate transaction commiting the result. For example, (Perlish) pseudocode for inserting at the beginning of a linked list might look like this: