Here's much the same thing, but using a closure. I'm sure
this will slow down the process but can improve the usage of
it by seperating the buffer from the rest of the code, and
allowing easy reuse - and multiple buffers if desired - without needing to intersperse your code
in amoungst other processing. It's
a matter of tradeoffs, but I'm not sure on how much slower
it will be.
my $buf = make_buf(3);
&$buf('hi');
&$buf('moo');
print join(' ', &$buf) . "\n"; # 'hi moo'
$buf->('foo','no');
print join(' ', $buf->()) . "\n"; # 'moo foo no'
sub make_buf {
my $size = shift || 3;
my @buf;
my $pos = -1;
my $last = $size - 1;
return sub {
if (@_) {
while (@_) { $buf[ $pos==$last ? $pos=0 : ++$pos ] = shift
+ }
}
elsif (wantarray) {
return ($#buf==$last ? @buf[ $pos+1 .. $last, 0 .. $pos ]
+: @buf);
}
else { warn "Call with an argument or in list context"; return
+; }
}
}
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.