Bros,

I am reading RSS feeds with XML::FeedPP. It's been working fine for quite some time, but today I got an error on the cron job Invalid string: [\x6A\x74\x61\x62\x6C\x65\x73\x65\x73\x73\x69\x6F\x6E::\x73\x74\x6F\x72\x65 \x66\x61\x69\x6C\x65\x64] before <br /> at /home/perl/usr/lib/perl5/site_perl/5.8.8/XML/FeedPP.pm line 478

Line 478 is where it's parsing the feed, so obviously, there is a squirrely entry in one of the feeds I'm reading, which I'm tracking down.

But I was surprised to get this error in the first place because I'm invoking the feed inside an eval to guard against such an event, i.e. eval { $feed = XML::FeedPP->new( $feedurl ) }; Will this not trap errors that occur inside the module? If not is there some other way to do that? I don't want my reader to crash every time someone inserts a non-standard element in a feed.

TIA....Steve

In reply to XML::FeedPP how to trap error by cormanaz

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.