05:41:32 -0800, Steve Thames <[EMAIL PROTECTED]>
wrote:
>Consider this:
>
> my %names = (Bob => 'Robert Brower');
> my $caption = 'Name: $names{Bob)';
> print eval "qq|$caption|";
>
>If you can't see it, there is
On Fri, 31 Mar 2006 16:33:56 +0200, [EMAIL PROTECTED] (Tomas Zerolo)
wrote:
>On Fri, Mar 31, 2006 at 05:41:32AM -0800, Steve Thames wrote:
>> Consider this:
>>
>> my %names = (Bob => 'Robert Brower');
>> my $caption = 'Name: $
On Fri, 31 Mar 2006 08:48:20 -0500, Michael Peters
<[EMAIL PROTECTED]> wrote:
>
>
>Steve Thames wrote:
>> Consider this:
>>
>> my %names = (Bob => 'Robert Brower');
>> my $caption = 'Name: $names{Bob)';
>> print
In testing my mod_perl application, I would like to set up a die
handler that will return the fatal errors I am getting to a custom
"Server Error 500" page as well as write them to the log file.
I am considering using Error.pm. Does anyone have any suggestions?
Consider this:
my %names = (Bob => 'Robert Brower');
my $caption = 'Name: $names{Bob)';
print eval "qq|$caption|";
If you can't see it, there is a syntax error in $caption: closing
paren ) instead of brace }. The eval will produce no $@ and will
return the empty string.
Yeah, it turns out it works using the fixup handler. Odd thing is, it
works in the Init handler if I am debugging perl-status--just not
anything else.
Can anyone tell me why I can't get Apache::DB to work with the
following config?
In the PERLDB block, if I change the Location to '/perl-status', the
debugger activates fine. However, when its set to '/pa/session', I
never see the debugger. I just see the output from the response
handler in the
