You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that we have other technology specific examples, (such as K3FSM) we now should rename the LegacyFSM in something clearer.
If the example mimics code reuse of a "legacy" language as a general concerns, this name doesn't help to understand implied technologies and how the languages are built.
This is actually an example of use of GEMOC with Melange+K3 in order create 2 languages that inherits one from another (thus enabling model conversion, editor code reuse, etc)
my suggestion: MelangeK3FSM
other suggestions are welcome for a better name... 😉
The text was updated successfully, but these errors were encountered:
Now that we have other technology specific examples, (such as K3FSM) we now should rename the LegacyFSM in something clearer.
If the example mimics code reuse of a "legacy" language as a general concerns, this name doesn't help to understand implied technologies and how the languages are built.
This is actually an example of use of GEMOC with Melange+K3 in order create 2 languages that inherits one from another (thus enabling model conversion, editor code reuse, etc)
my suggestion: MelangeK3FSM
other suggestions are welcome for a better name... 😉
The text was updated successfully, but these errors were encountered: