aboutsummaryrefslogtreecommitdiffstats
path: root/docs/progGuideDB/implementation.adoc
diff options
context:
space:
mode:
authorAlexander Kriegisch <Alexander@Kriegisch.name>2021-07-16 10:48:06 +0700
committerAlexander Kriegisch <Alexander@Kriegisch.name>2024-01-06 10:09:11 +0100
commita6a1dbea46fd4829189b23fb900da6a586a8151a (patch)
treeb6d8a3b4e38e320813566535c6ea4f036fb4ba91 /docs/progGuideDB/implementation.adoc
parentfa63feda31a6a9656173a63dc057993d98469305 (diff)
downloadaspectj-a6a1dbea46fd4829189b23fb900da6a586a8151a.tar.gz
aspectj-a6a1dbea46fd4829189b23fb900da6a586a8151a.zip
Fix more AsciiDoc links and code blocks (WIP)
- Add Java syntax highlighting to AspectJ and Java files - Add XML syntax highlighting to XML files (Ant, LTW etc.) - Dedent and remove empty lines, where necessary - Enclose in-line line numbers for Java code in /*23*/ comments in order to enable Java formatting Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
Diffstat (limited to 'docs/progGuideDB/implementation.adoc')
-rw-r--r--docs/progGuideDB/implementation.adoc6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/progGuideDB/implementation.adoc b/docs/progGuideDB/implementation.adoc
index a34324d5f..f7a8f7c7b 100644
--- a/docs/progGuideDB/implementation.adoc
+++ b/docs/progGuideDB/implementation.adoc
@@ -17,6 +17,7 @@ implementations should do tomorrow.
According to the AspectJ language semantics, the declaration
+[source, java]
....
before(): get(int Point.x) { System.out.println("got x"); }
....
@@ -128,6 +129,7 @@ source code. This means that there may be call join points to
`Class.forName` or `StringBuffer.append` from programs that do not, at
first glance, appear to contain such calls:
+[source, java]
....
class Test {
void main(String[] args) {
@@ -158,6 +160,7 @@ be the case. Before advice is allowed.
The second is that the control flow of a handler join point is not
picked out. For example, the following pointcut
+[source, java]
....
cflow(call(void foo()) || handler(java.io.IOException))
....
@@ -173,6 +176,7 @@ This does not restrict programs from placing before advice on handlers
inside _other_ control flows. This advice, for example, is perfectly
fine:
+[source, java]
....
before(): handler(java.io.IOException) && cflow(void parse()) {
System.out.println("about to handle an exception while parsing");
@@ -187,6 +191,7 @@ have fewer such restrictions.
The code for Java initializers, such as the assignment to the field d in
+[source, java]
....
class C {
double d = Math.sqrt(2);
@@ -203,6 +208,7 @@ a super-constructor (as opposed to a `this` constructor), the target
type's initialization code will _not_ be run when that inter-type
constructor is called.
+[source, java]
....
aspect A {
C.new(Object o) {} // implicitly calls super()