Bugzilla – Full Text Bug Listing
| Summary: | Pointcut resolution fails against type variables | ||
|---|---|---|---|
| Product: | [Tools] AspectJ | Reporter: | Adrian Colyer <adrian.colyer> |
| Component: | Compiler | Assignee: | aspectj inbox <aspectj-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | adrian.colyer |
| Version: | 1.5.0 | ||
| Target Milestone: | 1.5.1 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
I'll take this one... fix committed in CVS, waiting on build. This gives us a capability I've been wanting for several years now... fix available. |
Ok, so I'm on the bleeding edge of aspect design here... but I have a generic aspect of the form public abstract aspect MyAspect<T extends Bar> { declare warning : T.somePC() : "a match"; } and Bar is defined as: public abstract aspect Bar { public abstract pointcut somePC(); } (yes, what that enables is indeed unbelievably cool). We fail (perhaps unsurprisingly) when compiling the generic aspect because we can't find the pointcut somePC in T. We should of course be looking in the upper bound when searching for a pointcut in a type variable...