OK, so, playing around with my test version, I've discovered that including Use Try; breaks it in exactly the way I'm seeing, regardless of whether or not there are any try/catch blocks. If I remove Try from my script, it works (but will be more fragile), except that it's still breaking on some feeds, always on lines that contain CDATA, but they all include CDATA blocks, and these aren't the first in the feeds, so it's not going to be that obvious:

-- Feed is broken -- End tag mismatch (itunes:subtitle != content:encoded) [Ln: 735, Col: 2 +93548366282188] Line 734 78 <itunes:subtitle><![CDATA[It is the QUESTIONS +EPISODE!]]></itunes:subtitle>

If I run it several times, the same feeds are consistently breaking on the same line, so something weird is still happening.


In reply to Re: RSS Parsing not working on new machine by wintermute115
in thread RSS Parsing not working on new machine by wintermute115

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.