Community
Participate
Working Groups
I would like to see pointcut overloading supported in future versions, because I think it's very natural for Java programmers to have this, compared to method overloading. One issue, Gregor raised is the one that people also requested the feature of omitting certain parameters in pointcuts, such as: pointcut foo(Object o1): foo(Object o1, Object o2); If one *does* want to allow this, this is of course an issue: What happens in the case pointcut foo(Object o): foo(Object o, String s); ... where ... pointcut foo(Object o, String s): call(* Object.equals(..)) && this(o) && target(s); Problem: Should foo(String s) only match calls to Strings, as foo(Object o, String s) does, or should it omit the constraint introduced by target(s), since s is not bound? So either one could drop this feature of omission altogether or one could find some sensible semantics for this ambiguity. But overloading would be nice anyway IMHO.
this is a perfectly valid feature request but we have no immediate plans to implement it so marking as "LATER" for consideration in future planning cycles.
LATER/REMIND bugs are being automatically reopened as P5 because the LATER and REMIND resolutions are deprecated.
*** Bug 582496 has been marked as a duplicate of this bug. ***