Subject: compiler investigation
From: Jonathan Aldrich (jonal@cs.washington.edu)
Date: Thu Apr 19 2001 - 09:47:05 PDT
I did some investigation of Java compilers that could be extended to
support Java language extensions. The results (including all the
semi-realistic choices I could find on the web) are summarized in a table
at:
http://www.cs.washington.edu/homes/jonal/archjava/compilers.html
If we limit ourselves to compilers with the following characteristics:
* open source
* written in Java or perhaps GJ
* target pure Java, not some tricky extension
then we have only two choices: Kopi or Barat. Kopi is the larger project,
thus hopefully better quality, and our connection with Clifton gives us
some background for using it. However, we do have a certain amount of
negative feedback saying that Kopi is not all one might hope for.
We could also give up open source and choose javac or deal with extra
typechecking hassle and choose pizza/mjc. I don't really want to
implement anything in C code, though.
Another alternative is to "roll our own" extensible Java compiler. The
advantage is that we could do the minimum work necessary: parse Java,
build an AST, typecheck it minimally, and output it back to Java source
for compilation by javac. Also, Michael and I could share the base work,
make it available to the community, and then both extend the result with
our favorite language extensions.
Right now I think I'd lean towards modifying Kopi, but also checking out
Barat and considering rolling my own if I am getting stuck down a rathole.
What is your preference, Michael? Do others in the group have an interest
in this issue? Know any undergrads who might want to write a Java
compiler?
Jonathan
_______________________________________________
Cecil mailing list
Cecil@cs.washington.edu
http://majordomo.cs.washington.edu/mailman/listinfo/cecil
This archive was generated by hypermail 2b25 : Thu Apr 19 2001 - 09:48:04 PDT