Skip to content
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

tokens not introducing keyword rules in lexer? #20

Closed
parrt opened this issue Feb 18, 2012 · 1 comment
Closed

tokens not introducing keyword rules in lexer? #20

parrt opened this issue Feb 18, 2012 · 1 comment

Comments

@parrt
Copy link
Member

parrt commented Feb 18, 2012

the lexer wouldn't match correctly and would cast them all as id tokens

    tokens { TRUE='true'; FALSE='false'; TYPE_BOOL='boolean'; TYPE_VOID='void'; TYPE_INT='int';
             TYPE_FLOAT='float'; TYPE_CHAR='char';}

    primitiveType
      returns [CymbolProperties props]
      @init{$primitiveType.props = new CymbolProperties();}
      : 'float'
      | 'int'
      | 'char'
      | 'boolean
      | 'void'
      ;
@sharwell
Copy link
Member

Closing since the tokens{} block can no longer be used in this manner.

parrt pushed a commit that referenced this issue Jun 30, 2015
parrt pushed a commit that referenced this issue Jun 30, 2015
remove unnecessary getSerializedATNSegmentLimit
this should have been removed when Target became a full fledged class
BurtHarris pushed a commit to BurtHarris/antlr4 that referenced this issue Sep 28, 2016
parrt pushed a commit that referenced this issue Nov 7, 2016
Added to contributors.txt
@ericvergnaud ericvergnaud mentioned this issue Nov 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants