Brothers, for reasons that I won't bore you with I have a big hashy structure thing and now I want to objectify it so that I create a corresponding method for each fieldname. So in my naivety I started writing a method for each key of the hash within my package (class) as follows: 
sub status {
return $_[0]->{status};
}
sub deadline {
return $_[0]->{deadline};
}
sub chasedate {
return $_[0]->{chasedate};
}
.
.
.

[download]
When it suddenly occurred to me that if this cannot be how the great God Wall intended things to be. Repetition not being a favourite thing in any PL, let alone PERL. However, I am not too savvy with objects let alone doing clever stuff with subroutines. I'm sure there's an easy answer to eliminating all these methods into a single clever one. Can anyone elucidate?

In reply to Object methods from hashy structures by jfrm

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.