Re: [perl #57960] Inconsistent for loop semantics

2008-08-18 Thread Patrick R. Michaud
Now resolved in r32094. Some specific notes below: On Mon, Aug 18, 2008 at 03:39:18AM -0500, Patrick R. Michaud wrote: > On Fri, Aug 15, 2008 at 11:15:46PM -0700, Carl Mäsak wrote: > > r30258: > > $ ./perl6 -e '.say for [1,2,3]' # as expected > > 1 > > 2 > > 3 > > This one is actually incorrect

Re: [perl #57960] Inconsistent for loop semantics

2008-08-18 Thread Patrick R. Michaud
On Fri, Aug 15, 2008 at 11:15:46PM -0700, Carl Mäsak wrote: > r30258: > $ ./perl6 -e '.say for [1,2,3]' # as expected > 1 > 2 > 3 This one is actually incorrect in Rakudo -- at least according to Pugs (and I agree with Pugs here). The correct output is "1 2 3\n". Rakudo's output is likely incor

Re: [perl #57960] Inconsistent for loop semantics

2008-08-17 Thread Carl Mäsak
It was revision 28928 that introduced this difference between the for statement and statement-modifying for. I'm not sure exactly what issue it intended to fix, but if I undo that revision everything works according to my (not necessarily correct) expectations. $ svn log -r28928 --

[perl #57960] Inconsistent for loop semantics

2008-08-16 Thread Carl Mäsak
# New Ticket Created by "Carl Mäsak" # Please include the string: [perl #57960] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=57960 > r30258: $ ./perl6 -e '.say for [1,2,3]' # as expected 1 2 3 $ ./perl6 -e 'for [1,2,3] {