Would it have been clearer what I meant if I said "Always be orderly, even if you think you don't have to"? How about "Always use 'use strict', even if you think you don't have to?"

Most quests for a software methodology seem to boil down to a search for an "Always do it like this", e.g. always encapsulate (meaning, insulate the small parts from the behavior of the whole... this might or might not be done using OOP).

I would contend that every one of these principles is the enemy of strict parsimony. Should you never use encapsulation unless you know you need to, or should you always use (some form of) encapsulation, so you don't have to worry about whether you need to?

In reply to Re^6: Understanding 'Multiple Inheritance' by doom
in thread Understanding 'Multiple Inheritance' by punkish

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.