While the aspect definition in the [[examples/example1|previous example]] appropriately modularizes the new feature, it is a typical example of a //stateful// aspect, implemented with book-keeping code (the ''times'' variable in the pointcut). Recognizing this fact, we now present an alternative implementation that uses a general-purpose ''trace''
While the aspect definition in the [[examples/example1|previous example]] appropriately modularizes the new feature, it is a typical example of a //stateful// aspect, implemented with book-keeping code (the ''times'' variable in the pointcut). Recognizing this fact, we now present an alternative implementation that uses a general-purpose ''trace''
<a id="button" class="button" onclick="toggle('code1','example1')"> <span>Toggle between the code and example </span></a>
</html>
</html>
-
AspectScript permits to expose context information to either the advice or other pointcuts, a pointcut can take as optional parameter an environment, and define new bindings in it. Using this environments, we can match a sequence of //removeTag// invocations happening in a 10 seconds interval.
+
\\ AspectScript permits to expose context information to either the advice or other pointcuts, a pointcut can take as optional parameter an environment, and define new bindings in it. Using this environment, we can match a sequence of //removeTag// invocations happening in a 10 seconds interval. The following window uses the "trace" PCD with an environment: