There isn't a standard 'fatalsToEmail' pragma for the CGI::Carp module, however it would not be particularly difficult to build such functionality using the set_message method. This method allows a subroutine to be specified which is called with the text of the error message that caused the script to die - For example:

use CGI::Carp qw/ fatalsToBrowser set_message /; use Mail::Mailer; BEGIN { sub fatalsToEmail { my $error = shift; my $smtp = Mail::Mailer->new('smtp', Server => '127.0.0.1'); $smtp->open({ 'To' => 'you@yourdomain.com', 'From' => 'you@yourdomain.com' }); print $smtp $error; $smtp->close; } set_message(\&fatalsToEmail); }

As outlined in the CGI::Carp man page, the set_message routine should be called from within a BEGIN in order to correctly interpret compile-time errors.

 


In reply to Re: Is there a CGI::Carp fatalstoEmail ? by rob_au
in thread Is there a CGI::Carp fatalstoEmail ? by bear_phillips

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.