diff options
author | acolyer <acolyer> | 2004-11-24 19:57:59 +0000 |
---|---|---|
committer | acolyer <acolyer> | 2004-11-24 19:57:59 +0000 |
commit | acbb4e5b1a7c107d0f3897431b15a78d9026c381 (patch) | |
tree | 27bace6b8184de939ece3f89b6c354a31aa97a94 /docs/adk15ProgGuideDB/pertypewithin.xml | |
parent | 639b61b6a7f5cd090137340c35c2f4ae355ad538 (diff) | |
download | aspectj-acbb4e5b1a7c107d0f3897431b15a78d9026c381.tar.gz aspectj-acbb4e5b1a7c107d0f3897431b15a78d9026c381.zip |
more updates to 1.5 design
Diffstat (limited to 'docs/adk15ProgGuideDB/pertypewithin.xml')
-rw-r--r-- | docs/adk15ProgGuideDB/pertypewithin.xml | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/docs/adk15ProgGuideDB/pertypewithin.xml b/docs/adk15ProgGuideDB/pertypewithin.xml index 5f5b8fd66..e870f10e5 100644 --- a/docs/adk15ProgGuideDB/pertypewithin.xml +++ b/docs/adk15ProgGuideDB/pertypewithin.xml @@ -2,5 +2,19 @@ <title>The pertypewithin Aspect Instantiation Model</title> + <para>This is a placeholder to stimulate discussion around a possible new + instantiation model : <literal>pertypewithin(OptionalParensTypePattern)</literal>. + The semantics of <literal>pertypewithin</literal> are that a new aspect + instance will be created at the <literal>staticinitialization</literal> + join point of each type matching the given type pattern.</para> + + <para>Discussion must include motivating use cases. Raise the issue that + pertypewithin takes a type pattern, not a pointcut.</para> + + <para>We will only do this if we believe we can generate an implementation + that is significantly more efficient than hand-coded alternatives.</para> + + <para>Need to define aspectOf(Class), hasAspect(Class).</para> + </chapter> |