[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aspectj-dev] Howto @SuppressAjWarnings
|
Currently the only warning suppressed is the 'adviceDidNotMatch' lint
warning -
we haven't decided about others yet. Obviously there is a normal lint
mechanism
for globally turning some warnings off. This annotation makes sense for
cases
where neither 'always report this as a warning' or 'never report this as a
warning'
are what you want. We'll have to go through all the warnings before 1.5.0
final...
Andy.
"Oli B."
<boehm@xxxxxxxxxx
> To
Sent by: aspectj-dev@xxxxxxxxxxx
aspectj-dev-bounc cc
es@xxxxxxxxxxx
Subject
[aspectj-dev] Howto
17/04/2005 19:44 @SuppressAjWarnings
Please respond to
boehm@xxxxxxxxxx;
Please respond to
AspectJ developer
discussions
<aspectj-dev@ecli
pse.org>
Hi,
I did some experiments with @SuppressAjWarnings with different results:
@SuppressAjWarnings
before() : call(* java.lang.String.helloWorld()) {
System.out.println(thisJoinPoint);
}
This works, the warning is suppressed. But when I tried
@SuppressAjWarnings
after() : call(String java.lang.Xxx.toString()) {
System.out.println(thisJoinPoint);
}
I got a "Xlint:invalidAbsoluteTypeName" warning. Is it possible, that
some warnings can't be suppressed?
regards
Oliver
--
Oliver Böhm
http://www.javatux.de
_______________________________________________
aspectj-dev mailing list
aspectj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-dev
