Using Memoize is certainly possible, but you'll need to jump through a couple of hoops - you must only memoize() the 'get' functionality, and need to be able to clear the cached value as part of 'set' - so it's probably easiest doing it the way you already are.

I've not used this myself, but I believe it should work something like this (untested):

  use Memoize;
  my(%_getscalar, %_getlist);
  memoize(__PACKAGE__ . '::_get',
    SCALAR_CACHE => [ HASH => \%_getscalar ],
    LIST_CACHE => [ HASH => \%_getlist ],
  );

  # in _set()
  sub _set {
    my($self, $element, $value) = @_;
    ...
    # default normaliser
    my $cachekey = join "\034", $self, $element;
    delete $_getscalar{$cachekey};
    delete $_getlist{$cachekey};
    ...
  }

[download]

Hugo

In reply to Re: Memoizing Methods by hv
in thread Memoizing Methods by bduggan

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.