As I already mentioned, Tom
blogged
on Monday about the compiler change that put Classpath's japi results
against JDK1.4 at over 90% - specifically 90.47%. I remember that
because it was a bigger improvement than I could account for based on
the compiler difference I knew about. I attributed the discrepancy to
compiler differences I
didn't know about, but now I suspect it may have represented real improvement.
You see, it's now four days later, and the
same page is now showing 91.49%. That's over a full percentage point difference and only 8.5% to go!
At that rate of improvement the numbers will hit 100% in a month ;)
The
results against JDK1.3
have now climbed over 90% for the first time too. At first glance it's
weird that the 1.3 percentage should be lower, but it actually makes
sense - the APIs that were new in 1.4 are mostly covered extremely well
already; the biggest hole is in areas that were also in 1.3 (mostly
Swing, since that's such a disproportionate chunk of the size of the
JDK API), and since 1.3 is smaller that hole represents a higher
percentage.
Classpath hackers, your progress is insane! Congratulations!
In other news, after a long hiatus, I'm actually making progress
towards getting some support of JDK1.5 features into japitools. We'll
see if my motivation holds up long enough for the results to actually
be visible. There are many evil
(<mikemyers>EEE-VILLE</mikemyers>) corner cases to be
handled in the generics world...
