Open ebousse opened 7 years ago
Also a quick note, the renaming
is used as a workaround to two bugs that occur when no renaming
is used to merge both packages into a single one:
Symbol
is generated twice in both packages of the language runtime (miniJava
and minijavadynamicdata
)miniJava
and minijavadynamicdata
)So in fact it would also be great to have this example work without the use of renaming
.
"Works for me" :(. I can successfully generate everything (runtime language, adapters, interfaces, etc.).
I'm working outside GEMOC: Eclipse Modeling + latest Melange.
Could you please try to update to the latest version of Melange in your GEMOC installation and report back?
OK, I confirm that is now works well with master
, for some reason. Thanks all!
However, I still have several errors when I remove the renaming
in the melange file, due to the Eclass Symbol
being generated twice for some reason (one per EPackage).
Originally it only exists in the miniJava
epackage, in the abstract syntax:
But after running Generate All, it can be found in both resulting epackages:
If you want I can create a separate issue for this problem, but it's up to you.
I feel bad for opening an issue for a very unprecise and not well identified problem, but here I go...
I am working on a MiniJava language, available here: https://github.com/tetrabox/minijava
Most importantly, it contains:
org.tetrabox.minijava.xtext
: a grammar-first xtext project, which generates the abstract syntaxorg.tetrabox.minijava.semantics.modelstate
: an additional metamodel that defines the execution state of a minijava programorg.tetrabox.minijava.semantics
: semantics written only with K3 aspects (no new classes, no static classes)org.tetrabox.minijava.dsl
: the melange project, with the following melange file:language XMiniJava inherits MiniJava {
}