summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRicardo Signes <rjbs@cpan.org>2013-05-14 21:29:16 -0400
committerRicardo Signes <rjbs@cpan.org>2013-05-14 21:29:16 -0400
commitf3068e1b8162c9d1fc179c4642cb0af8c9f5d065 (patch)
treea0fa1e2a4afd414c3a5f4722866b0863410fc5bb
parent55c6e7a8d6cf0b496596c66f110d3984a2b500c3 (diff)
downloadperl-f3068e1b8162c9d1fc179c4642cb0af8c9f5d065.tar.gz
perldelta: clarify the deprecation of non-PerlIO perl
-rw-r--r--pod/perldelta.pod14
1 files changed, 8 insertions, 6 deletions
diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index da7144ab7f..1901627fce 100644
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -714,12 +714,14 @@ constructs.
=head2 Pre-PerlIO IO implementations
-Perl supports being built without PerlIO proper, using a stdio or sfio
-wrapper instead. A perl build like this will not support IO layers and
-thus Unicode IO, making it rather handicapped.
-
-PerlIO supports a C<stdio> layer if stdio use is desired, and similarly a
-sfio layer could be produced.
+In theory, you can currently build perl without PerlIO. Instead, you'd use a
+wrapper around stdio or sfio. In practice, this isn't very useful. It's not
+well tested, and without any support for IO layers or (thus) Unicode, it's not
+much of a perl. Building without PerlIO will most likely be removed in the
+next version of perl.
+
+PerlIO supports a C<stdio> layer if stdio use is desired. Similarly a
+sfio layer could be produced in the future, if needed.
=head1 Future Deprecations