[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[aspectj-users] Using ApectJ for option types?
- From: "Curt Cox" <curtcox@xxxxxxxxx>
- Date: Fri, 9 Jun 2006 20:15:33 -0500
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=nRLkP/ZeMyxiO6l/RGD0YYQI0b7+LjxX4VBXT5KqDAjcfj7so68ZtR/7+23cBkoxmhT7ZSlolte/YeO2ckFM02jTyHdWuF1/YFFTspWqR7Bya5qNS1YZEdiqTpDjTg751EO5Jhdq48Y8TZTaNlAmwnna0fCMCwfACGVNnX1ZSYw=
I'm new, to AspectJ. I recently read the following article, which
indicates that AspectJ can be used to generate compile time warnings.
"AOP@Work: Check out library aspects with AspectJ 5"
More specifically, "Table 1. Aspects for error checking" lists some checks.
Later in the article, "Table 2. Aspects for boilerplate code" shows
how an exception can be thrown when null is passed to a public method.
This got me wondering if AspectJ could be used to generate compile
time warnings for null parameters. Compile time warnings of the
sophistication of the Nice language would be ideal, but that doesn't
seem very likely. Still, some warnings would be better than none.
Nice Option Types
Has anyone on the list ever explored this?