Stories
Slash Boxes
Comments
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

use Perl Log In

Log In

[ Create a new account ]

Matts (1087)

Matts
  (email not shown publicly)

I work for MessageLabs [messagelabs.com] in Toronto, ON, Canada. I write spam filters, MTA software, high performance network software, string matching algorithms, and other cool stuff mostly in Perl and C.

Journal of Matts (1087)

Monday July 28, 2003
06:22 PM

On XML::Parser

[ #13741 ]

I'm now maintaining XML::Parser. This is probably "my" most downloaded module, but it's not mine really so it doesn't count.

It's not a nice module (in that it takes the XML::Parser namespace which makes newbies think that it is the way to parse XML, and it's not compatible with any other APIs (SAX)), so from here on out it will be purely bug fixes. Any bugs please send to the perl-xml list.

I just released 2.32 which ironically broke XML::DOM. TJ has just released a new XML::DOM that fixes this (it was an invalid assumption in XML::DOM anyway). All fun and games.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • It's good to see XML::Parser finally has somebody taking care of it. I realise that it's mostly stable, but bugs inevitably occur, and it's good to see new versions get released with fixes.

    Now, I just need to figure out a suitable patch to let XML::SAX::Expat throw the correct exceptions and pass it to you...

    -Dom

  • As you have repeatedly said in the past "Don't use XML::Parser", I'm not conviced this is such a good thing. :-)