From @masak

Rakudo r34064 doesn't allow two spaces between 'say' and 'for' in this
one-liner​:

$ ./perl6 -e 'say for 1'
Could not find non-existent sub for
[...]

From @moritz

# New Ticket Created by "Carl Mäsak"
# Please include the string​: [perl #​61494]
# in the subject line of all future correspondence about this issue.
# <URL​: http://rt.perl.org/rt3/Ticket/Display.html?id=61494 >

Rakudo r34064 doesn't allow two spaces between 'say' and 'for' in this
one-liner​:

$ ./perl6 -e 'say for 1'
Could not find non-existent sub for

Actually I think that's the correct parse, because say() expects an
argument list, so a bare 'for' has to be a sub call. It only parses 'for
1' as a statement modifying loop where an operator is expected.

I'd argue that the parse of 'say for 1' (with only one whitespace) is
incorrect. In case of doubt, ask STD.pm.

Cheers,
Moritz

The RT System itself - Status changed from 'new' to 'open'

From @TimToady

On Fri, Dec 19, 2008 at 10​:04​:34AM +0100, moritz@​casella.faui2k3.org wrote​:
: > # New Ticket Created by "Carl Mäsak"
: > # Please include the string​: [perl #​61494]
: > # in the subject line of all future correspondence about this issue.
: > # <URL​: http://rt.perl.org/rt3/Ticket/Display.html?id=61494 >
: >
: >
: > Rakudo r34064 doesn't allow two spaces between 'say' and 'for' in this
: > one-liner​:
: >
: > $ ./perl6 -e 'say for 1'
: > Could not find non-existent sub for
:
: Actually I think that's the correct parse, because say() expects an
: argument list, so a bare 'for' has to be a sub call. It only parses 'for
: 1' as a statement modifying loop where an operator is expected.
:
: I'd argue that the parse of 'say for 1' (with only one whitespace) is
: incorrect. In case of doubt, ask STD.pm.

STD considers modifiers to be terminators, so 'for' will never be
interpreted as a listop. I just fixed STD so that 'say for()' lets
you call the for() function, however.

Larry

From @kyleha

This is an automatically generated mail to inform you that tests are now available in b/t/spec/S04-statement-modifiers/for.t

From @masak

This particular parsefail doesn't occur anymore in ng. Resolving ticket.

@masak - Status changed from 'open' to 'resolved'