Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 347304

Summary: Specifying super types with only alternative break EAttribute inheritance
Product: [Modeling] TMF Reporter: Florian Philipp <eclipse>
Component: XtextAssignee: Project Inbox <tmf.xtext-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: minor    
Priority: P3 CC: sebastian.zarnekow
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Florian Philipp CLA 2011-05-26 08:39:22 EDT 
Build Identifier: M20100909-0800

Consider the following grammar:
SuperType: TypeA | TypeB;

TypeA: SubTypeA1 | SubTypeA2;
SubTypeA1: name='A1';
SubTypeA2: name='A2';

TypeB: SubTypeB;
SubTypeB: name='B';

In this case, neither TypeB nor SuperType will contain a name attribute in the generated source code. Adding a second alternative to TypeB or removing TypeB and adding SubTypeB directly to the alternatives of SuperType resolves this issue and adds name to SuperType.

Reproducible: Always
Comment 1 Sebastian Zarnekow CLA 2011-05-26 09:23:25 EDT 
This works as specified. The attributes will be pulled up if there is more than one subtype and all subtypes have the attribute in common. That condition does not hold for TypeB which has not a 'name' attribute.

Consider the following simplified example:

Type: SubType | {Type} 'keyword';
SubType: someAttribute=ID;

If we reduce the constraints that mark attributes as 'to-be-pulled-up', all attributes would end up in the most abstract super type. That's usually not what you'ld expect.

In general I'd recommend to switch to imported metamodels as soon as your grammar is settled or the meta model inference does not do what you want. 

Please reopen if I missed a point.
Comment 2 Karsten Thoms CLA 2017-09-19 17:12:06 EDT 
Closing all bugs that were set to RESOLVED before Neon.0
Comment 3 Karsten Thoms CLA 2017-09-19 17:23:34 EDT 
Closing all bugs that were set to RESOLVED before Neon.0