Documentation of non-handle IO::Handle methods in perlvar.pod

[perl5.git] / README.os2

diff --git a/README.os2 b/README.os2
index e32d9af..c2a8794 100644 (file)
--- a/README.os2
+++ b/README.os2
@@ -162,7 +162,7 @@ Using F<perl__.exe> avoids such a degradation.
 =item *
 
 There is no simple way to access WPS objects. The only way I know
-is via C<OS2::REXX> and C<SOM> extensions (see L<OS2::REXX>, L<Som>).
+is via C<OS2::REXX> and C<SOM> extensions (see L<OS2::REXX>, L<SOM>).
 However, we do not have access to
 convenience methods of Object-REXX. (Is it possible at all? I know
 of no Object-REXX API.)  The C<SOM> extension (currently in alpha-text)
@@ -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
@@ -264,7 +264,7 @@ either in the wired-in-during-compile locations (usually F<F:/bin>),
 or in configurable location (see L<"PERL_SH_DIR">).
 
 For best results use EMX pdksh. The standard binary (5.2.14 or later) runs
-under DOS (with L<RSX>) as well, see
+under DOS (with L</RSX>) as well, see
 
   http://www.ilyaz.org/software/os2/
 
@@ -315,7 +315,7 @@ or whatever method you prefer.
 There are also endless possibilities to use I<executable extensions> of
 4os2, I<associations> of WPS and so on... However, if you use
 *nixish shell (like F<sh.exe> supplied in the binary distribution),
-you need to follow the syntax specified in L<perlrun/"Switches">.
+you need to follow the syntax specified in L<perlrun/"Command Switches">.
 
 Note that B<-S> switch supports scripts with additional extensions 
 F<.cmd>, F<.btm>, F<.bat>, F<.pl> as well.
@@ -435,7 +435,7 @@ managed to goof.  C<;-)>
 =item *
 
 Did you run your programs with C<-w> switch? See 
-L<Starting OS/2 (and DOS) programs under Perl>.
+L<Starting OSE<sol>2 (and DOS) programs under Perl>.
 
 =item *
 
@@ -557,7 +557,7 @@ of this file.
 
 B<NOTE>. Because of a typo the binary installer of 5.00305
 would install a variable C<PERL_SHPATH> into F<Config.sys>. Please
-remove this variable and put C<L<PERL_SH_DIR>> instead.
+remove this variable and put C<L</PERL_SH_DIR>> instead.
 
 =head2 Manual binary installation
 
@@ -618,7 +618,7 @@ C<set PERLLIB_PREFIX> in F<Config.sys>, see L<"PERLLIB_PREFIX">.
 
 =item Additional Perl modules
 
-  unzip perl_ste.zip -d f:/perllib/lib/site_perl/5.15.0/
+  unzip perl_ste.zip -d f:/perllib/lib/site_perl/5.17.6/
 
 Same remark as above applies.  Additionally, if this directory is not
 one of directories on @INC (and @INC is influenced by C<PERLLIB_PREFIX>), you
@@ -1061,7 +1061,7 @@ Run
 to convert perl utilities to F<.cmd> files and put them on
 PATH. You need to put F<.EXE>-utilities on path manually. They are
 installed in C<$prefix/bin>, here C<$prefix> is what you gave to
-F<Configure>, see L<Making>.
+F<Configure>, see L</Making>.
 
 If you use C<man>, either move the installed F<*/man/> directories to
 your C<MANPATH>, or modify C<MANPATH> to match the location.  (One
@@ -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.
@@ -1264,7 +1264,7 @@ redirect the new version of Perl to a new location, and copy the installed
 files to this new location.  Redo the tests to make sure that the versions of
 modules inherited from older versions of Perl are not needed.
 
-Actually, the log output of L<pod2ipf> during the step 6 gives a very detailed
+Actually, the log output of L<pod2ipf(1)> during the step 6 gives a very detailed
 info about which modules are loaded from which place; so you may use it as
 an additional verification tool.
 
@@ -1461,7 +1461,7 @@ Here is the sample C file:
 
       if (_execname(buf, sizeof(buf) - 13) != 0)
           die_with("Can't find full path: ", strerror(errno), "", "");
-      /* XXXX Fill `me' with new value */
+      /* XXXX Fill 'me' with new value */
       l = strlen(buf);
       while (l && buf[l-1] != '/' && buf[l-1] != '\\')
           l--;
@@ -2217,8 +2217,7 @@ It is a VIO application.
 =head2 Why strange names?
 
 Since Perl processes the C<#!>-line (cf. 
-L<perlrun/DESCRIPTION>, L<perlrun/Switches>,
-L<perldiag/"Not a perl script">, 
+L<perlrun/DESCRIPTION>, L<perlrun/Command Switches>,
 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
@@ -2638,7 +2637,7 @@ I will include it into distribution. I have no need for such a module, so
 cannot test it.
 
 For the details of the current situation with calling external programs,
-see L<Starting OS/2 (and DOS) programs under Perl>.  Set us mention a couple
+see L<Starting OSE<sol>2 (and DOS) programs under Perl>.  Set us mention a couple
 of features:
 
 =over 4
@@ -2700,7 +2699,7 @@ have a low probability of affecting small programs.
 =head1 BUGS
 
 This description is not updated often (since 5.6.1?), see F<./os2/Changes>
-(L<perlos2delta>) for more info.
+for more info.
 
 =cut