I don't quite understand what you want. Should each class have its own %types hash, but somehow fall back to the parent's hash if something is not found? If yes, that can be implemented with methods and SUPER:: calls.

Or do you want one hash in the base class, and populate it along the way? That might look like this:

use strict; use warnings; { package Base; our %types = qw/BASE_TYPE Some::Class/; sub get_type { $types{$_[0]} } } { package Foo; our @ISA = qw/Base/; $Base::types{FOO_TYPE} = q/Another::Class/; } { package Bar; our @ISA = qw/Base/; $Base::types{BAR_TYPE} = q/Yet::Another::Class/; } use Data::Dumper; print Dumper \%Base::types; print Base::get_type('BAR_TYPE'), $/;

In reply to Re: How to implement such kind of magic? by moritz
in thread How to implement such kind of magic? by llancet

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.