melange
melange copied to clipboard
diverse-project
The Melange Language Workbench
curently the projet that contains the extended metamodel runtime code use the following pattern ExtendedRuntime for the project however, such project usually use a more complex naming scheme with for...
Currently, Melange's compiler generates (among others) a Java file for each metamodel and a Java file for each of its metaclass, in the same package. If a metamodel and one...
Inheritance differs from merge operator by enforcing the subtyping relation between the sub-metamodel and its super-metamodel. However, subtyping can be broken e.g. if new mandatory references are inserted in the...
Split from #7 Name-based structural typing works well for evolution. However, mapping independently developed DSLs rarely works out-of-the-box. Melange should support adaptation specification, at least through renaming, ideally with advanced...
Second step for #7 Name-based structural typing works well for evolution. However, mapping independently developed DSLs rarely works out-of-the-box. Melange should support adaptation specification, at least through renaming, ideally with...
(split from #7) Name-based structural typing works well for evolution. However, mapping independently developed DSLs rarely works out-of-the-box. Melange should support adaptation specification, at least through renaming, ideally with advanced...
There is currently two ways to define a model type. Either by extracting the exact type of an existing metamodel: ``` metamodel X { ecore "..." exactType XMT //
Multiple inheritance should be supported with a well-defined semantics (e.g. no conflict or left/right-linearization): ``` metamodel X { ... } metamodel Y { ... } metamodel Z { ... }...