diff options
| -rw-r--r-- | README.os2 | 5 | ||||
| -rw-r--r-- | t/porting/known_pod_issues.dat | 6 |
2 files changed, 5 insertions, 6 deletions
diff --git a/README.os2 b/README.os2 index 359fc844ab..0425292771 100644 --- a/README.os2 +++ b/README.os2 @@ -196,7 +196,7 @@ Cf. L</Prerequisites>. EMX runtime is required (may be substituted by RSX). Note that it is possible to make F<perl_.exe> to run under DOS without any -external support by binding F<emx.exe>/F<rsx.exe> to it, see L<emxbind>. Note +external support by binding F<emx.exe>/F<rsx.exe> to it, see C<emxbind>. Note that under DOS for best results one should use RSX runtime, which has much more functions working (like C<fork>, C<popen> and so on). In fact RSX is required if there is no VCPI present. Note the @@ -1111,7 +1111,7 @@ named accordingly. Fully build and test the Perl distribution. Make sure that no tests are failing with C<test> and C<aout_test> targets; fix the bugs in Perl and the Perl test suite detected by these tests. Make sure that C<all_test> -make target runs as clean as possible. Check that C<os2/perlrexx.cmd> +make target runs as clean as possible. Check that F<os2/perlrexx.cmd> runs fine. =item 2. @@ -2218,7 +2218,6 @@ It is a VIO application. Since Perl processes the C<#!>-line (cf. L<perlrun/DESCRIPTION>, L<perlrun/Command Switches>, -L<perldiag/"Not a perl script">, L<perldiag/"No Perl script found in input">), it should know when a program I<is a Perl>. There is some naming convention which allows Perl to distinguish correct lines from wrong ones. The above names are diff --git a/t/porting/known_pod_issues.dat b/t/porting/known_pod_issues.dat index 12c7be51fa..af25387944 100644 --- a/t/porting/known_pod_issues.dat +++ b/t/porting/known_pod_issues.dat @@ -82,6 +82,7 @@ perllexwarn(1) perlthanks POD2::FR POD2::IT +pod2ipf(1) pod2man(1) Pod::HTML2Pod Pod::Plainer @@ -103,6 +104,7 @@ Shell Shell::Command sock_init(3) socketpair(3) +SOM splain sprintf(3) stat(2) @@ -262,9 +264,7 @@ pod/perlmroapi.pod ? Should you be using L<...> instead of 1 pod/perlnetware.pod Verbatim line length including indents exceeds 80 by 4 pod/perlnewmod.pod Verbatim line length including indents exceeds 80 by 1 pod/perlop.pod Verbatim line length including indents exceeds 80 by 30 -pod/perlos2.pod ? Should you be using F<...> or maybe L<...> instead of 1 -pod/perlos2.pod ? Should you be using L<...> instead of 1 -pod/perlos2.pod Apparent broken link 4 +pod/perlos2.pod ? Should you be using L<...> instead of 2 pod/perlos2.pod Verbatim line length including indents exceeds 80 by 22 pod/perlos390.pod Verbatim line length including indents exceeds 80 by 11 pod/perlpacktut.pod Verbatim line length including indents exceeds 80 by 6 |