Hi Jim,
The documentation is neither unclear nor confusing. However, the
implication was not obvious (well... not obvious enough) when I first read
this section three years ago. If you're sincere about wanting
suggestions, here's mine:
of course :)
In addition to understanding the
Hi Stas.
The documentation is neither unclear nor confusing. However, the
implication was not obvious (well... not obvious enough) when I first read
this section three years ago. If you're sincere about wanting
suggestions, here's mine:
In addition to understanding the behavior of END blocks
Hi Jim, Stas,
On Fri, 12 Jul 2002, Stas Bekman wrote:
Jim Schueler wrote:
I just read the fine print:
:) Good man.
Apache::Registry runs BEGIN subroutines just once per child
process, but END routines run every time a script is run. The
implication is that an otherwise robust
Please read:
http://perl.apache.org/release/docs/1.0/guide/porting.html#END_blocks
The special case is for registry scripts that include END blocks. If the
the explanation at the above URL is unclear/confusing, please suggest
how to improve it.
It's pretty clear, and the bit about BEGIN
I just read the fine print: Apache::Registry runs BEGIN subroutines just
once per child process, but END routines run every time a script is run.
The implication is that an otherwise robust module may behave unexpectedly
when it's imported by an Apache::Registry script. Doesn't this cause
