Hi Monks,

Is there a known problem with inheritance on Perl 5.6.0?

Briefly: I was working with a CPAN module that relies upon my subclass inheriting from an inheritance hierarchy above it. On a Linux box with 5.6.1 everything works, but my tests fail on a Mac with 5.6.0 with a "method not found" error. All the modules are installed, and the @ISA arrays seem to be intact and show the right inheritance -- but calls to UNIVERSAL::isa show that the Linux/5.6.1 setup correctly inherits, while the Mac/5.6.0 setup breaks 3 classes up the hierarchy.

Is there a smoking gun I'm missing here? E.g., is it well-known that 5.6.0 doesn't inherit properly?

(If there is no smoking gun or further info is needed, I can post specifics; the breakage seems to be between Class::DBI:__::Base and Ima::DBI and I have tests that bear this out.)

Best,

Randall

In reply to Broken inheritance on 5.6.0 / Mac OS x 10.2 ? by rlucas

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.