org.aspectj/tests/bugs/DisjunctVarBinding_3.java

aspect IfPointcut { 

	after(A a, B b) returning:
	   execution(* foo(*,*)) && 
	(args(b,a) || args(a,b)) { 
		System.out.println("Woven"); 
	}
}
Tests for Bugzilla Bug 62073 false ambigous binding error (introduced in 1.2rc2) 2004-05-14 11:27:42 +02:00			`aspect IfPointcut {`

			`after(A a, B b) returning:`
partial fix for bug 61568. These changes are both (a) a performance optimization, and (b) an improvement on the binding across \|\| rules that we implemented in 1.2.1. Instead of saying the the first binding in a left-to-right traversal of the pointcuts DNF is the one that you get (too much to ask users to do DNF rewriting in their heads), this version implements the rule that every \|\| branch in the DNF must bind all formals, and if two \|\| branches can have any join points in common (can match join points of the same kind), then both must bind all formals identically. So it allows things like execution(* (..)) && args(x) \|\| call( *(..)) && this(x) which previously we used to forbid. But primarily it turned out to be a performance optimization. 2004-12-15 21:51:01 +01:00			`execution(* foo(,)) &&`
Tests for Bugzilla Bug 62073 false ambigous binding error (introduced in 1.2rc2) 2004-05-14 11:27:42 +02:00			`(args(b,a) \|\| args(a,b)) {`
			`System.out.println("Woven");`
			`}`
			`}`