-Original Message-
From: Perrin Harkins [mailto:[EMAIL PROTECTED]]
My problem is that die works fine as such but it conks out if done
inside a eval.
Okay, I missed the part about eval() before. Take a look at this code
from Parse::ePerl::Evaluate() :
local $SIG{'__DIE__'} =
Perrin Harkins wrote:
local $SIG{'__DIE__'} = sub { $error .= $_[0]; };
That's going to kill your exception handling code. You need to change
that if you want to be able to use eval() in your code. Matt has an
explanation of this in the exceptions part of the mod_perl Guide.
Hmm,
I
print STDERR blah blah blah is going to the browser but I am not
really worried about it too much unless it is something I should worry
about - anyone care to comment on that ?
Printing error messages to the public is a potential security risk, so
you have to decide how paranoid you want to
Perrin Harkins wrote:
Umm I didnt mean to offend anyone in my previous posting - I did say I
probably hadnt presented my situation properly.
First, ePerl has nothing to do with Embperl or Mason. It is a totally
Ofcourse you noticed I wrote ePerl/EmbPerl/Mason ?? I clubbed them
together
On Mon, 21 Jan 2002, Mithun Bhattacharya wrote:
Perrin Harkins wrote:
Umm I didnt mean to offend anyone in my previous posting - I did say I
probably hadnt presented my situation properly.
I don't think anyone was offended. Perrin was just trying to help you see
why people might not have
Umm I didnt mean to offend anyone in my previous posting - I did say I
probably hadnt presented my situation properly.
No problem, I just meant don't give up so quickly.
Ofcourse you noticed I wrote ePerl/EmbPerl/Mason ?? I clubbed them
together since I assume among other things you can
