Maybe one shouldnt rely on it, but I'd hope that anybody writing a subclass of one of my classes would be calling $self->SUPER::new(@_) and so at least initialize my class the way it should be, instead of just overwriting the 'new' method. Theres not much use in inheriting, if you're not using what the module provides. Of course, that doesn't stop the overwritten method killing the contents of the object, there are ways to hide them, if you're that worried about it (theres a lovely chapter in the Camel about objects :)..
I guess you either hide everything, document properly, or do it another way.. As the book says, Perl doesn't lock you out, it just hopes you're polite enough not to wander into its space. (or something similar..)

C.

In reply to Re: OOP safety by castaway
in thread OOP safety by nothingmuch

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.