stas 2003/02/19 19:02:25
Modified: src/docs/2.0/devel/porting porting.pod
Log:
of course
use mod_perl 2.0;
should be used, before $mod_perl::VERSION can be used
Revision Changes Path
1.7 +2 -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.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- porting.pod 29 Jan 2003 05:19:31 -0000 1.6
+++ porting.pod 20 Feb 2003 03:02:25 -0000 1.7
@@ -110,13 +110,14 @@
use the appropriate code for 1.0 or 2.0. You can use it to load
C<Apache::compat> if running under mod_perl 2.0:
+ use mod_perl;
if ($mod_perl::VERSION >= 2.0) {
require Apache::compat;
}
META: while 2.0 is not released, use:
- $mod_perl::VERSION >= 1.99
+ if ($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]
