On 3/19/06, Andrew John Hughes <[EMAIL PROTECTED]> wrote: > I think the interface problem you mention is the most obvious, but I > think this should be solvable by declaring the class abstract (which > shows up in JAPI too).
It's a shame that we can't use annotations on the trunk; it wouldn't be hard to have Japi pick up an annotation which marked stub methods and flag any such methods as errors. What's the status on the whole ecj-as-gcc-frontend thing? Since gcj and ecj are pretty much the only maintained Free java compilers at this point, seems to me that's the only blocker to making the generics branch the primary development trunk and adopting the new language features wholesale... I also remember hearing about some stub methods in Swing which are currently defined as calling super.whatever(), which will eventually need to be overridden but currently other features in the class do work. Declaring the class as abstract would break working functionality; deleting the stub wouldn't have any effect on the japi results because the inherited method would be picked up. As far as I can figure out, an annotation is pretty much the only way to get these kinds of methods to get flagged by Japi. Stuart. -- http://sab39.dev.netreach.com/
