stas 2003/08/08 14:00:31 Modified: src/docs/2.0/user/porting porting.pod Log: L<> fix Revision Changes Path 1.11 +3 -3 modperl-docs/src/docs/2.0/user/porting/porting.pod Index: porting.pod =================================================================== RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/porting/porting.pod,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- porting.pod 25 Jul 2003 09:27:10 -0000 1.10 +++ porting.pod 8 Aug 2003 21:00:31 -0000 1.11 @@ -939,7 +939,7 @@ backward compatibility document|docs::2.0::user::porting::compat>. But the first issue can be easily worked out using -C<L<ModPerl::MethodLookup|docs::2.0::user::api::ModPerl::MethodLookup>>. +C<L<ModPerl::MethodLookup|docs::2.0::api::ModPerl::MethodLookup>>. As explained in the section L<Using C<ModPerl::MethodLookup> Programmatically|/Using_C_ModPerl__MethodLookup__Programmatically> I've added the @@ -1022,8 +1022,8 @@ now has to be C<Apache::OK>, mainly because in mod_perl 2.0 there is an enormous amount of constants (coming from Apache and APR) and most of them are grouped in C<Apache::> or C<APR::> namespaces. The -C<L<Apache::Const|docs::2.0::user::api::Apache::Const>> and -C<L<APR::Const|docs::2.0::user::api::APR::Const>> manpage provide more +C<L<Apache::Const|docs::2.0::api::Apache::Const>> and +C<L<APR::Const|docs::2.0::api::APR::Const>> manpage provide more information on available constants. This search and replace accomplished the job:
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
