I may have exactly what you are looking for.
Ovid has a series of blog articles about his attempts to solve some of the inheritance tangles at the BBC. Here they are in order.
Pictures of the class hierarchy in question.
Initial thoughts on how roles might help. Then he ran into
an interesting technical issue. More
thoughts on refactoring using Moose roles. Then
roles start to pay off for him. Then
more on why this is good.
This gives you a sense of how migrating to Moose worked out for a good programmer on a realistically complex code base. Better yet, he describes exactly why it was helpful for him, and you get to see both the positives and negatives with a timeline to indicate how much of an investment this was.
Speaking personally my reaction was, "I'd rather work on a small code base without all of that complexity." But if I had to work in a larger code base, I'd definitely investigate whether Moose could clean things up.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.