You have clearly not understood anything I've written.
Methods like get_/set_ do not necessarilly correspond to any actual member variable of an object
I'm talking about an API. That was the main thrust of my original post. Actual member variables are supposed to be hidden, and they are hidden equally well by my method or yours.
Making FETCH and STORE procedures that handle every possible method call would mean
I didn't suggest that they should handle every possible method call. They are specifically for simple accessors. Any other methods would be written just as before.
Caution: Contents may have been coded under pressure.

In reply to Re^8: tie for Perlish, encapsulated objects by Roy Johnson
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.