I once implemented a similar hierarchy, but all the derived classes used the same %RootClass::attr_data. As I needed some statistics over existing objects in each class, I used ref of each object as the top level key in the hash, it also simplified inspecting the hash for human readers as the key indicated what data to expect in the deeper structure. Something like 
#!/usr/bin/perl
use warnings;
use strict;
use feature qw{ say };

{   package My::Root;
    use Scalar::Util qw{ refaddr };

    our %attr;
    sub new {
        my ($class, $name) = @_;
        my $o;
        $attr{$class}{ refaddr(\$o) }{name} = $name;
        bless \ $o, $class;
    }
    sub name {
        my ($self) = @_;
        $attr{ ref $self }{ refaddr($self) }{name}
    }
    sub count {
        my ($class) = @_;
        return scalar keys %{ $attr{$class} }
    }
}

{   package My::Child;
    use parent -norequire => 'My::Root';
}

my $o1 = 'My::Root'->new('root1');
say $o1->name;

my $children = map 'My::Child'->new("child$_"), 1 .. 10;
say "Number of Root instances: ", 'My::Root'->count;
say "Number of Child instances: ", 'My::Child'->count;

[download]

map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]

In reply to Re: Class attribute handling by choroba
in thread Class attribute handling by Dirk80

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.