diff options
Diffstat (limited to 'docs/dist/doc/porting.adoc')
| -rw-r--r-- | docs/dist/doc/porting.adoc | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/docs/dist/doc/porting.adoc b/docs/dist/doc/porting.adoc index 0bda1cf3b..31f3016ae 100644 --- a/docs/dist/doc/porting.adoc +++ b/docs/dist/doc/porting.adoc @@ -17,7 +17,7 @@ _© Copyright 1998-2002 Palo Alto Research Center Incorporated, [[pre-1_2]] === Porting pre-1.2 code to AspectJ 1.2 -README-12.html contains a discussion of the changes between 1.1 and 1.2. +README-1.2.html contains a discussion of the changes between 1.1 and 1.2. The key points are: *The default AspectJ compiler compliance level is now 1.4* (whereas in @@ -192,7 +192,7 @@ https://bugs.eclipse.org/bugs/show_bug.cgi?id=59921[59921]. [[pre-1_1]] === Porting pre-1.1 code to AspectJ 1.1 -README-11.html contains a discussion of the language changes from 1.0 to +README-1.1.html contains a discussion of the language changes from 1.0 to 1.1. The high points: The `call(..)` pointcut designator is now implemented only at the call @@ -201,14 +201,14 @@ the callee side. So in 1.0 if you compiled a pointcut using `call(..)` but only passed the compiler the code for the target of the call, the pointcut could be implemented. This is not true for 1.1. To fix this, use `execution(..)` in place of `call(..)`, or include all calling -clients in the compile. (xref:README-11.adoc#NO_CALLEE_SIDE_CALL[more +clients in the compile. (xref:README-1.1.adoc#NO_CALLEE_SIDE_CALL[more info]) Type-patterns are no longer permitted for the defining type of inter-type declarations. Replace the pattern with a type. In many cases, you can declare members on an interface type, and then declare that the types picked out by the type-pattern implement have the interface as -their parent. (xref:README-11.adoc#SINGLE_INTERCLASS_TARGET[more info]) +their parent. (xref:README-1.1.adoc#SINGLE_INTERCLASS_TARGET[more info]) Type-patterns are no longer permitted when specifying `declare soft`. Replace the pattern with a literal type. @@ -216,7 +216,7 @@ Replace the pattern with a literal type. Wildcards patterns (`foo..*`) are no longer permitted for `this()`, `target()`, or `args()`. Replace the pattern with a literal type or with a subtype wildcard (`Type+`). -(xref:README-11.adoc#INSTANCEOF_ON_WILD[more info]) +(xref:README-1.1.adoc#INSTANCEOF_ON_WILD[more info]) Conflicts will be reported for no-argument constructors generated by compilers when no constructor is defined for a class. That means the @@ -234,14 +234,14 @@ One fix is to declare a non-conflicting constructor by adding arguments (or defining a constructor in the target class); a better fix might be to do the work of the declared constructor in advice on the initialization join point for the object. -(xref:README-11.adoc#DEFAULT_CONSTRUCTOR_CONFLICT[more info]) +(xref:README-1.1.adoc#DEFAULT_CONSTRUCTOR_CONFLICT[more info]) The pointcut designators `within()` and `withincode()` will not pick out code within the lexical extent of method-local and anonymous inner types (because these are not represented as such in bytecode form). Because `within` forms specify staticly-determinable pointcuts, they might be used in declare error or declare warning statements, which might produce -different results. (xref:README-11.adoc#WITHIN_MEMBER_TYPES[more info]) +different results. (xref:README-1.1.adoc#WITHIN_MEMBER_TYPES[more info]) The compiler will report an error that the form `aspect {name} dominates {list}...` is no longer supported. It has been @@ -252,17 +252,17 @@ replaced by a new declare statement: declare precedence : {name} {list}... .... -(xref:README-11.adoc#ASPECT_PRECEDENCE[more info]) +(xref:README-1.1.adoc#ASPECT_PRECEDENCE[more info]) The field set join point now has a return type of `void`. Compiling programs using around advice on these join points might cause errors unless the return type of the around advice and the result of any proceed() call is `Object` or `void`. -(xref:README-11.adoc#VOID_FIELD_SET[more info]) +(xref:README-1.1.adoc#VOID_FIELD_SET[more info]) The compiler cannot implement after or around advice for the handler PCD because the end of exception handlers is ambiguous in bytecode. Try to -use before advice. (xref:README-11.adoc#AFTER_HANDLER[more info]) +use before advice. (xref:README-1.1.adoc#AFTER_HANDLER[more info]) [[pre-1_0_4]] === Porting pre-1.0.4 code |