Am Donnerstag, 11. Oktober 2012 19:29:18 UTC+2 schrieb Lukas Eder: > Just like with any technology, Xtend has flaws. From my experience, the > > advantages outweigh the flaws. > Yes, I have seen you debugging it :-) >
As I said: The advantages outweigh the flaws. I didn't try 2.3.1 but I'm pretty sure many bugs have already been fixed. Also, I'm worried that you favor anecdotal "evidence" over facts here :-( > > We'd need a version of Xtend on Maven Central but that shouldn't be a > show > > stopper. Other projects need the same plus the generated code doesn't > have > > any dependencies. The dependencies are only necessary when someone works > on > > the code generator itself. > > From what I understand, running such a code generator will need some > runtime dependencies? > To edit the code generator, you need Eclipse and the Xtend plugins at the moment. There is a plugin for Maven which can compile Xtend to Java but I didn't test/try/use that. To run the code generator, you need org.eclipse.xtext.xbase.lib on the classpath. The output of the code generator has only the dependencies which you coded into the generator. > >> 4. interoperable enough (Xtend / Xtext code cannot be mixed with Java > >> code) > > > > Bullshit. I'm extending Java classes from Xtend and I'm extending Xtend > > classes in Java. The output of Xtend is pure Java. What gives you the > idea > > that Java isn't compatible with Java? > > I cannot write Xtend code in a ".java" file. Neither can I write Java > code in a ".xtend" file. I see no strong reason for that not to be > possible. > For the same reason why you can't write SQL in a .java file or C or Smalltalk: It's a different language with different goals. Xtend wants to be compact and readable. Java wants to be unambiguous. Xtend supports templates in the language, Java has only very basic support for inlining multi-line strings. Xtend can be converted to Java. But that doesn't mean you can write a useful grammar that can mix the two. > In any case, don't be discouraged by my decision not to use Xtend. > Feel free to publish, maintain and support your own generator > implementation. If you wish, I can then reference to such an > inofficial generator implementation from the jOOQ website. > I'm completely discouraged by your decision. I simply don't have to time to maintain such an effort. For me, your decision means that I've wasted two weeks of my life :-( Plus all the effort I'll have to waste in the future to port my extensions to the code generator to whatever you might eventually come up with. Regards, A. Digulla
