mirror of
https://github.com/eclipse-aspectj/aspectj.git
synced 2024-09-13 15:45:38 +02:00
variables available in if(b), removed mdash entity as unknown
This commit is contained in:
parent
24508c8f49
commit
52d8746b89
@ -501,9 +501,10 @@
|
||||
<listitem>
|
||||
Picks out each join point where the boolean expression
|
||||
evaluates to <literal>true</literal>. The boolean expression used
|
||||
can only access static members, variables exposed by teh enclosing
|
||||
can only access static members, parameters exposed by the enclosing
|
||||
pointcut or advice, and <literal>thisJoinPoint</literal> forms. In
|
||||
particular, it cannot call non-static methods on the aspect.
|
||||
particular, it cannot call non-static methods on the aspect or
|
||||
use return values or exceptions exposed by after advice.
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
@ -1521,8 +1522,8 @@ aspect A {
|
||||
</para>
|
||||
|
||||
<para>
|
||||
If a type pattern is an exact type—if it doesn't
|
||||
include a wildcard—then the matching works just
|
||||
If a type pattern is an exact type - if it doesn't
|
||||
include a wildcard - then the matching works just
|
||||
like normal type lookup in Java: </para>
|
||||
|
||||
<itemizedlist>
|
||||
@ -1616,7 +1617,7 @@ aspect A {
|
||||
|
||||
<para>
|
||||
Type patterns with wildcards do not depend on Java's
|
||||
usual scope rules—they match against all types
|
||||
usual scope rules - they match against all types
|
||||
available to the weaver, not just those that are
|
||||
imported into an Aspect's declaring file.
|
||||
</para>
|
||||
|
Loading…
Reference in New Issue
Block a user