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
XML at last
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
--Larry Wall in <199911192358.PAA24109@kiev.wall.org>
Did I say I expect Perl to do the right thing? :-)
--Larry Wall in <199911200217.SAA24898@kiev.wall.org>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Followup (Score:2)
I don't get it. Last time I checked, expat was included in the XML::Parser distribution. Now I have to go fetch it myself? Why the regression? (I swear I remember being delighted when someone finally decided to include it; am I thinking of another module?)
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Expat conflicts (Score:1)
A common problem people encountered with Expat was that Apache included it by default. So if you tried to load XML::Parser under mod_perl Apache would segfault with a symbol clash. So the right solution is for the system to include a shared libexpat used by everyone that wants it.
Most Linux distributions provide Expat as a package and ActivePerl provides Expat in the distribution (PPM needs it). When I was using Solaris an HPUX, I found that binary packages were not hard to come by.
PS: re the thanks