Bug 238985 - wrong error message "multiple bindings"
Summary: wrong error message "multiple bindings"
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-30 09:44 EDT by Eric Bodden CLA
Modified: 2008-06-30 10:04 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Bodden CLA 2008-06-30 09:44:51 EDT
Build ID: M20060629-1905

Steps To Reproduce:
The following pointcut declaration type-checks fine:

pointcut FailSafeIter_updatesource(Collection v) :  
   call(* Collection+.remove*(..)) && target(v) && 
|| call(* Collection+.add*(..)) && target(v); 

The following however gives me a "multiple bindings" error message. Surely this cannot be right as bindings are clearly just as non-ambiguous as in the previous pointcut declaration.

pointcut FailSafeIter_updatesource(Collection v) :  
   call(* Collection+.remove*(..)) && target(v) && !within(abc)
|| call(* Collection+.add*(..)) && target(v) && !within(abc); 

More information:
Tested with AJDT version 1.4.2.200705221209

abc compiles this pointcut just fine.
Comment 1 Eric Bodden CLA 2008-06-30 09:45:26 EDT
Sorry the first pointcut should have been:

pointcut FailSafeIter_updatesource(Collection v) :  
   call(* Collection+.remove*(..)) && target(v) 
|| call(* Collection+.add*(..)) && target(v); 
Comment 2 Eric Bodden CLA 2008-06-30 10:04:31 EDT
seems to have been fixed in current RC for aspectj 1.6.1. sorry :-(