Monday, September 05, 2005

Current state of GCJ

GCJ is the Java compiler component of GNU's GCC.

So where is GCJ now? Probably, still not enough to catch with Sun's JDK. When at least full-1.4 compatibility is released, I'll be one of the first ones to jump ship.


  • java.applet - Believed to be complete, but note that without a functional AWT it isn't very useful.

  • java.awt - A lot of code exists, but not enough for use in real applications.

  • java.beans - Believed to be functional and complete, should be compatible with JDK 1.4.

  • java.io - Ok.

  • java.lang - Ok.

  • java.lang.ref - Ok.

  • java.lang.reflect - Ok. Does not check access permissions.

  • java.math - Ok.

  • java.net - Ok.

  • java.nio - The public interface is ready, but the implementation is not working yet.

  • java.rmi - Ok.

  • java.security - Code exist; completeness unknown.

  • java.sql - Ok, should be compatible with JDK 1.4.

  • java.util - Ok.

  • java.util.jar - Ok.

  • java.util.regex - Ok.

  • java.util.zip - Ok.

  • java.text - Ok, but most localization data not available.

  • javax.accessibility - Some code; status unknown.

  • javax.crypto - We recommend using GNU Crypto.

  • javax.naming - Complete, but no providers written.

  • javax.sql - Some code; status unknown.

  • javax.swing - Some code, but not enough for real applications.

  • javax.transaction - Complete, but no providers written.



Hmm, when can we finally set Java free. When can Java be fully open. So far, it is in a use-at-your-delight-and-risk thing.
Cheers!

richard@work

No comments: