diff options
| author | acolyer <acolyer> | 2004-08-04 16:06:44 +0000 |
|---|---|---|
| committer | acolyer <acolyer> | 2004-08-04 16:06:44 +0000 |
| commit | 290a13b086dc2c7f50330092d56d4290f8b4a7da (patch) | |
| tree | 07555954ed6fc67528aad45a1923fba35dde65ed /docs/progGuideDB | |
| parent | 086757332d7de8fa5f9f1b72302f3daf1aeb3316 (diff) | |
| download | aspectj-290a13b086dc2c7f50330092d56d4290f8b4a7da.tar.gz aspectj-290a13b086dc2c7f50330092d56d4290f8b4a7da.zip | |
fix for Bugzilla Bug 61569
if-pointcuts with side-effects
Diffstat (limited to 'docs/progGuideDB')
| -rw-r--r-- | docs/progGuideDB/semantics.xml | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/progGuideDB/semantics.xml b/docs/progGuideDB/semantics.xml index 650cc7345..3c02329f0 100644 --- a/docs/progGuideDB/semantics.xml +++ b/docs/progGuideDB/semantics.xml @@ -881,6 +881,13 @@ if(thisJoinPoint.getKind().equals("call")) </programlisting> + <para> + Note that the order of evaluation for pointcut expression + components at a join point is undefined. Writing <literal>if</literal> + pointcuts that have side-effects is considered bad style and may also + lead to potentially confusing or even changing behavior with regard + to when or if the test code will run. + </para> </sect3> </sect2> |