I have a popular (nearly 40,000 downloads) piece of software. It's 
available on Mac (Classic and OS X), Windows (all), and most Linux systems 
I've tested it on. Currently, it's using XML::Simple to build various 
formats of XML into a hash/tree data structure. It's been doing that for 
the past two years now.

I've gotten some other opinions on this, but
roughly, I want to hear from the rest of the group:

  - is there any benefit from moving from
    XML::Simple to something like XML::SAX?

Keep in mind:

  - expat is the only xml parser currently fully crossplatform
    for all my needs. it's also easily included into an
    .exe or application file (for Mac or Windows).

  - I'm using XML::Simple, and I only want things in a hashref.

  - I've been hacking up namespace recognition code to go
    with the hashref XML::Simple uses. This was the "last
    straw" that made me look into XML::SAX again.

  - I rarely use XML::Parser's API for anything crucial. The nearest
    is to stop XML::Simple from creating a hashref of the entire
    alphabet - I dump into XML::Parser to create a tree of only
    letter 'b', for example.

  - I'm a fan of readability. This attempt at SAX parsing for
    the format I'm interested in (RSS) is "ooky" and not
    code shui, in my head:

     http://aaronland.info/weblog/archive/4637

    A hearty thanks to Aaron for exploring that for me.

  - Common API portability isn't crucial to me, since
    XML::Simple figures all that crap out for me (thanks, Grant!).

Thoughts?


-- 
Morbus Iff ( i'm the droid you're looking for )
Culture: http://www.disobey.com/ and http://www.gamegrene.com/
Please Me: http://www.amazon.com/exec/obidos/wishlist/25USVJDH68554
icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus

_______________________________________________
Perl-XML mailing list
Perl-XML@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs