stas 2002/06/19 12:29:49
Modified: src/docs/2.0/user/coding coding.pod
src/docs/2.0/user/config config.pod
Log:
markup fixes
Revision Changes Path
1.11 +1 -1 modperl-docs/src/docs/2.0/user/coding/coding.pod
Index: coding.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/coding/coding.pod,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- coding.pod 19 Jun 2002 19:21:45 -0000 1.10
+++ coding.pod 19 Jun 2002 19:29:49 -0000 1.11
@@ -89,7 +89,7 @@
use strict;
use warnings FATAL => 'all';
-C<FATAL => 'all'> escalate all warnings into fatal errors. So when
+C<FATAL =E<gt> 'all'> escalate all warnings into fatal errors. So when
C<Apache::Whatever> is modified and reloaded by C<Apache::Reload> the
request is aborted. Therefore if you follow this very healthy style
and want to use C<Apache::Reload>, flex the strictness by changing it
1.18 +1 -1 modperl-docs/src/docs/2.0/user/config/config.pod
Index: config.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/config/config.pod,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- config.pod 19 Jun 2002 19:25:02 -0000 1.17
+++ config.pod 19 Jun 2002 19:29:49 -0000 1.18
@@ -213,7 +213,7 @@
$r->dir_config('VarTest');
Alternatively use the Apache core directives C<SetEnv> and C<PassEnv>,
-which always populate C<r->suprocess_env>, but this doesn't happen
+which always populate C<r-E<gt>suprocess_env>, but this doesn't happen
until the Apache fixup phase, which could be too late for your needs.
=head2 perl-script
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
