Skip Menu |

This queue is for tickets about the XML-SAX-Expat-Incremental CPAN distribution.

Report information
The Basics
Id: 13764
Status: resolved
Priority: 0/
Queue: XML-SAX-Expat-Incremental

People
Owner: NUFFIN [...] cpan.org
Requestors: grantm [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in: 0.02
Fixed in: 0.04



Subject: XML::SAX::Expat::Incremental should not install itself as default SAX parser
This idea of this module seems very useful, however since the module does not implement the full SAX API, it should not register itself in ParserDetails.ini. The current install script breaks all scripts on the target machine which use SAX. The attached simple test script works with any SAX parser. It no longer works after XML::SAX::Expat::Incremental has been installed. The simplest solution is to not register with ParserDetails.ini at all. A more complex solution would be to re-arrange the entries after registering so that XML::SAX::Expat::Incremental is not the last (default) entry.
#!/usr/bin/perl -w use strict; use XML::SAX::ParserFactory; use XML::SAX::Writer; my $h = XML::SAX::Writer->new; my $p = XML::SAX::ParserFactory->parser(Handler => $h); $p->parse_file(\*DATA); __DATA__ <people> <person>Jack</person> <person>Jill</person> </people>
RT-Send-CC: matt [...] sergeant.org
Looking at the XML::SAX docs I don't see a variation on add_parser that does not set the new parser as the default... Matt: can you help us out?
Show quoted text
> The simplest solution is to not register with ParserDetails.ini at > all.
Okay, while I'd still like to keep this open, so that we can find a better solution, i've uploaded 0.04, that doesn't register. Sorry for all the trouble this may have caused you!
this is fixed IIRC