aboutsummaryrefslogtreecommitdiffstats
path: root/docs/progGuideDB
diff options
context:
space:
mode:
authorwisberg <wisberg>2005-06-16 17:15:33 +0000
committerwisberg <wisberg>2005-06-16 17:15:33 +0000
commit58add6f5011ccba3f9e998f5bbbf0fccab2dc617 (patch)
tree9fd7ce582a0958fdc8f76fa5b32ebf477a570290 /docs/progGuideDB
parent894bb3c70a41ead4a634c2996312f1b98cecda55 (diff)
downloadaspectj-58add6f5011ccba3f9e998f5bbbf0fccab2dc617.tar.gz
aspectj-58add6f5011ccba3f9e998f5bbbf0fccab2dc617.zip
reflective calls outside the Java language
Diffstat (limited to 'docs/progGuideDB')
-rw-r--r--docs/progGuideDB/implementation.xml11
1 files changed, 9 insertions, 2 deletions
diff --git a/docs/progGuideDB/implementation.xml b/docs/progGuideDB/implementation.xml
index ecd73fb7d..d654eb44e 100644
--- a/docs/progGuideDB/implementation.xml
+++ b/docs/progGuideDB/implementation.xml
@@ -122,11 +122,18 @@
declared public to be overridden in any subtype or to be called
from code in a later compile using the target type as a library.
</para>
-
+
<para>
Other AspectJ implementations, indeed, future versions of ajc, may
define <emphasis>code the implementation controls</emphasis> more
- liberally or restrictively.
+ liberally or restrictively, so long as they comport with the Java
+ language. For example, the <literal>call</literal> pointcut does
+ not pick out reflective calls to a method implemented in
+ <literal>java.lang.reflect.Method.invoke(Object, Object[])</literal>.
+ Some suggest that the call "happens" and the call pointcut should
+ pick it out, but the AspectJ language shouldn't anticipate what happens
+ in code outside the control of the implementation, even when it
+ is a a well-defined API in a Java standard library.
</para>
<para>