On Thu, Mar 5, 2009 at 7:12 PM, Jake Luciani <[email protected]> wrote:
> I've always wondered why the IDL compiler was written in c++, seems > like a bad choice. > > I think a java compiler using JavaCC would be a bit better (though > requiring java is a pain for some). > At least it would be cross platform.... > > -Jake > I've wondered the same myself. After all, it isn't a compiler at all. It is just a code generator. A cross platform language like java, ruby, perl, or python seems like a better choice for the "compiler". I don't see the benefit in c++. It seems there are a couple posts a week to the mailing lists about c++ build failures on various platforms. Anyone have an interest in contributing a java implementation? Thrift could benefit tremendously from a more maintainable implementation that also uses some text templates for each language. In Java, Velocity or Freemarker could take care of the code generation. I don't think the task would be monumental, but I'm not willing to take the task on myself. I'd be willing to contribute if someone else takes the initiative to start the project. Mike > > On Thu, Mar 5, 2009 at 7:15 PM, Michael Greene <[email protected]> > wrote: > > Jérémie BORDIER <[email protected]> wrote: > >> I might be wrong, but i think that the current compiler isn't cross > >> platform, this could be the right time to do something to ease > >> thrift's accessibility on windows (even if they don't run the CPP > >> Library, at least they could generate Java stubs) > > > > Unfortunately, the cross-platform problems with the C++ Thrift > > compiler are mostly outside of the project's control, but I agree that > > this is a big problem at the moment. As far as I can tell (and I've > > looked far and wide) Flex and Bison versions late enough for Thrift > > simply cannot be built on Windows. I have some changes stored away in > > a working copy to build the compiler in Visual C++ that are mostly > > working, but lack a native Windows flex lib. > > > > Michael Greene > > >
