Re: Filtering failing under Apache & mod

When I hear that a source filter works in normal Perl environments but then fails under Apache & mod_perl, my mind jumps to the following line from BEGIN, UNITCHECK, CHECK, INIT and END in perlmod:

The CHECK and INIT code blocks will not be executed inside a string eval(), if that eval() happens after the end of the main compilation phase; that can be a problem in mod_perl and other persistent environments which use eval STRING to load code at runtime.

Comment on Re: Filtering failing under Apache & mod_perl?

Replies are listed 'Best First'.
Re^2: Filtering failing under Apache & mod_perl? by clueless newbie (Curate) on Jul 19, 2010 at 19:49 UTC
No doubt that I am being extremely dense, but I haven't seen anything in Filter::Util, Filter::Simple or Smart::Comments that hint that filtering does NOT work under mod_perl. Evidence to the contrary (other than "Your code isn't working under mod_perl") would be appreciated. Suggestions on how to make it work would be appreciated even more.	[reply]
Re^3: Filtering failing under Apache & mod_perl? by kennethk (Abbot) on Jul 19, 2010 at 20:37 UTC
A little googling for "source filter" mod_perl uncovered this gem from a few years ago: http://www.issociate.de/board/post/363951/Using_%22switch%22_in_%3CPerl%3E_section..html. Search page for "source filter".	[reply]