As others said, I'd rather preferre a simple object to a tie.
In your case it (yet) seems sufficient to bless a scalar ref instead of a hash ref. So you can fetch and store your link with $$ dereferencing.
Of course this doesn't scale well when your object needs more data...
Then lvalue mutators maybe a handy alternative... but to validate the stored links you need again a tie on the data, see Re: A tale about accessors, lvalues and ties
#!/usr/bin/perl
use strict;
use warnings;
$\="\n";
{
package LinkClass;
sub new {
my $scalar="link";
my $self=\$scalar;
bless $self;
return $self;
}
sub print {print ${$_[0]}}
sub url :lvalue { ${$_[0]} }
}
my $obj=LinkClass->new();
$obj->print();
$$obj="link2";
$obj->print();
$obj->url="link3";
$obj->print();
__END__
link
link2
link3
a completely other approach maybe
using a wrapper write(), which calls tied($var)->print_method; like Arunbear suggested.
write($var);
write() could be automatically imported with your Linkpackage...
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|