New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An if statement isn't parsed correctly if it follows on a sub #234
Comments
From luben@unixsol.orgThere is some parse error for this simpe case: sub ok ($num){ for 1..5000 { The error message is : Statement not terminated properly at line 7, near "{ \n ok(" if we add some statement before the "for" it compiles. For example this is OK: ==code sub ok ($num){ Best regards |
From @masakr30183: From S04: =head1 Statement-ending blocks A line ending with a closing brace "C<}>", followed by nothing but my $x = sub { 3 } |
From @masakIf not actually a duplicate, then at least a close relative of #56228. |
@masak - Status changed from 'new' to 'open' |
From @chrisdolanI studied the solution employed by STD.pm for this. STD uses embedded endstmt = 0 (default) means we have not reached the end of a statement Those flags are set in <block>, <regex_block> and <stdstopper>. Statement modifiers are forbidden when endstmt == 2. |
The RT System itself - Status changed from 'new' to 'open' |
From slavikg@gmail.comif there is a grammar definition followed by an if statement, even if there grammar A { if ("blah" ~~ A) { slavik@slavik-desktop:~/code/perl6$ perl6 test.p6 current instr.: 'parrot;PGE;Util;die' pc 129 |
From @chrisdolanThis is a variation on "#56228: Perl6 grammar bug" which notices that a Could someone please mark this as duplicate and fix the subject line of |
The RT System itself - Status changed from 'new' to 'open' |
From dwhipp@nvidia.com(rakudo 34337) Strange parsing error: sub x { breaks: [[[ Statement not terminated properly at line 6, near "{\n If I add a semicolon after to sub decl, then it's happy: sub x { The strange thing is that it's only happening for "my" decls in the This email message is for the sole use of the intended recipient(s) and may contain |
From @pmichaudOn Wed Dec 24 07:38:04 2008, dwhipp@nvidia.com wrote:
This is the same problem as RT #57876 -- Rakudo currently sees a Pm |
The RT System itself - Status changed from 'new' to 'open' |
From @pmichaudOn Sun Jun 22 13:04:51 2008, karavelov wrote:
This is now fixed in 1e22a68, as well as the other cases where Thanks! Pm |
@pmichaud - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#57876 (status was 'resolved')
Searchable as RT57876$
The text was updated successfully, but these errors were encountered: