Let me be more explicit. If you change something from a simple accessor that you reach through the tie methods like $foo{'bar'} = 7 to a method call, you will have to either change that calling code to something like tied($foo)->set_bar(7) or else put a special case in the FETCH method so that it calls "set_bar()" if the key is "bar". This would break the abstraction in the former case or compicate the code in the latter.

UPDATE: as requested, an example, using your code. Say we change the definitions of get/set_foo in MyThing to something like this: 

sub set_foo {
  my ($self, $newfoo) = @_;
  $self->[1] = localtime(); # track last change
  $self->[0] = $newfoo;
  $self->_recalculate_bar();
}

sub get_foo {
  $self->[2] = localtime(); # track last access
  return $_[0]->[0];
}

[download]
After this change, the $clunker code using MyThing requires no changes at all. On the other hand, the tied HashAPI version, must change the accessing code from this: 
$slick->{foo} = 'Some value';
print $slick->{foo}, "\n";

[download]
to this: 
$slick->set_foo('Some value');
print $slick->get_foo(), "\n";

[download]
You could avoid needing this change by changing the FETCH and STORE, like this: 
sub STORE {
  my ($self, $key, $val) = @_;
  # assuming this class has more than just 'foo'...
  unless (grep { $_ eq $key } @CLASS_KEYS ) {
    croak (ref $self) . "has no $key member";
  }

  if ($key eq 'foo') {
    $self->[1] = localtime(); # track last change
    $self->[0] = $val;
    $self->_recalculate_bar();
  } else {
    # set normal keys somehow
  }

}

sub FETCH {
  my ($self, $key, $val) = @_;
  # assuming this class has more than just 'foo'...
  unless (grep { $_ eq $key } @CLASS_KEYS ) {
    croak (ref $self) . "has no $key member";
  }

  if ($key eq 'foo') {
    $self->[2] = localtime(); # track last access
    return $self->[0];
  } else {
    # get normal keys somehow
  }
}

[download]
That would quickly become cumbersome though.

In reply to Re^9: tie for Perlish, encapsulated objects by perrin
in thread tie for Perlish, encapsulated objects by Roy Johnson

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.