Mailing-List: contact docs-cvs-help@perl.apache.org; run by ezmlm
Precedence: bulk
Date: 10 Oct 2001 05:23:53 -0000
Message-ID: <20011010052353.73925.qmail@icarus.apache.org>
From: stas@apache.org
To: modperl-docs-cvs@apache.org
Subject: cvs commit: modperl-docs/src/user/coding coding.pod

stas        01/10/09 22:23:53

  Added:       src/user/coding coding.pod
  Log:
  - starting "Coding with and for mod_perl" chapter
  - documenting exit()'s behavior
  
  Revision  Changes    Path
  1.1                  modperl-docs/src/user/coding/coding.pod
  
  Index: coding.pod
  ===================================================================
  =head1 Coding with and for mod_perl
  
  =head1 Prerequisites
  
  =head1 Installing from Source
  
  =head1 Installing from Binary Packages
  
  =head1 Perl Specifics in mod_perl Environment
  
  In the following sections we discuss the specifics of Perl behavior
  under mod_perl.
  
  =head2 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: C<*CORE::GLOBAL::exit>, so if you mess up with
  C<*CORE::GLOBAL::exit> yourself you better know what you are doing.
  
  You can still call C<CORE::exit> to kill the interpreter, again if you
  know what you are doing.
  
  =head1 Maintainers
  
  Maintainer is the person(s) you should contact with updates,
  corrections and patches.
  
  =head1 Authors
  
  
  =cut
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-cvs-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-cvs-help@perl.apache.org