ANTLR4 Swift grammar cannot identify a for-in statement
up vote
0
down vote
favorite
I am using ANTLR4 to parse Swift code using the Swift grammar (or at least based on it) from GitHub. The parser does not identify the for-in statement as a loop statement / for-in statement even if it was defined in the grammar. I am trying to understand why.
Thanks,
Roy
I am attaching these files via OneDrive:
GameScene.swift
Swift.g4
java swift eclipse antlr4
edited Nov 10 at 19:43
Austin Conlon
86212
asked Nov 9 at 23:52
roywax
3516
add a comment |
up vote
0
down vote
favorite
I am using ANTLR4 to parse Swift code using the Swift grammar (or at least based on it) from GitHub. The parser does not identify the for-in statement as a loop statement / for-in statement even if it was defined in the grammar. I am trying to understand why.
Thanks,
Roy
I am attaching these files via OneDrive:
GameScene.swift
Swift.g4
java swift eclipse antlr4
edited Nov 10 at 19:43
Austin Conlon
86212
asked Nov 9 at 23:52
roywax
3516
Just a glance, but your grammar cannot distinguishtrailing_closureandcode_block.
– OOPer
Nov 10 at 5:02
Well, it did in other unit and i use this recognition of both trailing_closure and code_block so i guess that isn't the issue. In this case it doesn't recognize the for-in as a loop statement but instead as an expression or binary expression.
– roywax
Nov 10 at 20:47
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am using ANTLR4 to parse Swift code using the Swift grammar (or at least based on it) from GitHub. The parser does not identify the for-in statement as a loop statement / for-in statement even if it was defined in the grammar. I am trying to understand why.
Thanks,
Roy
I am attaching these files via OneDrive:
GameScene.swift
Swift.g4
java swift eclipse antlr4
edited Nov 10 at 19:43
Austin Conlon
86212
asked Nov 9 at 23:52
roywax
3516
I am using ANTLR4 to parse Swift code using the Swift grammar (or at least based on it) from GitHub. The parser does not identify the for-in statement as a loop statement / for-in statement even if it was defined in the grammar. I am trying to understand why.
Thanks,
Roy
I am attaching these files via OneDrive:
GameScene.swift
Swift.g4
java swift eclipse antlr4
java swift eclipse antlr4
edited Nov 10 at 19:43
Austin Conlon
86212
asked Nov 9 at 23:52
roywax
3516
edited Nov 10 at 19:43
Austin Conlon
86212
asked Nov 9 at 23:52
roywax
3516
edited Nov 10 at 19:43
Austin Conlon
86212
edited Nov 10 at 19:43
Austin Conlon
86212
edited Nov 10 at 19:43
Austin Conlon
86212
86212
asked Nov 9 at 23:52
roywax
3516
asked Nov 9 at 23:52
roywax
3516
asked Nov 9 at 23:52
roywax
3516
3516
Just a glance, but your grammar cannot distinguishtrailing_closureandcode_block.
– OOPer
Nov 10 at 5:02
Well, it did in other unit and i use this recognition of both trailing_closure and code_block so i guess that isn't the issue. In this case it doesn't recognize the for-in as a loop statement but instead as an expression or binary expression.
– roywax
Nov 10 at 20:47
add a comment |
Just a glance, but your grammar cannot distinguishtrailing_closureandcode_block.
– OOPer
Nov 10 at 5:02
Well, it did in other unit and i use this recognition of both trailing_closure and code_block so i guess that isn't the issue. In this case it doesn't recognize the for-in as a loop statement but instead as an expression or binary expression.
– roywax
Nov 10 at 20:47
Just a glance, but your grammar cannot distinguish
trailing_closure and code_block.– OOPer
Nov 10 at 5:02
Just a glance, but your grammar cannot distinguish
trailing_closure and code_block.– OOPer
Nov 10 at 5:02
Well, it did in other unit and i use this recognition of both trailing_closure and code_block so i guess that isn't the issue. In this case it doesn't recognize the for-in as a loop statement but instead as an expression or binary expression.
– roywax
Nov 10 at 20:47
Well, it did in other unit and i use this recognition of both trailing_closure and code_block so i guess that isn't the issue. In this case it doesn't recognize the for-in as a loop statement but instead as an expression or binary expression.
– roywax
Nov 10 at 20:47
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
OOPer, upon further investigating i did found out the problem was that the parser was wrongly identifying the 'for' as a variable / regular identifier.
So, i looked in GitHub swift grammar that they indeed separated the identifier to 2 types to avoid such things.
After i did that, the parser identified the for loop statement correctly...
Thanks
Bye
answered Nov 13 at 15:18
roywax
3516
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
OOPer, upon further investigating i did found out the problem was that the parser was wrongly identifying the 'for' as a variable / regular identifier.
So, i looked in GitHub swift grammar that they indeed separated the identifier to 2 types to avoid such things.
After i did that, the parser identified the for loop statement correctly...
Thanks
Bye
answered Nov 13 at 15:18
roywax
3516
add a comment |
up vote
0
down vote
OOPer, upon further investigating i did found out the problem was that the parser was wrongly identifying the 'for' as a variable / regular identifier.
So, i looked in GitHub swift grammar that they indeed separated the identifier to 2 types to avoid such things.
After i did that, the parser identified the for loop statement correctly...
Thanks
Bye
answered Nov 13 at 15:18
roywax
3516
add a comment |
up vote
0
down vote
up vote
0
down vote
OOPer, upon further investigating i did found out the problem was that the parser was wrongly identifying the 'for' as a variable / regular identifier.
So, i looked in GitHub swift grammar that they indeed separated the identifier to 2 types to avoid such things.
After i did that, the parser identified the for loop statement correctly...
Thanks
Bye
answered Nov 13 at 15:18
roywax
3516
OOPer, upon further investigating i did found out the problem was that the parser was wrongly identifying the 'for' as a variable / regular identifier.
So, i looked in GitHub swift grammar that they indeed separated the identifier to 2 types to avoid such things.
After i did that, the parser identified the for loop statement correctly...
Thanks
Bye
answered Nov 13 at 15:18
roywax
3516
answered Nov 13 at 15:18
roywax
3516
answered Nov 13 at 15:18
roywax
3516
answered Nov 13 at 15:18
roywax
3516
3516
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53234728%2fantlr4-swift-grammar-cannot-identify-a-for-in-statement%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Just a glance, but your grammar cannot distinguish
trailing_closureandcode_block.– OOPer
Nov 10 at 5:02
Well, it did in other unit and i use this recognition of both trailing_closure and code_block so i guess that isn't the issue. In this case it doesn't recognize the for-in as a loop statement but instead as an expression or binary expression.
– roywax
Nov 10 at 20:47