Re: @deprecated

[Tom Tromey]

>>>>> "Stuart" == Stuart Ballard <address@hidden> writes:

Stuart> Looking at the current japi results (which once again blew my mind
Stuart> with the sheer magnitude of the improvement) I noticed that quite a
Stuart> lot of (minor) errors are of the form 'deprecated in jdk1x, but not
Stuart> deprecated in classpath'.

I spot checked a bunch of these last week, and in all cases the code
is correctly marked.  I think that perhaps the compiler you're using
when building the class files has a bug here -- I know some earlier
versions of gcj did :-(

Stuart> It occurred to me that with the output from
Stuart> japicompat, a copy of the classpath sources and a little perl, it
Stuart> might be possible to come up with a script that can automatically add
Stuart> "@deprecated" in the appropriate place on any such class or member,
Stuart> hence getting an almost instant 0.3% improvement in japi scores which
Stuart> incidentally would push us over 90% of 1.4, which is a nice little
Stuart> psychological milestone :)

One fun idea would be a japi-related eclipse plugin which could
automatically warn if you violate a japi rule, including @deprecated
markings.  Supplying the @deprecated (or whatever) could be a "Quick
Fix" :-).

Tom