Re: japi and public references to non-public types

[Stuart Ballard]

On 10/5/05, Jeroen Frijters <address@hidden> wrote:
> What about the NameImpl issue?

Definitely "detectable and ignorable". Check out
http://www.kaffe.org/~stuart/japi/htmlout/cvs/h-jdk13-classpath.html
It's already being detected and ignored. The code needs a little
refinement but the basic structure is there.

A separate report of "broken things in the API" is an excellent idea
(I'm trying to avoid volunteering to write "japilint", especially as I
can't believe the Java world doesn't already have an FxCop equivalent,
but I have a funny feeling I'm going to write it anyway ;) ). APIs
that are fundamentally broken and unimplementable are outside the
scope of japicompat, though, I think.

If we do find a situation where we need to differ from the JDK but
there's absolutely no way to distinguish that situation to make it
ignorable in japicompat then annotations are probably the way to go,
but I think it's a last resort...

Stuart.
--
http://sab39.dev.netreach.com/