comment on

That's funny, given that what else you said in this thread is only slightly truncated at:

If I never have to write an accessor generator by hand again, great!
I use Moose for anything with more than one object attribute.

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 self review of design prowess with a grain of salt.

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 sound like it, even just in this thread. :)

- tye

In reply to Re^3: How Large Does Your Project Have To Be to Justify Using Moose? (modular) by tye
in thread How Large Does Your Project Have To Be to Justify Using Moose? by jgamble

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks