Change 16183 by jhi@alpha on 2002/04/26 11:57:58
Stop being coy.
Affected files ...
.... //depot/perl/pod/perldelta.pod#360 edit
Differences ...
==== //depot/perl/pod/perldelta.pod#360 (text) ====
Index: perl/pod/perldelta.pod
--- perl/pod/perldelta.pod.~1~ Fri Apr 26 06:15:05 2002
+++ perl/pod/perldelta.pod Fri Apr 26 06:15:05 2002
@@ -48,19 +48,25 @@
=head2 Binary Incompatibility
-Perl 5.8 has not been designed to be binary compatible with earlier
-releases of Perl. While the compatibility has not been intentionally
-broken, it has not been intentionally protected, either. The major
-reason for the discontinity is the new IO architecture called PerlIO.
-The 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.
+B<Perl 5.8 is not binary compatible with earlier releases of Perl.>
+
+B<You have to recompile your XS modules.>
+
+(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
+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
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.
+Depending on your platform, there are also other reasons why
+we decided to break binary compatibility, please read on.
+
=head2 64-bit platforms and malloc
If your pointers are 64 bits wide, the Perl malloc is no longer being
End of Patch.
