"Parent class" and "Child class" are really bad terms. The best way to think about it, imho, is in terms of generalized vs. specialized. A "child class" is the specialization of the "parent class". You don't create a massive OO system for only one set of behaviors. You create it when you have several sets of behaviors that share a lot of common behaviors. The generalized case (parent class) provides the common behaviors. Then, each set of behaviors adds its own bits in a specialized case (child class).
What you're talking about regarding ThisFeature vs. ThatFeature sounds more like roles, honestly. Read ALL the documentation for Moose. That will probably help a lot. Oh, and when you decide to build a big OO system, use Moose. It will save you a lot of heartache.
My criteria for good software:
- Does it work?
- Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
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.