s/bad/frustrated/

Chill dude. I meant no harm.

Don't you mean bloomin' difficult in Perl harm? I troll, I troll.

Whether or not you actually meant harm to Perl with what you said, i am here to make sure that you don't harm Perl. What is the message you are sending out? That one would be better off NOT using Perl to work with XML. That is an outright lie and borderline slander.

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

Whatever...^H^H^H^H^H

I take back the flippant "Whatever" response. You asked a valid question and I posted a knee jerk response. Sorry about that.

My intention in my original question was that when you look at many of the XML parsing modules, they create hashes of XXXX where the depth tend to become rather unwieldly. XML::Simple is good for simple XML but not not so much for complex XML. On the flip side, libXML is a bit much for simple XML.

The thing that started all this? Flickr::API using the abandoned XML::Parser::Lite::Tree module. Granted Flickr's REST interface is simple ... it just happened to be the last straw.

Let me formally apologize to anyone that took offense and especially to you.

Jason L. Froebe

Blog, Tech Blog