I understand your frustration but you are just wrong.

Object oriented inheritance is not about reading the implementation of your SUPER classes.

If you are overriding method you should expect to reimplement it.

Consider: if the _helper_function's effect was contained in the method, you would not be complaining, but you would still have to reimplement the effect.

The SUPER class author is telling you outright not to count on the interface of _helper_function.

Just be happy he gave you an example implementation.

If you're going to use object programming, use method calls. Don't use functions.

Exactly right, but this should be applied to yourself as a client writer.

In reply to Re: $functions xor $methods by rir
in thread $functions xor $methods by Ovid

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.