The execution is fine.

The constructor for Obj as chromatic wrote it will cheerfully construct things for subclasses.

However his very good point is that there appears to be no point in having your readers and writers have the methods in Obj, or vica versa. It is very easy to just say, "inherit", but inheritance used too often loses the point.

For serious food for thought, look through how LWP works. You will find a lot of classes, but things of different types (eg user agents, requests, responses) don't inherit from each other even though they interact quite a bit. And the design of the whole benefits from that.

In reply to RE (a lot) tilly: Object Heirarchy / Design by tilly
in thread Object Heirarchy / Design by lattice

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.