This bit:

my $self_term=shift; my $self=shift;

... seems to be assuming that your handler will be called with two arguments, the second of which is an object.

But if you read sigtrap which refers you to perlvar you'll see that for real signals (not Perl's internal __DIE__ and __WARN__ signals) the handler gets passed just one parameter: the name of the signal (e.g. "INT", "QUIT", etc).

The fact that you're using Moose makes no difference here.

What are you actually hoping to achieve? What's the overall reason you're installing a signal handler? If you explain that, then perhaps somebody can give you some advice about how to go about doing it.

perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'

In reply to Re: Any one know how to use sigtrap with moose? by tobyink
in thread Any one know how to use sigtrap with moose? by hisycg@gmail.com

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.