Long ago in the pre Moose days I converted a great deal of data into a collection of hash tables with simple-minded code like (large hunks redacted/removed for brevity) the following:

package Chess::PGN::Moves;

use 5.006;
use strict;
use warnings;

require Exporter;

our @ISA = qw(Exporter);
our @EXPORT = qw(
    %King_Moves
);
our $VERSION = '0.05';

use vars qw(
    %King_Moves
);

%King_Moves = (
a1 => [qw(a2 b2 b1)],
b1 => [qw(a2 b2 c2 a1 c1)],
c1 => [qw(b2 c2 d2 b1 d1)],
);

1;
__END__
[download]

My question now is what is the Moose equivalent of such a thing. That is how do I a take a collection of static information (all hash tables as it turns out) and bring them into the 21st century object-wise? It is clear that this is do-able in terms of a dynamic hash, but I don't understand the plumbing well enough to abstract from that to what I need for pre-declared material. I've seen references to http://search.cpan.org/~drolsky/Moose-1.21/lib/Moose/Meta/Attribute/Native.pm which I find relatively clear, but again, it doesn't seem to speak to the notion of pre-declared information.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.