| Subject: | The rare SAX parser issue |
I don't know if you have gotten anywhere with the latest test failures
of Trine. I figured I'd submit it to this tracker, since it is a test
failure. I've seen it before, and this is where I stopped the last time
I looked:
This error message
"Nonblocking reads only make sense if you're giving me file handles,
y'know (well, actually sockets). Use parse_file at
/home/trushel/cpan/build/5.15.3-m/RDF-Trine-0.137-TcXpYH/blib/lib/RDF/Trine/Parser/RDFXML.pm
line 159"
is emitted by XML::SAX::ExpatNB:
In the parser code, this is where it happens:
if (ref($string)) {
$self->{parser}->parse_file( $string );
} else {
$self->{parser}->parse_string( $string );
}
It is the parse_string line where it happens. So, it seems like in rare
cases, it chooses a parser which then passes parse_string to the
internal XML::SAX::ExpatNB parse, which expects a filehandle not a
string, and then croaks...
Seems like a complicated mess of parsers here. I don't know if you had
already figured this out yourself, if not I hope it helped a bit...
Cheers,
Kjetil