>>>>> "Stuart" == Stuart Ballard <stuart.a.ballard@xxxxxxxxx> writes: Stuart> I believe Classpath already has an unchecked NotImplementedException Stuart> so that's what I used. Any method marked as "throws Stuart> NotImplementedException" will be reported by Japi as "not implemented Stuart> in Classpath", in the same category as "missing" errors. This is a nice hack, I like it. We probably don't want to use the JDWP exception as a marker, in general... I'd rather not overload it like this. We can easily add 'gnu.classpath.NotImplementedException' though. Stuart> If this approach is acceptable to everyone, the next question is how Stuart> do we identify the stub methods to flag them? By hand I'm afraid... Stuart> A) Void method that does nothing at all or nothing but return; Stuart> B) Method that unconditionally throws; Ones that 'throw new Error' are probable stubs. Sometimes there are methods which legitimately do nothing else; but those tend to throw something more specific. Tom
