[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aspectj-users] Xlint:unmatchedSuperTypeInCall is unpreventable and 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
On 26/09/2007, Caplan, Josh <jcaplan@xxxxxxxxxx> wrote:
>
>
>
>
> I'm getting this compiler warning
> (Xlint:unmatchedSuperTypeInCall) for a call( * T+.*( .. ) )
> pointcut (defined on a per. What amazes me about it is that there seems to
> be
>
> 1. absolutely no way to put a declaring type T (other than "Object")
> in the join point signature and still avoid this warning if someone,
> somewhere, calls an overridden method in T on a statically-determined
> supertype of T
>
> 2. absolutely no information in the warning message about the where
> the call is that necessitated it, only that it exists somewhere
>
>
>
> I suppose my join point signature could be call( * *( .. ) ), which I
> presume would blow my bytecode and latency up by a significant factor.
>
>
>
> Is there any point to this warning?
>
>
>
> Josh
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>
