Eclipse Community Forums: TMF (Xtext) » difference terminals and datatypes

Home

Home » Modeling » TMF (Xtext) » difference terminals and datatypes

difference terminals and datatypes [message #1692515]

Thu, 16 April 2015 06:28

Eclipse User

Hi,
I am developing a language that has a part of its terminals and a rule like the below:

-------------------------------------------------------
terminal fragment BASIC_ID:
LETTER('_' | LETTER_OR_DIGIT)*
;
terminal fragment SPECIAL_ID:
GRAPHICS_CHAR | LC_LETTERS
;

terminal ID: BASIC_ID | SPECIAL_ID ;

terminal INTEGER :
DIGIT | DIGIT ('_'? DIGIT)+
;

time_rule:
INTEGER ID ;
--------------------------------------------------------
Now when I write 6000ns it gives an error while 6000 ns is not giving errors. I want to allow both cases (with/without) spaces.

Shall I change terminals to datatypes or vice versa? Any Help with that please.

Thanks

Re: difference terminals and datatypes [message #1692518 is a reply to message #1692515]

Thu, 16 April 2015 06:36

Eclipse User

Hi,

just some hints

- use as few terminals as possible
- do not use spaces in terminal

Re: difference terminals and datatypes [message #1692519 is a reply to message #1692518]

Thu, 16 April 2015 06:40

Eclipse User

you mean these terminals:

terminal WS:
(' ' | '\t' | '\r' | '\n')+
;

terminal SL_COMMENT:
'//' !('\n' | '\r')* ('\r'? '\n')?
;

terminal ML_COMMENT:
'/*'->'*/'
;

I am added them and set them as Hidden rules

Re: difference terminals and datatypes [message #1692522 is a reply to message #1692519]

Thu, 16 April 2015 06:43

Eclipse User

No other terminals you did not show

if the lexer recognizes 12345ns as a terminal it cannot be parsed as a datatype rule "firstterminal secondterminal"

Re: difference terminals and datatypes [message #1692526 is a reply to message #1692522]

Thu, 16 April 2015 06:58

Eclipse User

What should be defined as terminals and what should be defined as datatypes? Integers and letters for example?

Re: difference terminals and datatypes [message #1692527 is a reply to message #1692526]

Thu, 16 April 2015 07:03

Eclipse User

Hi,

this depends on your usecase

if you want to have 1234ns being parsed as two parts and 1234 ns beeing identified as two parts
you should not have a terminal rules that matches 1234ns but one that matches 1234 and another that matches ns (e.g. a keyword)

=> do the basic parts only as terminals and those who do not interfere e.g. strings comments etc

Re: difference terminals and datatypes [message #1692532 is a reply to message #1692527]

Thu, 16 April 2015 07:21

Eclipse User

The problem is solved but wherever I use the ns for example as a variable name it is highlighted and gives an error. I don't want it to be a keyword so I can use it in different places. the same issue with exponential numbers, the 'e' is always highlighted but I don't want it as a keyword in the same time I want specifically 'e' and not any other letter

Re: difference terminals and datatypes [message #1692533 is a reply to message #1692532]

Thu, 16 April 2015 07:23

Eclipse User

Hi,

if ns is a keyword or a terminal then it will be not ne recognized as an ID by the lexer anymore

=> you have to use a datatype rule for name names as well:

MyID : ID | "ns";

Variable:
"var" name=MyID;

Re: difference terminals and datatypes [message #1692534 is a reply to message #1692533]

Thu, 16 April 2015 07:24

Eclipse User

And if you dont want highlighting: have a look at semantic highlighting

Previous Topic:	Protected region support
Next Topic:	Extending the Xtext Generator

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 06 17:11:25 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter