> -----Original Message-----
> From: Connie Chan [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 16, 2002 12:13 PM
> To: Bob Showalter; [EMAIL PROTECTED]
> Subject: Re: How fatalsToBrowser works ?
>
>
> [...]
> > If you really want to munge the message, you could subclass
> CGI::Carp and
> > install your munger in front of the call to CGI::Carp::die in the
> > $SIG{__DIE__} handler.
> >
>
> But what is a 'munger' ? and what about $SIG{__DIE__}?
> How to play with ? Is there any reference documents I
> can read on ?
A 'munger' would be a routine you write to remove the offending information
from the error message. Since only you know what you want to remove, you
will need to write this.
__DIE__ is a pseueo-signal called by the die() function. CGI::Carp works by
installing its own handler for $SIG{__DIE__}. By subclassing CGI::Carp, you
could catch the __DIE__ signal yourself, adjust the error message, and pass
the (now adjusted) message on to CGI::Carp's normal routine.
perldoc -m CGI::Carp (to see how CGI::Carp works)
perldoc -f die
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
