Ignoring the mistake which you have since fixed, posting a runnable example of your problem is invaluable. At best we can extrapolate what we *thin* you code might look like in a runable form, and try that -- in my case, it works fine...

#!/bin/perl -l use warnings; use strict; package Bar; sub new { print STDERR "Bar'ed"; my $class = shift; my $self = {}; bless $self, $class; } package Foo; use base qw/Bar/; sub new { print STDERR "Foo'ed"; my $class = shift; my $self = $class->SUPER::new(@_); bless $self, $class; return $self; } my $foo = Foo->new; print ref($foo); # gives "Foo"

...Produces...

hossman@bester:~$ perl ~/tmp/monk.pl Foo'ed Bar'ed Foo

In reply to Re: Duh. What am I missing about inherited constructors? by hossman
in thread Duh. What am I missing about inherited constructors? by locked_user sundialsvc4

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.