[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [aspectj-users] Xlint:unmatchedSuperTypeInCall is unpreventableand uninformative
|
Yes, I found that 2004 post myself. It seems to refer to the
java.lang.Object case of the warning, rather than the general case.
Thanks for the other link. Unfortunately I have never seen "see also"
messages either within Eclipse or using ant on the command line.
The issue I have is that where my pertarget aspect was advising ~50
calls using call( * T+.*( .. ) ), now it's advising ~1300 calls using
call( * *( .. ) ) (all with runtime tests that will disqualify nearly
every one of them). Eclipse is covered with little orange bars on the
right of nearly every file. I can't help but think that the performance
will suffer. Eclipse has a hard enough time loading the aspect since it
has to populate the Cross-References view.
Josh
-----Original Message-----
From: aspectj-users-bounces@xxxxxxxxxxx
[mailto:aspectj-users-bounces@xxxxxxxxxxx] On Behalf Of Andy Clement
Sent: Wednesday, September 26, 2007 3:21 PM
To: aspectj-users@xxxxxxxxxxx
Subject: Re: [aspectj-users] Xlint:unmatchedSuperTypeInCall is
unpreventableand uninformative
using google.
I find this post by me in 2004:
http://dev.eclipse.org/mhonarc/lists/aspectj-dev/msg01058.html
The xlint is discussed in the 1.2 readme
http://www.eclipse.org/aspectj/doc/next/README-12.html
