From: Philip Newton Date: Sat, 27 Apr 2002 08:51:30 +0000 (+0200) Subject: Subject: Re: Change 16122: Try to be clearer about perlio. X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=365d6a78c0c0d9ae8eb550ee59400df4508f8b71;p=p5sagit%2Fp5-mst-13.2.git Subject: Re: Change 16122: Try to be clearer about perlio. Date: Sat, 27 Apr 2002 08:51:30 +0200 Message-Id: Subject: Re: Change 16183: Stop being coy. From: Philip Newton Date: Sat, 27 Apr 2002 08:52:13 +0200 Message-Id: p4raw-link: @4 on //depot/thrperl: 11343788cbaaede18e3146b5219d2fbdaeaf516e p4raw-id: //depot/perl@16213 --- diff --git a/INSTALL b/INSTALL index da0c726..836f152 100644 --- a/INSTALL +++ b/INSTALL @@ -24,7 +24,7 @@ with all the defaults are: Each of these is explained in further detail below. -B: starting from the release 5.6.0 Perl will use a version +B: 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 @@ and the long double support. =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 diff --git a/pod/perldelta.pod b/pod/perldelta.pod index 0ebd999..74a7b48 100644 --- a/pod/perldelta.pod +++ b/pod/perldelta.pod @@ -55,11 +55,11 @@ B (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.