Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Talk:Papyrus/CodeGenerationAndDeployment"
(don't spray language in several layers; use one layer for each language.) |
|||
| Line 23: | Line 23: | ||
Cedric | Cedric | ||
| + | |||
| + | |||
| + | Hi Cedric, | ||
| + | I updated the proposal on the main page, much more aligned with your's now | ||
| + | |||
| + | Ansgar | ||
Latest revision as of 11:30, 22 January 2016
Can we express what are the requirements and what are our goals ?
For my point of view, I prefer to have all stuff related to a language under a layer dedicated to this language, rather than having it sprayed under different layers.
There is several reasons : - When we will add new languages, we have only to add the corresponding layer - Language will be more easily plug and play (like diagrams and other papyrus stuff) - Language will be more independent one from the other. Common stuff can be put in a shared layers
So the proposal could be :
- language.common - all common stuff -- language.common.xxx - one sublayers for each important category - language.java - all things related to java -- language.java.generator -- language.java.reverse -- language.java.profile -- language.java.xxx - language.cpp - all things related to c++ -- language.cpp.generator -- language.cpp.reverse -- language.cpp.profile -- language.cpp.xxx - ...
Cedric
Hi Cedric,
I updated the proposal on the main page, much more aligned with your's now
Ansgar