Be very, very careful.

Relying on the details of someone else's implementation is a very bad thing to do. Oh, lots of people do it. It works. But it leads to extra complexity, potential problems with future changes to the library, etc, etc, etc.

In general assume that anything not explicitly documented can and will change. Work with the interface whereever possible. Anything which pokes around in internals you have no business accessing should be regarded as probable future breakage. And remember that modular code is broken into components, each of which has a simple interface to the outside world. Keep your interfaces simple and clean, only use those interfaces. you will save a lot of headaches...

In reply to Re (tilly) 2: Is there always MTOWTDI? by tilly
in thread Is there always MTOWTDI? by PsychoSpunk

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.