> Thomas Kuhn wrote:
>
> since the runtime library for GCJ (the Java-frontend for GCC) has no support
> for AWT, I think about porting the AWT-package of Classpath to that compiler.
> Well, do you think it is possible to port those Parts from JNI to CNI and to
> extract the AWT-Parts from the package (and use them without the other
> Packages ?)
There was a post about this on the libgcj list today. I think porting
CLASSPATH's native peers to CNI could be done fairly easily. It would be an
interesting project and I've been hoping to find the time to work on this for a
while.
Personally, I really like CNI, and I think that AWT peers written with CNI will
be cleaner and possibly faster than the JNI implementation.
That said, I also agree that libgcj needs to get closer to classpath, and
perhaps it would be nice if classpath could support gcj 'out of the box'.
libgcj's coverage of the APIs is currently very small and I don't see that
changing much without using classpath code.
[Incidently, native method dispatch with gcj/CNI is more than 6X faster than JNI
on the IBM Linux JDK. Interface calls, which I think should also important for a
fast AWT, should also be very competitive once my changes for constant-time
interface dispatch are checked in.]
regards
[ bryce ]
