Re: Req_rec undefined when calling Embperl::Execute from within a mod_perl Method handler

Hi, I have found the problem and trying to resolve it. Just give me a few days time... Gerald Am Donnerstag, 17. Februar 2005 15:18 schrieb Martin Moss: > Hi Gerald, > > We're using :- > > Apache 1.3.33, mod_perl-1.29, perl v5.8.6 on SunOS 5.7 > Generic_106541-10 sun4u sparc > SUNW,UltraSPARC-

Re: [RESEND] Trapping errors

> > And then in base.epl, something like this: > > eval { Execute('*') }; > if($@) { > Execute('error.epl', $@); > } > Instead use Execute({inputfile => '*', options => Embperl::Constant::optReturnError, errors => [EMAIL PROTECTED]) ; if (@errors) { Execute ( } Gerald

Re: Req_rec undefined when calling Embperl::Execute from within a mod_perl Method handler

No worries, thanks Gerald, Marty --- Gerald Richter <[EMAIL PROTECTED]> wrote: > Hi, > > I have found the problem and trying to resolve it. > Just give me a few days > time... > > Gerald > > > Am Donnerstag, 17. Februar 2005 15:18 schrieb Martin > Moss: > > Hi Gerald, > > > > We're using

Re: SEGFAULT on Mac OS X 10.2

Hi, Am Montag, 21. Februar 2005 20:35 schrieb Derrick Spell: > I've got a Mac OS X 10.2 server loaded with Apache 2.0.52, mod_perl > 2.0rc4, Perl 5.8.6, Embperl 2.0rc2 - All installed fresh by hand (no > factory installations) > At rather irregular intervals my apache children will segfault during

Re: [RESEND] Trapping errors

> Instead use > > Execute({inputfile => '*', options => > Embperl::Constant::optReturnError, > errors => [EMAIL PROTECTED]) ; > if (@errors) { > Execute ( > } > I've been doing something recently with Execute and @errors, and I noticed that the @errors array also contained any 'warnin

RE: [RESEND] Trapping errors

> > > Instead use > > > > Execute({inputfile => '*', options => > > Embperl::Constant::optReturnError, > > errors => [EMAIL PROTECTED]) ; > > if (@errors) { > > Execute ( > > } > > > > I've been doing something recently with Execute and > @errors, and I noticed that the @errors array al

Re: [RESEND] Trapping errors

Hi Gerald, Thanks for your reply. On Tue, Feb 22, 2005 at 05:52:33PM +0100, Gerald Richter wrote: > > And then in base.epl, something like this: > > > > eval { Execute('*') }; > > if($@) { > > Execute('error.epl', $@); > > } > > > > Instead use > > Execute({inputfile => '*', options

Re: [RESEND] Trapping errors

Hi, > > Any way to make this behave more like croak/die? These seem to check if > their argument is a reference. If it is, they just drop the reference > into $@, otherwise they add context (line number, etc). > I take a look at it if I can change the error handling in this way. I agree that thi

Re: [RESEND] Trapping errors

On Wed, Feb 23, 2005 at 05:28:17AM +0100, Gerald Richter wrote: > > Any way to make this behave more like croak/die? These seem to check if > > their argument is a reference. If it is, they just drop the reference > > into $@, otherwise they add context (line number, etc). > > > > I take a look at

[OT] Yet Another Perl Conference North America 2005 announces call-for-papers

YAPC::NA 2005 (Yet Another Perl Conference, North America) has just released its call-for-papers; potential and aspiring speakers can submit a presentation proposal via: http://yapc.org/America/cfp-2005.shtml The dates of the conference are Monday - Wednesday 27-29 June 2005.