Eclipse Community Forums: TMF (Xtext) » How does the XVariableDeclaration rule result in an ecore class that extends JvmIdentifiableElement?

Home » Modeling » TMF (Xtext) » How does the XVariableDeclaration rule result in an ecore class that extends JvmIdentifiableElement?

How does the XVariableDeclaration rule result in an ecore class that extends JvmIdentifiableElement? [message #1800705]

Sun, 06 January 2019 09:46

Eclipse User

Hello,

I'm trying to understand how the xbase rule XVariableDeclaration results in an ecore class that derives from the xtext common type JvmIdentifiableElement.

I can't see anything in the way the XVariableDeclaration rule is written that would trigger this result.

Where does the logic reside that causes XVariableDeclaration to extend JvmIdentifiableElement? Is it in the xbase grammar or some other part of xbase?

Thank you in advance,
Jay

Re: How does the XVariableDeclaration rule result in an ecore class that extends JvmIdentifiableElem [message #1800748 is a reply to message #1800705]

Mon, 07 January 2019 14:10

Eclipse User

Xbase uses a manually written metamodel, not an inferred one

Previous Topic:	Error in entering an ID having the same name as a keyword
Next Topic:	Couldn't resolve reference to PanelType 'NavigationBar'

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Jul 21 09:19:07 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter