IMHO it's not state which is buggy but rather map.
see this
DB<168> sub tst (&@) { my $cr=shift; print $cr->($_)," " for @_ }
DB<169> use feature 'state'; tst {state $i++} 1..3 for 1..3
=> ""
0 1 2 0 1 2 0 1 2
The blocks of map and grep are no anonymous subroutines as Tobyink pointed out recently.
IMHO thats why scoping fails in your tests.
DB<173> use feature 'state'; map {state $i++; print "$i "} 1..3 for
+1..3
=> ""
1 2 3 4 5 6 7 8 9
(at least with 5.10)
udate
also while conditions
DB<195> use feature 'state'; for (1..3) { $y=0;while (++(my $x)) { p
+rint " $x .";last if $y++>3 } }
=> ""
1 . 1 . 1 . 1 . 1 . 1 . 1 . 1 . 1 . 1 . 1 . 1 . 1 . 1 . 1 .
DB<196> use feature 'state'; for (1..3) { $y=0;while (++(state $x))
+{ print " $x .";last if $y++>3 } }
=> ""
1 . 2 . 3 . 4 . 5 . 6 . 7 . 8 . 9 . 10 . 11 . 12 . 13 . 14 . 15 .
Cheers Rolf
( addicted to the Perl Programming Language)
-
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.
|