Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister

Re^4: Ignoring not well-formed (invalid token) errors (pipeline)

by brettski (Initiate)
on Jan 19, 2015 at 19:22 UTC ( #1113807=note: print w/replies, xml ) Need Help??

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

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

  • Comment on Re^4: Ignoring not well-formed (invalid token) errors (pipeline)

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1113807]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (6)
As of 2022-11-29 12:12 GMT
Find Nodes?
    Voting Booth?