anchor.diff:  When you specify the compiler mode, you can also specify a classloader (passing null is allowed).
   Compiled expressions are defined in a child classloader created under any that is supplied.
   It is important to ensure that, if a classloader is specified, it can see all the types involved in
  -the expression evaluation process.
  -If you do not specify a classloader, a default classloader is used (typically the context classloader for
  -the thread that is running during expression evaluation).
  +the expression evaluation process. If you do not specify a classloader, a default classloader is used
  +(typically the context classloader for the thread that is running during expression evaluation).
   
   The second way to configure the compiler is for use when SpEL is embedded inside some other
  -component and it may not be possible to configure it through a configuration object.
  -In these cases, it is possible to use a system property. You can set the
  -`spring.expression.compiler.mode` property to one of the `SpelCompilerMode`
  -enum values (`off`, `immediate`, or `mixed`).
  +component and it may not be possible to configure it through a configuration object. In these
  +cases, it is possible to use a system property. You can set the `spring.expression.compiler.mode`
  +property to one of the `SpelCompilerMode` enum values (`off`, `immediate`, or `mixed`).
   
   
   [[expressions-compiler-limitations]]
   ==== Compiler Limitations
   
  -Since Spring Framework 4.1, the basic compilation framework is in place. However, the framework does not
  -yet support compiling every kind of expression. The initial focus has been on the common expressions that are
  -likely to be used in performance-critical contexts. The following kinds of expression cannot be compiled
  -at the moment:
  +Since Spring Framework 4.1, the basic compilation framework is in place. However, the framework
  +does not yet support compiling every kind of expression. The initial focus has been on the
  +common expressions that are likely to be used in performance-critical contexts. The following
  +kinds of expression cannot be compiled at the moment:
   
   * Expressions involving assignment
   * Expressions relying on the conversion service
  
positive.code: ----
  ====
  
  The following listing shows A more complex example:
  
  ====
  [source,java,indent=0]
  
negative.code: this is fine, but, when used by other components such as Spring Integration,
  performance can be very important, and there is no real need for the dynamism.
  
  The SpEL compiler is intended to address this need. During evaluation, the compiler
  generates a Java class that embodies the expression behavior at runtime and uses that
  class to achieve much faster expression evaluation. Due to the lack of typing around
  expressions, the compiler uses information gathered during the interpreted evaluations
  of an expression when performing compilation. For example, it does not know the type
  of a property reference purely from the expression, but during the first interpreted
  evaluation, it finds out what it is. Of course, basing compilation on such derived
  information can cause trouble later if the types of the various expression elements
  change over time. For this reason, compilation is best suited to expressions whose
  type information is not going to change on repeated evaluations.
  
  Consider the following basic expression:
  
  