Re^3: XML::Simple giving a non-specific error

By the way, the error wasn't reported at the end of the file

Judging by the byte position (377), it was (the closing angle bracket of </ROOT> is byte 375^(*)). I don't know why the line number is reported one less than it should be — maybe the <?xml ...?> header isn't being counted.

As for your other point, I think you're right if the parser would keep track of all starting positions of so far unclosed tags.

___

^(*) assuming unix newlines, which I did after having seen i386-linux-thread-multi in the OP's error message.

Comment on Re^3: XML::Simple giving a non-specific error Select or Download Code

Replies are listed 'Best First'.
Re^4: XML::Simple giving a non-specific error by ikegami (Patriarch) on Mar 12, 2010 at 00:50 UTC
If a guy catches the baseball at the edge of the outfield, it's not the edge of the outfield that caught the ball. Aside from the fact that it really was found before EOF (since at least the last newline and the EOF remain unparsed), the point was that the error could have been caught earlier, and would have been caught earlier (say if you had `<ROOT><BODY><ERROR><ERROR></BODY></ROOT>`). Besides, the following indicates the reported byte pos for me: `</ROOT> ^ \|` [download]	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^4: XML::Simple giving a non-specific error
by ikegami (Patriarch) on Mar 12, 2010 at 00:50 UTC

If a guy catches the baseball at the edge of the outfield, it's not the edge of the outfield that caught the ball. Aside from the fact that it really was found before EOF (since at least the last newline and the EOF remain unparsed), the point was that the error could have been caught earlier, and would have been caught earlier (say if you had <ROOT><BODY><ERROR><ERROR></BODY></ROOT>).

Besides, the following indicates the reported byte pos for me:

</ROOT>
  ^
  |
[download]

[reply]
[d/l]
[select]