[aspectj-dev] call for XLint contributions

[Wes Isberg <wes@xxxxxxxxxxxxxx>]

ajc's -XLint option produces messages that can avoid common
mistakes when programming in AspectJ.  In 1.1, the user can
enable or disable specific messages, so ajc can look for more
kinds of mistakes without worrying that users will be inundated
with unneeded messages.  That means we can look for many more
kinds of mistakes.

So, users, particularly new users, are encouraged to submit
a programming mistake they made and the kind of compiler
error they would like to see as a result.  That way we
get a new list of -XLint candidates.  You can submit them
by emailing this list or adding an enhancement request bug
at https://bugs.eclipse.org/bugs/enter_bug.cgi?product=AspectJ
The best candidates for XLint messages are legal programs
that don't do what was intended but look like they should,
particularly if it is difficult to find out that it didn't.

Developers interested in contributing to the project can
submit patches to implement particular XLint messages.  To get
started, email aspectj-dev@xxxxxxxxxxx with the XLint condition
you'd like to implement, and one of the committers can help you
work out the right approach.  Then submit a patch to the bug.

I believe that new XLint messages could be rolled into the
maintenance (1.1.X) releases, so the sooner they're designed
and implemented, the better!

Thanks -
Wes