So? You're not supposed to know anything the base class is doing. As long as its interface is strict and well-documented, you won't have a problem. Unit testing should handle your problem.
That's true, and I agree with that. However, I think that the nifty thing in this example is that they *can't* know anything about it.

It seems to me that Perl hasn't forayed into the commercial *product* market like other products. By that, I mean that you can develop a system in Perl (say, a web site), and you can sell that. Unlike other products, though, your end-user is free to muck about with it. In open source, this is A Good Thing, and I support it.

If you're trying to develop a product to sell, though, it can prevent you from handing out "demo" versions, pursuing upgrade revenue, or getting follow-on work.

Perlapp, in my mind, has been a nifty way to package up a piece of functionality, but before now it always meant that the end-user couldn't customize it or add to it (which is a beautiful thing in Perl). Now, with this approach, and a little planning, they can.

It's kinda like writing it in C, and letting your users plug in functionality with DLLs, except that you're still promoting Perl.

:)

-Dave

Update: Changed PERL => Perl

In reply to Re: Re: Win32 binary (and extensible) OO-perl applications by dpmott
in thread Win32 binary (and extensible) OO-perl applications by dpmott

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.