org.aspectj.weaver.bcel
Class BcelCflowCounterFieldAdder
java.lang.Object
org.aspectj.weaver.ConcreteTypeMunger
org.aspectj.weaver.bcel.BcelTypeMunger
org.aspectj.weaver.bcel.BcelCflowCounterFieldAdder
- All Implemented Interfaces:
- PartialOrder.PartialComparable
public class BcelCflowCounterFieldAdder
- extends BcelTypeMunger
This type munger will modify a given class (see the munge() method) to include a field representing a CflowCounter object.
Methods inherited from class java.lang.Object |
clone, finalize, getClass, notify, notifyAll, wait, wait, wait |
BcelCflowCounterFieldAdder
public BcelCflowCounterFieldAdder(ResolvedMember cflowCounterField)
munge
public boolean munge(org.aspectj.weaver.bcel.BcelClassWeaver weaver)
- Overrides:
munge
in class BcelTypeMunger
getMatchingSyntheticMember
public ResolvedMember getMatchingSyntheticMember(Member member)
- Overrides:
getMatchingSyntheticMember
in class ConcreteTypeMunger
getSignature
public ResolvedMember getSignature()
- Overrides:
getSignature
in class ConcreteTypeMunger
matches
public boolean matches(ResolvedType onType)
- Overrides:
matches
in class ConcreteTypeMunger
existsToSupportShadowMunging
public boolean existsToSupportShadowMunging()
- Description copied from class:
ConcreteTypeMunger
- Some type mungers are created purely to help with the implementation of shadow mungers. For example to support the cflow()
pointcut we create a new cflow field in the aspect, and that is added via a BcelCflowCounterFieldAdder.
During compilation we need to compare sets of type mungers, and if some only come into existence after the 'shadowy' type
things have been processed, we need to ignore them during the comparison.
Returning true from this method indicates the type munger exists to support 'shadowy' stuff - and so can be ignored in some
comparison.
- Overrides:
existsToSupportShadowMunging
in class ConcreteTypeMunger
toString
public java.lang.String toString()
- Overrides:
toString
in class BcelTypeMunger