<?xml version="1.0" encoding="windows-1252"?>
<node id="930064" title="Re^3: How Large Does Your Project Have To Be to Justify Using Moose? (modular)" created="2011-10-06 16:33:02" updated="2011-10-06 16:33:02">
<type id="11">
note</type>
<author id="22609">
tye</author>
<data>
<field name="doctext">
&lt;p&gt;
That's funny, given that what else you said in this thread is only slightly truncated at:
&lt;/p&gt;&lt;blockquote&gt;&lt;i&gt;&lt;p&gt;
If I never have to write an accessor generator by hand again, great!
&lt;/p&gt;&lt;p&gt;
I use Moose for anything with more than one object attribute.
&lt;/p&gt;&lt;/i&gt;&lt;/blockquote&gt;&lt;p&gt;
Otherwise, your question is obviously just rhetorical since I don't know what you do or don't do when you design.  Though, certainly, one should take a &lt;em&gt;self&lt;/em&gt; review of design prowess with a grain of salt.
&lt;/p&gt;&lt;p&gt;
I also never claim that using Moose makes good OO design impossible.  If you can fight the tendency that I pointed out, then good for you.  Though, it doesn't really &lt;em&gt;sound&lt;/em&gt; like it, even just in this thread. :)
&lt;/p&gt;
&lt;div class="pmsig"&gt;&lt;div class="pmsig-22609"&gt;&lt;p align="right"&gt;
- [tye]&lt;tt&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/tt&gt;
&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;</field>
<field name="root_node">
930019</field>
<field name="parent_node">
930056</field>
</data>
</node>
