I don't believe you think that using caller to implement access control or interface selection is a reasonable idea. I don't believe that even though you just said it.

I know that kind of trick has been used to implement something like private or protected methods; I would rather not debate if it is reasonable or not.

What I have done is use caller information to decide how a routine behaves, so that if caller()->isa("Picky::Class"), the data passed is handled ... slightly differently.

What can I say? It seemed like a reasonable idea at the time.

... and it has worked without redesign for years now :-)

The Sidhekin
print "Just another Perl ${\(trickster and hacker)},"

In reply to Re: Re: Re: AUTOLOAD and call tracing by Sidhekin
in thread oop - obvious AUTOLOAD question by princepawn

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.