NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
On SAX (Score:2)
That's pretty much just how SAX works I'm afraid. It has a tendency to contain a large case statement with things that say: "If tag is this do this. If tag is that do that."
I'd welcome alternate ways of designing SAX handlers though. Unfortunately that tends to be the way data driven code works.
Trying SAX Modules
Re:On SAX (Score:1)
I'm not really knowledgable enough about SAX to understand this design problem to make a good suggestion, but I won't let that stop me.
I have been using XML::Twig and XML::Writer with some success, and have enjoyed the XPath features in XML::Twig.
Instead of writing a large case statement, I usually use a dispatch table. Typically I use a hash of anonymous subs, where the key to
It should work perfectly the first time! - toma
Re:On SAX (Score:2)
Re:On SAX (Score:1)
I posted a question about this at XML::Filter::Dispatcher string rules problem [perlmonks.org].
It should work perfectly the first time! - toma
Huge case statements (Score:1)
sub start_element {
my $self = shift;
my $e = ElementFactory->make_from_struct(shift);
$e->start_with_parser($self);
}
And have
start_with_parserdo the double dispatch trick:sub MyElement::docbook::para::start_with_parser {
my $self = shift;