On Fri, 2005-10-07 at 14:51 -0400, Stuart Ballard wrote: > On 07 Oct 2005 12:38:03 -0600, Tom Tromey <[EMAIL PROTECTED]> wrote: > > Spell-check identifiers. There's at least one bug like this in java. > > Just today I was looking at code with "primative" all over... > > How do you do that though in a way that catches "primative" but > doesn't catch "Impl" or "Spi" or "Tls" (just found in a quick scan > through jdk-vs-classpath japi errors)? Hardcode those as exceptions to > the rule?
That might be hard. But what would be useful is flagging wrongly spelled overridden public/protected method names (equal -> equals, hascode -> hashCode, finalise -> finalize) or a void method name that is identical to a constructor name, or equal to a name of a (future) reserved word like assert or enum. Cheers, Mark
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Classpath mailing list [email protected] http://lists.gnu.org/mailman/listinfo/classpath
