As you say it is bad design. Why not just call a user method on the object - this method just needs to know where to go for its data? But as (almost) always Perl will accomodate you.

package Bad::Design; use Data::Dumper; my $o = Bad::Design->new(); print Dumper $o; print $o->parameters->user, $/; $o->parameters->user('Matt Wright'); print $o->parameters->user, $/; sub new { bless { 'params' => { user => 'Randal Schwartz' } }, shift } sub parameters { bless $_[0]->{'params'}, ref($_[0]) } sub user{ $_[0]->{'user'} = $_[1] if defined $_[1]; $_[0]->{'user'} } __DATA__ $VAR1 = bless( { 'params' => { 'user' => 'Randal Schwartz' } }, 'Bad::Design' ); Randal Schwartz Matt Wright

cheers

tachyon


In reply to Re: Capturing Method Call, And Relaying. by tachyon
in thread Capturing Method Call, And Relaying. by Revelation

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.