X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=README.os2;h=8cc0ec7d406194945ea34c0d1350345aa69c500e;hb=47c8db80932508b6333745f2c283d5a98bf9cccb;hp=69fa3866a4ae2e35222960fdf7b4fbab9f9428ba;hpb=d88df687829d8e1fb1928d0da0f560eb2e46996d;p=p5sagit%2Fp5-mst-13.2.git diff --git a/README.os2 b/README.os2 index 69fa386..8cc0ec7 100644 --- a/README.os2 +++ b/README.os2 @@ -262,7 +262,7 @@ same way as on any other platform, by perl foo.pl arg1 arg2 arg3 If you want to specify perl options C<-my_opts> to the perl itself (as -opposed to to your program), use +opposed to your program), use perl -my_opts foo.pl arg1 arg2 arg3 @@ -386,7 +386,7 @@ there is an executable file F I on C. 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 as as simple as that: since F and F denote the +The workaround is as simple as that: since F and F denote the same file, to start an executable residing in file F (no extension) give an argument C (dot appended) to system(). @@ -733,7 +733,7 @@ Users of Emacs would appreciate it very much, especially with C mode loaded. You need to get latest C from C, or, alternately, prebuilt info pages. -=head2 F<.PDF> files +=head2 F files for C are available on CPAN (for slightly old version of perl). @@ -829,8 +829,8 @@ link386 prompts, press C to exit. You need to fetch the latest perl source (including developers releases). With some probability it is located in - http://www.perl.com/CPAN/src/5.0 - http://www.perl.com/CPAN/src/5.0/unsupported + http://www.cpan.org/src/5.0 + http://www.cpan.org/src/5.0/unsupported If not, you may need to dig in the indices to find it in the directory of the current maintainer. @@ -838,7 +838,7 @@ of the current maintainer. Quick cycle of developers release may break the OS/2 build time to time, looking into - http://www.perl.com/CPAN/ports/os2/ilyaz/ + http://www.cpan.org/ports/os2/ilyaz/ may indicate the latest release which was publicly released by the maintainer. Note that the release may include some additional patches @@ -1185,7 +1185,7 @@ C. Returns C if it was not called yet, otherwise bit 1 is set if on the previous call do_harderror was enabled, bit -2 is set if if on previous call do_exception was enabled. +2 is set if on previous call do_exception was enabled. This function enables/disables error popups associated with hardware errors (Disk not ready etc.) and software exceptions. @@ -1639,7 +1639,7 @@ of the F<.EXE> file are loaded is decided at compile-time, thus all the processes have these sections loaded at same addresses, and no fixup of internal links inside the F<.EXE> is needed. -Since DLLs may be loaded at run time, to have the same mechanism for for DLLs +Since DLLs may be loaded at run time, to have the same mechanism for DLLs one needs to have the address range of I DLLs in the system to be available I which did not load a particular DLL yet. This is why the DLLs are mapped to the shared memory region. @@ -1790,7 +1790,7 @@ F to the "new" F. =back -=head2 DLL name mangling: 5.6.2 and beyound +=head2 DLL name mangling: 5.6.2 and beyond In fact mangling of I DLLs was done due to misunderstanding of the OS/2 dynaloading model. OS/2 (effectively) maintains two @@ -1847,7 +1847,7 @@ same as for Perl 5.005_53 (same as in a popular binary release). Thus new Perls will be able to I of old extension DLLs if @INC allows finding their directories. -However, this still does not guarantie that these DLL may be loaded. +However, this still does not guarantee that these DLL may be loaded. The reason is the mangling of the name of the I. And since the extension DLLs link with the Perl DLL, extension DLLs for older versions would load an older Perl DLL, and would most probably @@ -1872,7 +1872,7 @@ Old perl executable is started when a new executable is running has loaded an extension compiled for the old executable (ouph!). In this case the old executable will get a forwarder DLL instead of the old perl DLL, so would link with the new perl DLL. While not directly -fatal, it will behave the same as new excutable. This beats the whole +fatal, it will behave the same as new executable. This beats the whole purpose of explicitly starting an old executable. =item *