stas 2002/12/03 18:41:53
Modified: src/docs/2.0/user/compat compat.pod
src/docs/2.0/devel/porting porting.pod
Log:
- xref the compatibility docs
- document the Apache::SIG stub
- add a ref to an anonymous tempfile feature of perl 5.8.0
Revision Changes Path
1.32 +20 -7 modperl-docs/src/docs/2.0/user/compat/compat.pod
Index: compat.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/compat/compat.pod,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- compat.pod 29 Nov 2002 04:15:17 -0000 1.31
+++ compat.pod 4 Dec 2002 02:41:53 -0000 1.32
@@ -23,6 +23,9 @@
cannot find any more or which behave differently now under the package
names the functions belong in mod_perl 1.0.
+See also L<additional porting
+notes|docs::2.0::devel::porting::porting>, mainly oriented for the 3rd
+party module and core developers.
=head1 Configuration Files Porting
@@ -82,8 +85,6 @@
-
-
=head1 Code Porting
mod_perl 2.0 is trying hard to be back compatible with mod_perl
@@ -559,15 +560,22 @@
=head2 C<open()> and C<close()>
-See the implementation in the module C<Apache::compat>.
+The methods C<open()> and C<close()> were removed. See the back
+compatibility implementation in the module C<Apache::compat>.
=head2 C<tmpfile()>
-See C<File::Temp>, or the implementation in the module
-C<Apache::compat>.
+The method C<tmpfile()> was removed since Apache 2.0 doesn't have the
+API for this method anymore.
+
+See C<File::Temp>, or the back compatibility implementation in the
+module C<Apache::compat>.
+
+With Perl v5.8.0 you can create anonymous temporary files:
-It was removed since Apache 2.0 doesn't have the API for this method
-anymore.
+ open $fh, "+>", undef or die $!;
+
+That is a literal C<undef>, not an undefined value.
=head2 C<mtime()>
@@ -741,7 +749,10 @@
+=head1 C<Apache::SIG>
+C<Apache::SIG> currently exists only C<Apache::compat> and it does
+nothing.
@@ -759,6 +770,8 @@
However C<Apache::Reload> provides an extra functionality, covered in
the module's manpage.
+
+
=head1 Maintainers
1.3 +9 -1 modperl-docs/src/docs/2.0/devel/porting/porting.pod
Index: porting.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/devel/porting/porting.pod,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- porting.pod 13 Nov 2002 15:43:34 -0000 1.2
+++ porting.pod 4 Dec 2002 02:41:53 -0000 1.3
@@ -9,6 +9,9 @@
2.0 while still preserving 1.0 compatibility. This document attempts
to answer some of the questions related to this issue.
+API changes are listed in L<the back compatibility
+document|docs::2.0::user::compat::compat/>.
+
=head1 Should the Module Name Be Changed?
While you can change the name of the module, it's the best to try to
@@ -91,7 +94,8 @@
use Apache::compat();
-in the code or I<startup.pl>.
+in the code or I<startup.pl>. The API changes are documented in L<the
+back compatibility document|docs::2.0::user::compat::compat/>.
The variable C<$mod_perl::VERSION> should be used in conditionals to
use the appropriate code for 1.0 or 2.0. You can use it to load
@@ -100,6 +104,10 @@
if ($mod_perl::VERSION >= 2.0) {
require Apache::compat;
}
+
+META: while 2.0 is not released, use:
+
+ $mod_perl::VERSION >= 1.99
XS modules will need I<Makefile.PL>/C<#ifdef> logic to work with both
versions. But the applications that use them should not need to know
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
