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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Perl is a great tool for processing XML. Check out some of the modules in the XML:: and W3C:: namespaces.

    If you need to increase the runtime performance, you could always install Apache with mod_perl.

    Clark Cooper did a performance test of various XML parsers in C/C++, Perl, Java and Python a while back for, and his XML::Parser gave adequate performance for most purposes. Of course, "adequate performance" is highly subjective; I don't think I'd even to use Perl or Java if I were managing a few

  • An XML parser does not an application make. As Larry's been known to say: "The complexity has to go *somewhere*".

    I think you should stick to Perl until you have something that absolutely doesn't work with it. But maybe that's just me.

  • All you say is that you need to port some services to XML. Services that have to do with DB-backed sites. But you don't tell any details of either what needs to be done, what the requirements are, and what you have to work with.

    Yet you ask for an objective opinion. IMO, that's a very unrealistic wish.

    -- Abigail

  • I'd say managing Tb of XML data is perfectly feasible in Perl or Java... it depends on how you need to use that data.. Certainly DOM is a no-no... but SAX lets you work on small bits of the grove without reading the whole thing to memory...

    I'd just hope there where validating parsers in Perl, but we'll have to wait a bit or use xpat in C, directly...

    (or maybe just help the author of XML::Parser... :)
    $ pugs -M6 -e 'say "use 6 :)"'
    use 6 :)