-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typechecker not called on GEMOC official example #26
Comments
Actually, what are the correct keys to be used in the dsl file ? the ALE example uses:
and the GEMOC ALE example uses:
for the same information syntax/behavior allows to have some type-checking in the ale editor, and ecore/ale allows to start the GEMOC ALE engine 🤔 |
Need to harmonize the keys of the dsl file: one purpose = one keyword |
Decision: must change to |
Same issue here: when using ALE in GEMOC (with TFSM official example) I have no auto-completion and it can barely detect any error. And I tried to make a tiny group of students code an interpreter in ALE in the GEMOC Studio, and they really struggled because of this :D |
the current workaround is to duplicate the key to use both ecore and syntax and tio use both ale and behavior (referencing the same files) |
…in .dsl files (fix #26) Because: - "ecore" and "ale" are the keys understood by the GEMOC Studio and using others make some ALE features unavailable Signed-off-by: Emmanuel Chebbi <emmanuel.chebbi@outlook.fr>
…in .dsl files (fix #26) Because: - "ecore" and "ale" are the keys understood by the GEMOC Studio and using others make some ALE features unavailable Signed-off-by: Emmanuel Chebbi <emmanuel.chebbi@outlook.fr>
when installing the GEMOC ALE official example I was expecting it to be configured as a nominal configuration and to be able to raise typechecking errors
but introducing errors in the ALE code does not raise any error. (both trying to change Ecore attribute or local attribte for example)
might be related to #4
note: using current ale distributed with GEMOC
The text was updated successfully, but these errors were encountered: