Change 16213 by ams@lustre on 2002/04/27 15:38:50
Subject: Re: Change 16122: Try to be clearer about perlio.
From: Philip Newton <[EMAIL PROTECTED]>
Date: Sat, 27 Apr 2002 08:51:30 +0200
Message-Id: <[EMAIL PROTECTED]>
Subject: Re: Change 16183: Stop being coy.
From: Philip Newton <[EMAIL PROTECTED]>
Date: Sat, 27 Apr 2002 08:52:13 +0200
Message-Id: <[EMAIL PROTECTED]>
Affected files ...
.... //depot/perl/INSTALL#101 edit
.... //depot/perl/pod/perldelta.pod#362 edit
Differences ...
==== //depot/perl/INSTALL#101 (text) ====
Index: perl/INSTALL
--- perl/INSTALL.~1~ Sat Apr 27 09:45:05 2002
+++ perl/INSTALL Sat Apr 27 09:45:05 2002
@@ -24,7 +24,7 @@
Each of these is explained in further detail below.
-B<NOTE>: starting from the release 5.6.0 Perl will use a version
+B<NOTE>: starting from the release 5.6.0, Perl will use a version
scheme where even-numbered subreleases (like 5.6) are stable
maintenance releases and odd-numbered subreleases (like 5.7) are
unstable development releases. Development releases should not be
@@ -806,23 +806,23 @@
=head2 Selecting File IO mechanisms
-Executive summary: in Perl 5.8 you should use the default "PerlIO"
+Executive summary: in Perl 5.8, you should use the default "PerlIO"
as the IO mechanism unless you have a good reason not to.
In more detail: previous versions of perl used the standard IO
mechanisms as defined in stdio.h. Versions 5.003_02 and later of perl
-introuced alternate IO mechanisms via a "PerlIO" abstraction, but up
-until and including Perl 5.6 stdio mechanism was still the default and
-the only supported mechanism.
+introduced alternate IO mechanisms via a "PerlIO" abstraction, but up
+until and including Perl 5.6, the stdio mechanism was still the default
+and the only supported mechanism.
-Starting from Perl 5.8 the default mechanism is to use the PerlIO
+Starting from Perl 5.8, the default mechanism is to use the PerlIO
abstraction, because it allows better control of I/O mechanisms,
instead of having to work with (often, work around) vendors' I/O
implementations.
-This PerlIO abstraction can be disabled (but again, unless you know
-what you are doing, should not) either on the Configure command line
-with
+This PerlIO abstraction can be (but again, unless you know what you
+are doing, should not be) disabled either on the Configure command
+line with
sh Configure -Uuseperlio
==== //depot/perl/pod/perldelta.pod#362 (text) ====
Index: perl/pod/perldelta.pod
--- perl/pod/perldelta.pod.~1~ Sat Apr 27 09:45:05 2002
+++ perl/pod/perldelta.pod Sat Apr 27 09:45:05 2002
@@ -55,11 +55,11 @@
(Pure Perl modules should continue to work.)
The major reason for the discontinity is the new IO architecture
-called PerlIO. The PerlIO is the default configuration because
+called PerlIO. PerlIO is the default configuration because
without it many new features of Perl 5.8 cannot be used. In other
words: you just have to recompile your modules, sorry about that.
-In future releases of Perl non-PerlIO aware XS modules may become
+In future releases of Perl, non-PerlIO aware XS modules may become
completely unsupported. This shouldn't be too difficult for module
authors, however: PerlIO has been designed as a drop-in replacement
(at the source code level) for the stdio interface.
End of Patch.
