perldelta: quadmath

[perl5.git] / README.os2

diff --git a/README.os2 b/README.os2
index 359fc84..ae03a56 100644 (file)
--- 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
@@ -404,11 +404,12 @@ there is an executable file F<blah.exe> I<anywhere> on C<PATH>.  In
 other words, C<PATH> is essentially searched twice: once by the OS for
 an executable, then by Perl for scripts.
 
-Note also that executable files on OS/2 can have an arbitrary extension, 
-but F<.exe> will be automatically appended if no dot is present in the name.  
-The workaround is as simple as that:  since F<blah.> and F<blah> denote the 
-same file (at list on FAT and HPFS file systems), to start an executable residing in file F<n:/bin/blah> (no 
-extension) give an argument C<n:/bin/blah.> (dot appended) to system().
+Note also that executable files on OS/2 can have an arbitrary extension, but
+F<.exe> will be automatically appended if no dot is present in the name.  The
+workaround is as simple as that:  since F<blah.> and F<blah> denote the same
+file (at list on FAT and HPFS file systems), to start an executable residing in
+file F<n:/bin/blah> (no extension) give an argument C<n:/bin/blah.> (dot
+appended) to system().
 
 Perl will start PM programs from VIO (=text-mode) Perl process in a
 separate PM session;
@@ -618,7 +619,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.21.4/
 
 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
@@ -1015,12 +1016,12 @@ The reasons for most important skipped tests are:
 
 =over 4
 
-=item 18
+=item Z<>18
 
 Checks C<atime> and C<mtime> of C<stat()> - unfortunately, HPFS
 provides only 2sec time granularity (for compatibility with FAT?).
 
-=item 25
+=item Z<>25
 
 Checks C<truncate()> on a filehandle just opened for write - I do not
 know why this should or should not work.
@@ -1111,7 +1112,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.
@@ -1409,7 +1410,8 @@ For best results compile the C file below with the same options as the Perl
 DLL.  However, a lot of functionality will work even if the executable is not
 an EMX applications, e.g., if compiled with
 
-  gcc -Wall -DDOSISH -DOS2=1 -O2 -s -Zomf -Zsys perl-starter.c -DPERL_DLL_BASENAME=\"perl312F\" -Zstack 8192 -Zlinker /PM:VIO
+  gcc -Wall -DDOSISH -DOS2=1 -O2 -s -Zomf -Zsys perl-starter.c \
+    -DPERL_DLL_BASENAME=\"perl312F\" -Zstack 8192 -Zlinker /PM:VIO
 
 Here is the sample C file:
 
@@ -1461,7 +1463,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--;
@@ -2218,7 +2220,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