We also knew that the python one could be run from within the maven build through jython. I bet nobody considered how much of a known quantity JRuby is, wrt doing the same thing. I can understand that people do not want a Java dependency on the C++ code, and might therefore object to Velocity (although such a dependency really doesn't seem that bad). Python or XSLT seems like the best middle ground dependency for Java and C++ to me.
I think that more effort has been expended on writing code generators, than would have been expended writing the generated code by hand. On 23/09/2007, John O'Hara <[EMAIL PROTECTED]> wrote: > > You know this is just an amazingly bad way to work. > It looks like almost everyone who has worked on the code generators just > threw away the previous one in a fit of Not Invented Here and started > again, > with no discussion. > > When it happens again, to one's favourite version, how will one feel? > > The XSLT one was clean even though no one really likes XSLT. But we have > this big XSLT which generates the docs in pretty print and no one will be > volunteering to rewrite that in Ruby. XSLT is portable, clean and > language > agnostic (and the open saxon.jar did all the work). The Java generator > deserved to die but what was wrong with the Python one? > > I'm not saying the Ruby one is bad, I'm just amazed at the lack of > stability > here. > > You know, I think loading the model into Eclipse EMF and using its code > generation framework could be great..... > > Arrrgh :) > john > > > On 17/09/2007, Alan Conway <[EMAIL PROTECTED]> wrote: > > > > On Mon, 2007-09-17 at 18:54 +0100, Rupert Smith wrote: > > > Can the Ruby generator be run from within Maven? That is, will JRuby > > handle > > > it? For the same reasons that we use jython... > > > > > Its just a couple of ruby scripts, nothing special so I don't see why > > not but I don't know if JRuby has limitations that we'd trip over. > > > > The generator is in 2 pieces: amqpgen.rb builds the AMQP model and > > collects the generated output. cppgen.rb adds some handy functions for > > generating C++, a similar javagen.rb would be easy to write. > > > > See /trunk/cpp/rubygen/templates for examples of use. > > > > Cheers, > > Alan. > > > > > > >
