Eclipse Community Forums: TMF (Xtext) » Wrong type binary rule's member

Help

Home

Home » Modeling » TMF (Xtext) » Wrong type binary rule's member

Show: Today's Messages :: Show Polls :: Message Navigator

Wrong type binary rule's member [message #900632]

Tue, 07 August 2012 17:04

Dobes Vandermeer
Messages: 26
Registered: July 2009

Junior Member

I have a rule like this:

Factor: Unary ({FactorOp.left=current} dotOp=("." | "*.") ("[" index=Expr? (range?='to' rangeEnd=Expr)? "]" | member=Name))*;

The problem is that the class generated for this (FactorOp) infers that the type of FactorOp.left will be Unary whereas it may be Unary or another FactorOp if these are chained.

How can I tell Xtext to declare the type of FactorOp.left as Factor or some other common base class of Unary and Factor?

Report message to a moderator

Re: Wrong type binary rule's member [message #900640 is a reply to message #900632]

Tue, 07 August 2012 17:53

Dobes Vandermeer
Messages: 26
Registered: July 2009

Junior Member

This typing problem also seems to apply to any left-associative operator. For example when I define a rule :

ImpliesCondition: LogicalOr ({BinaryOp.left=current} =>op=('implies' | '\\implies') right=LogicalOr )*;

The resulting class "BinaryOp" has both left and right with type "LogicalOr" which means it cannot be recursive and have an ImpliesCondition on the left.

For the binary operators I think I can workaround it by using rules like:

ImpliesCondition: LogicalOr ({BinaryOp.left=current} =>op=('implies' | '\\implies') right=ImpliesCondition)?;

But I'm still pondering how to do that for my "Factor" rule above, and I'm not sure these rules should really be right-associative.

Report message to a moderator

Re: Wrong type binary rule's member [message #900642 is a reply to message #900640]

Tue, 07 August 2012 18:06

Dobes Vandermeer
Messages: 26
Registered: July 2009

Junior Member

Note this style of left-associative operators came from

http colon //blog.efftinge.de/2010/08/parsing-expressions-with-xtext.html

The Online Help doesn't seem to have any examples of left-associative operators at the moment.

Report message to a moderator

Re: Wrong type binary rule's member [message #900643 is a reply to message #900642]

Tue, 07 August 2012 18:15

Dobes Vandermeer
Messages: 26
Registered: July 2009

Junior Member

OK I looked at the Arithmetic example.

Turns out not so much a case of RTFM but check out the examples ...

I need to put "returns Expr" for all of the related rules, then it'll use Expr as the field type and clean up the type hierarchy.

Report message to a moderator

Previous Topic:	Documentation for "new" serializer?
Next Topic:	How does the Serializer work? Reg. NFA + NodeModel

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed May 22 16:57:35 EDT 2013