+1 for keeping C++. I still haven't heard what the compiler build and
packaging issues have been, other than boost, which can be removed with
a patch.
On 8/26/2010 4:52 PM, David Reiss wrote:
This has been
a hassle for httpd and svn... those two projects generally do *not*
provide binaries, and rely on downstream packagers. Of course, we
could also rely on packagers.
That sounds fine to me.
I'm more comfortable with C++ than Java, but it seems easier to use
compiler subsystems (like ANTLR) and other tools in Java.
My understanding was that ANTLR serves the same purpose as lex and yacc,
which are already used by Thrift.
And back to
the deployment question regarding dependencies: will the packagers
have all the deps available? Compare that to shipping one .jar.
The Thrift compiler doesn't have any runtime dependencies other than
system libraries. I think the few compile-time dependencies it has
can be eliminated far more easily than rewriting several thousand
lines of code.
--David
