At 09:49 AM 4/26/00 +0100, Steve Hay wrote:
> > [snip]
> >
> > Go into your CGI::Carp.pm file and look for the
> > ineval() method. Manually edit it to remove the 5.005 check and just
> > compile an ineval() routine that is dependent on longmess() instead of $^S.
>
>Thanks very much for your repl
Gunther Birznieks wrote:
> At 02:02 PM 4/18/00 +0100, Steve Hay wrote:
>
> >I'm having problems using "CGI::Carp qw(fatalsToBrowser);" in modperl
> >scripts.
>
> Sorry for the late reply. I was actually trying to figure out why you were
> experiencing this problem. I rarely use Perl 5.005 specifi
At 02:02 PM 4/18/00 +0100, Steve Hay wrote:
>I'm having problems using "CGI::Carp qw(fatalsToBrowser);" in modperl
>scripts.
Sorry for the late reply. I was actually trying to figure out why you were
experiencing this problem. I rarely use Perl 5.005 specific features, and
so I actually recei
At 12:46 PM 4/18/00 +0100, Matt Sergeant wrote:
>On Tue, 18 Apr 2000, Steve Hay wrote:
>
> > I'm having problems using "CGI::Carp qw(fatalsToBrowser);" in modperl
> scripts.
>
>Then don't use CGI::Carp. The whole qw(fatalsToBrowser) thing is broken,
>IMHO, anyway. See http://modperl.sergeant.org/
At 06:38 PM 4/19/00 -0700, Perrin Harkins wrote:
> > > CGI::Carp can't catch compile errors.
> >
> > Oh. The CGI::Carp manpage says (regarding the use of "set_message()" to
> > control the output message): "In order to correctly intercept compile-time
> > errors, you should call set_message() fr
On Wed, 19 Apr 2000, Steve Hay wrote:
> > Sounds like a difference in the way CGI scripts and mod_perl buffer. I
> > fyou really want CGI::Carp to work, you need to make sure you don't send
> > any output before it gets called. Maybe you have PerlSendHeader on?
>
> I did have PerlSendHeader On:
Perrin Harkins wrote:
> On Tue, 18 Apr 2000, Steve Hay wrote:
>
> > The first one calls die() itself.
> [...]
>
> Sounds like a difference in the way CGI scripts and mod_perl buffer. I
> fyou really want CGI::Carp to work, you need to make sure you don't send
> any output before it gets called.
On Tue, 18 Apr 2000, Steve Hay wrote:
> I'm having problems using "CGI::Carp qw(fatalsToBrowser);" in modperl
> scripts.
[...]
> The first one calls die() itself. Under Apache/CGI the die() message
> appears in the web browser (albeit preceded by a
> spurious Content-Type line), but under Apache/m
Sorry! Here it is again in text/plain this time...
(My mail client doesn't ask whether I want to send in text or HTML,
hence the slip. Maybe *I* should get a new one!)
---
I'm having problems using "CGI::Carp qw(fatalsToBrowser);" in modperl
scripts.
Below are three short scripts and their o
On Tue, 18 Apr 2000, Steve Hay wrote:
> I'm having problems using "CGI::Carp qw(fatalsToBrowser);" in modperl scripts.
Then don't use CGI::Carp. The whole qw(fatalsToBrowser) thing is broken,
IMHO, anyway. See http://modperl.sergeant.org/guide/exceptions.html for
a better way to handle exception
I'm having problems using "CGI::Carp qw(fatalsToBrowser);" in modperl
scripts.
Below are three short scripts and their output under Apache/CGI
and Apache/modperl. All three of them produce (more or less) useful
output under Apache/CGI, but only the last one does under Apache/modperl.
The first o
11 matches
Mail list logo
