Recently I wrote a simple IRC client with POE::Component::IRC. I fixed the bugs in my client I've found. One day when I was testing it again, it died with "Badly formed CTCP message...". I looked into the module and found the answer:
($name, $args) = $_ =~ /^(\w+)(?: (.*))?/ or die "Badly formed CTCP message: \"$_\""; I spend some minutes to decide whether the modul needs that die or not. Finally I found that it isn't the way it should work. It makes Your client buggy. When some bad guy sends You an illegal CTCP, Your client dies immediately.

My questions are the following:

- do You think that "die" is important here?
- how can I prevent that to trigger? (I don't want to hack the module source)


<-- z0d -->

In reply to POE::Component::IRC and CTCP by z0d

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.