If modifying the content is something you often do, it would be kind of cool to have the set method take a block of code and act internally:
$self->content(sub{s/foo/bar/g});
where the content method would recognize the code ref and treat the current value as $_ within it. Something vaguely like:
sub content {
my $self = shift;
if (@_) {
my $set = shift;
if (isa($set,"CODE")) {
# fixed :-)
&$set for $self->{'content'}; # Code to modify content (as
+ $_) gets executed
}
else {
$self->{'content'} = $set; # Direct set
}
}
$self->{'content'};
}
Another spiffy (but experimental) technique would be to make the content method
an lvalue subroutine. So you could write the one-liner
$self->content =~ s/foo/bar/g;
# instead of
# $self->content(map { s/foo/bar/g } map $_, $self->content);
We're not really tightening our belts, it just feels that way because we're getting fatter.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.