stas 2002/06/19 12:21:45 Modified: src/docs/2.0/user/coding coding.pod Log: notes regarding the fatal warnings and Apache::Reload Revision Changes Path 1.10 +35 -0 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.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- coding.pod 5 Jun 2002 17:34:26 -0000 1.9 +++ coding.pod 19 Jun 2002 19:21:45 -0000 1.10 @@ -69,6 +69,41 @@ MPM, otherwise it prints the process id. +=head1 Developing Modules + +=head1 Apache::Reload + +META: need to port Apache::Reload notes from the guide here. but the +gist is: + + PerlModule Apache::Reload + PerlInitHandler Apache::Reload + PerlSetVar ReloadAll Off + PerlSetVar ReloadModules "ModPerl::* Apache::*" + +Though notice that we have started to practice the following style in +our modules: + + package Apache::Whatever; + + use strict; + use warnings FATAL => 'all'; + +C<FATAL => '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 +to: + + use warnings FATAL => 'all'; + no warnings 'redefine'; + +but if you still want the I<redefine> warnings, but so they won't be +fatal: + + use warnings FATAL => 'all'; + no warnings 'redefine'; + use warnings 'redefine'; =head1 Perl Specifics in mod_perl Environment
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
