RE: returning errors from Execute

2006-02-16 Thread Gerald Richter
> > On 2/12/06, Kathryn Andersen <[EMAIL PROTECTED]> wrote: > > Why is that hard to parse? Use perl regular expressions, > that's one > > of the things it is good at. > > > > You'd just have to go > > > > foreach (@errors) { > >if (/FIXME/) { > > # respond to this error > >} > > }

Re: returning errors from Execute

2006-02-12 Thread Dan Lenski
On 2/12/06, Kathryn Andersen <[EMAIL PROTECTED]> wrote: > Why is that hard to parse? Use perl regular expressions, that's one of > the things it is good at. > > You'd just have to go > > foreach (@errors) { >if (/FIXME/) { > # respond to this error >} > } > > That should enable you to

Re: returning errors from Execute

2006-02-12 Thread Kathryn Andersen
On Sun, Feb 12, 2006 at 04:15:03PM -0500, Dan Lenski wrote: > I've recently learned to use the error-catching feature of > Embperl::Object's Execute command. The thing I'm wondering is if it's > possible to make it return just the string or object that I pass to > the croak/die command, rather tha

Re: returning errors from Execute

2006-02-12 Thread Dan Lenski
I've recently learned to use the error-catching feature of Embperl::Object's Execute command. The thing I'm wondering is if it's possible to make it return just the string or object that I pass to the croak/die command, rather than the complete Embperl error message. I would like to be able to do