The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.

NAME

Coding with and for mod_perl

Description

This chapter covers the mod_perl coding specifics, different from normal Perl coding.

Prerequisites

Installing from Source

Installing from Binary Packages

Perl Specifics in mod_perl Environment

In the following sections we discuss the specifics of Perl behavior under mod_perl.

exit()

In the normal Perl code exit() is used to stop the program flow and exit the Perl interpreter. However under mod_perl we only want the stop the program flow without killing the Perl interpreter.

You should take no action if your code includes exit() calls and it's OK to continue using them. mod_perl worries to override the exit() function with its own version which stops the program flow, and performs all the necessary cleanups, but doesn't kill the server. This is done by overriding:

  *CORE::GLOBAL::exit = \&ModPerl::Util::exit;

so if you mess up with *CORE::GLOBAL::exit yourself you better know what you are doing.

You can still call CORE::exit to kill the interpreter, again if you know what you are doing.

Maintainers

Maintainer is the person(s) you should contact with updates, corrections and patches.

Authors

Only the major authors are listed above. For contributors see the Changes file.