Yeah it knows its not "technically" valid xml but XML::Parser does not care about that. XML::Checker::Parser would.
The versions of XML::Parser of the same, I have an idea it may be Expat chucking out the results in a different format but I cannot be sure. "Wiggins D'Anconia" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Keith Boynton wrote: > > I am having some problems with the XML::Parser module. It is returning an > > error when passed some valid xml in the form of a string. The error it > > returns is: > > > > No element found at line 1, column 0 byte -1 > > > > This seems to suggest that the string is empty although if I print the > > string immediately prior to trying to parse it, the contents are fine. > > > > Here is a copy of the code: > > use XML::Parser; > > > > my $sourceXML="<h><j>whatever</j></h>"; > > > > Technically the above is not well-formed XML, possibly the parser checks > this.... > > > > > This exact code works fine on another machine. Any ideas? > > > > Have you checked the versions of the XML::Parser module (and even perl) > to make sure they are the same? > > http://danconia.org > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
