Eclipse Community Forums: TMF (Xtext) » Scope provider stops working with UPPER_CASE

Home » Modeling » TMF (Xtext) » Scope provider stops working with UPPER_CASE_ID terminal rule

Scope provider stops working with UPPER_CASE_ID terminal rule [message #1016159]

Tue, 05 March 2013 05:01

Eclipse User

Hi,
I have two DSL's below. In the Entity DSL, if I change the Attribute rule to [0], the scope provider in the Function DSL stops returning me the list of Entity attributes. Is there a way I could fix this ? I am going through the implementation of the Scopes class, but so far I haven't found a solution. Any thoughts ?

[0]
Attribute:
name=UPPER_CASE_ID ':' type=DataType

-------------------Function DSL------------------------------------------------------
....
....
Function:
'func' name=ID '('parameters+=Parameter (',' parameters+=Parameter)* ')' '{'
body += Body (';' body += Body)*
'}'
;

Body:
object=[Parameter] tail=AttributeReference?
;

Parameter:
name=ID ':' type=[entity::Entity]
;

AttributeReference:
'.' attribute=[entity::Attribute]
;

---------------------------Entity DSL------------------------------------------------
....
....
Attribute:
name=ID ':' type=DataType

terminal UPPER_CASE_ID : '^'?('A'..'Z'|'_') ('A'..'Z'|'_'|'0'..'9')*;

-------------------------------------------------------------------------------------

Thanks in advance,

[Updated on: Tue, 05 March 2013 05:03] by Moderator

Re: Scope provider stops working with UPPER_CASE_ID terminal rule [message #1016264 is a reply to message #1016159]

Tue, 05 March 2013 12:53

Eclipse User

Hi,

cannot reproduce that. maybe cause some parts of the grammar are missing
never the less there are 2 potential pitfalls.

(1) your UPPER_CASE_ID may collide with ID - dont know if this i a problem in your case - and do you use it in both grammars?
(2) xxx=[Type] is short for xx=[Type|ID] which tells the parser to parse an ID
depending on your solution to (1) you may have to write xx=[Type|UPPER_CASE_ID] instead

Re: Scope provider stops working with UPPER_CASE_ID terminal rule [message #1016845 is a reply to message #1016159]

Thu, 07 March 2013 16:15

Eclipse User

Hi Christian,
Thanks for the reply. Yes, the grammar is incomplete. I had posted only the relevant parts of it.

1) I am aware that the UPPER_CASE_ID rule shadows/collides with the ID rule in some cases. For example, in the above dsl, if I was to define function name with all upper case, I would see the error - mismatched input 'FUNTIONFOO' expecting RULE_ID. Out of curiosity, is there a way we could fix this issue ?

2) xx=[Type|UPPER_CASE_ID] worked.

Thanks for the help.

[Updated on: Thu, 07 March 2013 16:16] by Moderator

Re: Scope provider stops working with UPPER_CASE_ID terminal rule [message #1016851 is a reply to message #1016845]

Thu, 07 March 2013 16:47

Eclipse User

Hi,

what about to put the upper case thing not into the grammar but into semantic validation?

Previous Topic:	dot as separator in rule with hidden white spaces
Next Topic:	Couldn't resolve reference to Type

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 26 15:32:32 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter