Another way:
package MyAgent; use parent 'LWP::UserAgent'; BEGIN {LWP::UserAgent->VERSION(6.39)}

But that's a little fragile; someone may refactor and forget to keep the BEGIN block after the call to parent causing things blow up. Sometimes code becomes complex, masking simple mistakes. I would prefer a solution that doesn't require the user to maintain several steps to set up inheritance while assuring minimal versions for parent classes.

I only now noticed this and must ask: how does this scenario cause things to blow up? Someone moving the BEGIN to before use parent? Even the most basic tests should catch that immediately.

TIMTOWDI:

use LWP::UserAgent 6.39; use parent 'LWP::UserAgent';

That makes an extra require but perl will check %INC, see that LWP::UserAgent has already been loaded, and proceed quickly. Normal style is that object-oriented modules export nothing, so the implicit ->import call should be harmless.

I believe that parent::versioned is the kind of feature that really does belong in the core or not at all — the TIMTOWDIs for it are just too simple to justify another dependency from CPAN for serious work, and it is the kind of feature that non-serious work does not care about.


In reply to Re: parent::versioned supports minimum version specification in parent classes by jcb
in thread parent::versioned supports minimum version specification in parent classes by davido

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.