Hi,
I'm trying to figure out what's wrong:
I have a cgi script running under mod_perl. I want this script to call a
ePerl document. I have other ePerl documents running under mod_perl, and
it's running fine.
So, on the command line, my script works fine with Parse::ePerl::Expand.
But when running within mod_perl, I can't get Parse::ePerl::Evaluate to
work. (Since I was having some problem, I've used the two-steps
Translate-Evaluate instead of Expand). Parse::ePerl::Translate is
working fine, but I've end up using eval($script) to make things work.
When trying to use Expand, I got no errors in my logs, even with Error
specified. I simply get an empty file. If I put some print statements
after Expand, they don't even work.
So I have three questions:
1) What could be the reason for Parse::ePerl::Evaluate not to work?
2) Except the additional functionalities (cwd, Env, etc), is there any
other differences, especially impact on caching and precompiling? How
should I choose
3) How should I choose if I should precompile my script (and using
&$script instead) or not?
BTW, what's the future of ePerl? Development has been quiet for over a
year. Is Ralph Engelschall still the maintainer? And it's sad to see
that perl.apache.org doesn't mention ePerl anymore, while it mentions
HTML::Embperl.
Here is some version info:
LinuxPPC R5 (RH 6.0 derivative, glibc 2.1 based)
Apache 1.3.6
mod_perl 1.19
ePerl 2.2.14
Cheers,
Simon Piette
