<?xml version="1.0" encoding="windows-1252"?>
<node id="1007150" title="Re: OO Perl Usage" created="2012-12-04 15:23:48" updated="2012-12-04 15:23:48">
<type id="11">
note</type>
<author id="424801">
bitingduck</author>
<data>
<field name="doctext">
&lt;p&gt;Looks useful and easy to use-- I'll probably check it out in the next week or so.  Like [roboticus], most of what I do is quick hacks of a page or so rather than applications, but unlike him, a large fraction of it is XML in one form or another.  I've been playing in the ebook world, and just about everything seems to be some kind of XML.  I end up using a bunch of different modules depending on how complicated the thing I'm dealing with is.&lt;/p&gt;
&lt;p&gt;And I actually prefer XML over YAML and JSON.  I think it's generally easier to make sense of if you're looking at it in isolation&lt;/p&gt;

&lt;p&gt;edit: And to address the OO topic-- I tend to use OO based modules.  It's not something that I really think about too much, as I look more for whether they do what I want easily than OO or not.&lt;/p&gt;</field>
<field name="root_node">
1007125</field>
<field name="parent_node">
1007125</field>
</data>
</node>
