From @masak

<diakopter> rakudo​: say 1 if 2 if 3 { say 3 }
<p6eval> rakudo e6863e​: OUTPUT«1␤3␤»
<jnthn> o_O
<diakopter> o!O
<diakopter> rakudo​: say 1 if 0 if 1 { say 3 } # masak
<p6eval> rakudo e6863e​: OUTPUT«3␤»
* masak submits rakudobug

Judging from the outputs above, it seems like Rakudo hallucinates a
semicolon, creating 'say 1 if 2; if 3 { say 3 }' and 'say 1 if 0; if 3
{ say 3 }', respectively.

This currently seems to be a parsing bug in STD also.

<diakopter> std​: say 1 if 2 if 3 { say 3 }
<p6eval> std 30732​: OUTPUT«ok 00​:01 111m␤»
<masak> o.O
<jnthn> Well, at least we're consistent.
<jnthn> (with STD)
<jnthn> :-)

@coke - Status changed from 'new' to 'open'

From @diakopter

On Thu May 20 15​:50​:01 2010, masak wrote​:

This currently seems to be a parsing bug in STD also.

FYI, now STD DTRT​:

14​:14 < diakopter> std​: say 1 if 2 if 3 { say 3 }
14​:14 <+p6eval> std f179a1b​: OUTPUT«Use of uninitialized value $x in
pattern match (m//) at
  STD.pm line 66577.␤Use of uninitialized value $x in
concatenation (.) or
  string at STD.pm line 66616.␤===SORRY!===␤Missing
semicolon at
  /tmp/2yh3PPJvek line 1​:␤------> say 1 if 2⏏[31…

From @coke

On Tue May 29 12​:15​:49 2012, diakopter wrote​:

On Thu May 20 15​:50​:01 2010, masak wrote​:

This currently seems to be a parsing bug in STD also.

FYI, now STD DTRT​:

14​:14 < diakopter> std​: say 1 if 2 if 3 { say 3 }
14​:14 <+p6eval> std f179a1b​: OUTPUT«Use of uninitialized value $x in
pattern match (m//) at
STD.pm line 66577.␤Use of uninitialized value $x in
concatenation (.) or
string at STD.pm line 66616.␤===SORRY!===␤Missing
semicolon at
/tmp/2yh3PPJvek line 1​:␤------> say 1 if 2⏏[31…

STD changed for the better​:

20​:17 < [Coke]> std​: say 1 if 2 if 3 { say 3 }
20​:17 <+camelia> std 09dda5b​: OUTPUT«===SORRY!===␤Missing semicolon at
  /tmp/Ht45Fl9DU1 line 1​:␤------> say 1 if 2⏏ if 3 { say 3
  }␤Parse failed␤FAILED 00​:01 123m␤»

Rakudo is correctly failing.

20​:18 < [Coke]> m​: say 1 if 2 if 3 { say 3 }
20​:18 <+camelia> rakudo-moar b2b333​: OUTPUT«===SORRY!=== Error while compiling
  /tmp/EjEL_Q5O1j␤Confused␤at /tmp/EjEL_Q5O1j​:1␤------> say 1 if
  2 ⏏if 3 { say 3 }␤ expecting any of​:␤ postfix␤»

The error is not the same as STD's, but I think it's good enough - closable with tests.
--
Will "Coke" Coleda

From @peschwa

On Sat Feb 22 17​:20​:15 2014, coke wrote​:

On Tue May 29 12​:15​:49 2012, diakopter wrote​:

On Thu May 20 15​:50​:01 2010, masak wrote​:

This currently seems to be a parsing bug in STD also.

FYI, now STD DTRT​:

14​:14 < diakopter> std​: say 1 if 2 if 3 { say 3 }
14​:14 <+p6eval> std f179a1b​: OUTPUT«Use of uninitialized value $x in
pattern match (m//) at
STD.pm line 66577.␤Use of uninitialized value $x in
concatenation (.) or
string at STD.pm line 66616.␤===SORRY!===␤Missing
semicolon at
/tmp/2yh3PPJvek line 1​:␤------> say 1 if 2⏏[31…

STD changed for the better​:

20​:17 < [Coke]> std​: say 1 if 2 if 3 { say 3 }
20​:17 <+camelia> std 09dda5b​: OUTPUT«===SORRY!===␤Missing semicolon at
/tmp/Ht45Fl9DU1 line 1​:␤------> say 1 if 2⏏ if 3 {
say 3
}␤Parse failed␤FAILED 00​:01 123m␤»

Rakudo is correctly failing.

20​:18 < [Coke]> m​: say 1 if 2 if 3 { say 3 }
20​:18 <+camelia> rakudo-moar b2b333​: OUTPUT«===SORRY!=== Error while
compiling
/tmp/EjEL_Q5O1j␤Confused␤at /tmp/EjEL_Q5O1j​:1␤------>
say 1 if
2 ⏏if 3 { say 3 }␤ expecting any of​:␤
postfix␤»

The error is not the same as STD's, but I think it's good enough -
closable with tests.

Added a test to roast in commit feeea52 as per the example above.

From @peschwa

On Sun Jul 20 01​:12​:18 2014, peschwa@​gmail.com wrote​:

On Sat Feb 22 17​:20​:15 2014, coke wrote​:

On Tue May 29 12​:15​:49 2012, diakopter wrote​:

On Thu May 20 15​:50​:01 2010, masak wrote​:

This currently seems to be a parsing bug in STD also.

FYI, now STD DTRT​:

14​:14 < diakopter> std​: say 1 if 2 if 3 { say 3 }
14​:14 <+p6eval> std f179a1b​: OUTPUT«Use of uninitialized value $x in
pattern match (m//) at
STD.pm line 66577.␤Use of uninitialized value $x in
concatenation (.) or
string at STD.pm line 66616.␤===SORRY!===␤Missing
semicolon at
/tmp/2yh3PPJvek line 1​:␤------> say 1 if 2⏏[31…

STD changed for the better​:

20​:17 < [Coke]> std​: say 1 if 2 if 3 { say 3 }
20​:17 <+camelia> std 09dda5b​: OUTPUT«===SORRY!===␤Missing semicolon at
/tmp/Ht45Fl9DU1 line 1​:␤------> say 1 if 2⏏ if 3 {
say 3
}␤Parse failed␤FAILED 00​:01 123m␤»

Rakudo is correctly failing.

20​:18 < [Coke]> m​: say 1 if 2 if 3 { say 3 }
20​:18 <+camelia> rakudo-moar b2b333​: OUTPUT«===SORRY!=== Error while
compiling
/tmp/EjEL_Q5O1j␤Confused␤at /tmp/EjEL_Q5O1j​:1␤------>
say 1 if
2 ⏏if 3 { say 3 }␤ expecting any of​:␤
postfix␤»

The error is not the same as STD's, but I think it's good enough -
closable with tests.

Added a test to roast in commit feeea52 as per the example above.

To add to that​: [0] makes the .reason of the thrown X​::Syntax​::Confused match the one that STD gives. Spectest looks clean, but I'm not sure if there might be untested cases where the message could be misleading.

[0] rakudo/rakudo#291

From @FROGGS

PR merged​: rakudo/rakudo@9a9f357fea
Test got adjusted​: Raku/roast@6811e5268e
psch++

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