in reply to Re^2: Ignoring not well-formed (invalid token) errors
in thread Ignoring not well-formed (invalid token) errors

If you do it like:

perl -ne'print $_ if ! /^<es\s*$/' huge.xml | perl -

Then you don't even have to wait for the huge file to be read twice. The time required could well be almost the same as it would be without the filter. Since the filter code likely can run faster than the XML parsing code, the difference in run-time could just be the insignificant time it takes to filter one buffer's worth of XML. It would likely take a bit more CPU (probably less than 2x), but I doubt processing a huge XML file is usually CPU-bound on most systems.

Though, brettski didn't seem to find even that proposal acceptable when I proposed it in chat around the time that the root node was posted.

- tye        

Replies are listed 'Best First'.
Re^4: Ignoring not well-formed (invalid token) errors (pipeline)
by brettski (Initiate) on Jan 19, 2015 at 19:22 UTC

    Tye, I must have not understood your proposal in the chatterbox. My apologies. This is good and I could use it on a case by case basis. I don't know 100% that I will always see the same line but I can substitute a different regex if necessary. I'm hoping this is just a rare occurrence and I will know more as I work with these files on a more regular basis.

    I was hoping there was some kind of exception handling that could catch this kind of error and move on. Though I know this goes against the XML doctrine on poorly formed XML