§B.1.(3) Between OTJLD 1.2 and OTJLD 1.3

• §1.2.4.(c) : Syntax for role class literals

  Previously, the syntax R<@t>.class was not supported. This restriction has been removed.

• §1.3 : Teams extending non-team classes

  Previously, org.objectteams.Team was the super class of all team classes. As a consequence a team could not extend a non-team class. This restriction has been removed by introducing a new super-type of all teams, the interface org.objectteams.ITeam. This change also affects some paragraphs in §6 as members have been moved to the new interface.

• §4.4.(c) : Further restrict result mapping in after callin bindings

  Clarify that after callin bindings cannot use the -> token to map a result value.

• §4.8.(a) : Precedence declarations affecting after callin bindings.

  While previously the effect of precedence declarations was underspecified it has been defined that the order of elements in a precedence declaration affects their priority similar to §5.1. This implies that the execution order for after bindings is now reversed compared to the previous implementation. In order to visualize this in the program it is now mandatory to mark precedence declarations for after bindings with the keyword after.

• §4.10, §4.10.(a) : Generic callin bindings

  Minor changes to give room for new paragraph §4.10.(e).

• §5.4.1.(a) : Scope of regular binding guard

  Removed an erroneous sentence about the special identifier result in a regular method binding guard. Since parameter mappings are applied before evaluating the guard, the result value can be accessed through a result mapping (§4.4.(c)). Furthermore, the sentence actually confused base and role sides.

• §A.3.2, §A.3.3 : Syntax: generic method bindings

  The location of possible type parameters in a method binding has been made explicit.