| Xtend and XPand [message #723724] |
Fri, 09 September 2011 09:18  |
 Johnnyboy 
Messages: 39
Registered: September 2011 |
Member |
|
|
Hello everyone,
How are you? I (again) have a question concerning the both technologies Xtend2 (Xtext)/XPand2. I work for a software development department and for a professor - both parties have choosen Xtext for creating a grammar. But both do not know what tool to choose for code generation. Christian Dietrich said before that both are maintained and it is a matter of tast which tool to choose. Now I should find out which tool to choose for their tool chain. Uff. That is why I have the following questions.
1) Is it right that XTend2 is the sucessor of XPand2 which means that XPand2 will be maintained but not extended anymore (the professor said that he understood it that way)? And Xtend will contain all features of XPand2 in the future? And does that means that XPand2 will be dead after Xtend2 has all features of XPand?
2) What features are still missing in Xpand? Christian Dietrich named configurable outlets. (I do not really know what that is but to be honest I didn't read the whole XPAnd documentation.) What else? => The thing is that we want to decide for a tool on the basis of understandable arguments and then stick to the techology.
Thanks in advance for all answers
Jonnyboy
[Updated on: Fri, 09 September 2011 09:36] Report message to a moderator |
|
|
| Re: Xtend and XPand [message #723739 is a reply to message #723724] |
Fri, 09 September 2011 10:10  |
|
Hi,
since ive already wrote on this in the other post just a short remark: first of all you should write down the requirements you have for your code generation technology.
(1) yes it is a successor and xpand will probably not get "new" features. And Xtend2 will probably never get all features of Xpand. It is not a 1:1 replacement with all pros and cons
(2) There is AOP, customizable Metamodels, There is not yet that bunch of infrastructure (workflow components) that xpand already has.
But that is not Problem. For AOP there is Guice, A Workflowcomponent is easy to write yourself.
Think of things like Change/Stability / Tooling / Runtime Performance / Type Safty too.
But if you start from Scratch and have no special requirements why not choose the new Thing = Xtend(2)
~Christian
Twitter : @chrdietrich
Blog : https://www.dietrich-it.de
[Updated on: Fri, 09 September 2011 10:45] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.03728 seconds
] 
Search
Help
Register
Login
Home
