Well, duh, yeah, I want to cluck. Woops. However, it still gives me a wierd behaviour:

$ perl a.pl Use of uninitialized value in print at a.pl line 11 (#1) (W uninitialized) An undefined value was used as if it were alread +y defined. It was interpreted as a "" or a 0, but maybe it was a mi +stake. To suppress this warning assign a defined value to your variables. To help you figure out what was undefined, perl tells you what ope +ration you used the undefined value in. Note, however, that perl optimiz +es your program and the operation displayed in the warning may not necessa +rily appear literally in your program. For example, "that $foo" is usually optimized into "that " . $foo, and the warning will refer +to the concatenation (.) operator, even though there is no . in your program. Use of uninitialized value in print at a.pl line 11. at a.pl line 11 main::foo() called at a.pl line 14 (#1) Use of uninitialized value in print at a.pl line 11. at a.pl line 11 main::foo() called at a.pl line 14 at a.pl line 11 main::foo() called at a.pl line 14 done.
For some reason, I'm getting that warning twice. Note also that I had to add a few extra lines to the callstack function:
sub callstack { &$oldwarn if $oldwarn; require Carp; delete $SIG{__WARN__}; goto &Carp::cluck; $SIG{__WARN__} = \&callstack; }
For some reason, Carp::cluck calls warn, so disabling the warn handler gets rid of the infinite recursion. A bit more digging changes the above to:
sub callstack { &$oldwarn if $oldwarn; require Carp; print STDERR Carp::longmess(@_); }
which solves the problem - the warning message only shows on the screen once.


In reply to Re^2: Automatic stack tracebacks in warnings? by Tanktalus
in thread Automatic stack tracebacks in warnings? by Tanktalus

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.