anchor.diff:  ;;; and the intrinsic case.  In the extrinsic case, the expander
   ;;; functions should be generated as host functions so that expansion
   ;;; can take place at compile time.  Cleavir does this by calling the
  -;;; generic EVAL to process the lambda expressions resulting macro
  -;;; definitions.
  +;;; generic EVAL to process the lambda expressions resulting from
  +;;; macro definitions.
   ;;;
   ;;; When the Cleavir tools are used as extrinsic tools, a reasonable
   ;;; method on EVAL would be to convert the form to an AST and then
  
positive.code: ;;;     optional argument to CL:MACRO-FUNCTION was supplied, it is
  ;;;     passed directly as the second argument to the generic
  ;;;     MACRO-FUNCTION.  If not, an argument representing the global
  ;;;     environment is passed instead. 
  ;;;
  ;;;   * Supply one or more methods on the generic MACRO-FUNCTION,
  ;;;     specialized to the implementation-specific global environment
  
negative.code: ;;; situation of :COMPILE-TOPLEVEL by calling the EVAL generic
  ;;; function.
  ;;;
  ;;; For the discussion that follows, recall that we use the word
  ;;; "intrinsic" to mean "native", as in the host and the target
  ;;; environment are the same, and we use the word "extrinsic" to mean
  ;;; "cross", i.e., the two environments are not the same.
  ;;;
  ;;; The reason for calling the Cleavir-specific generic function
  ;;; rather than just calling CL:EVAL is that CL:EVAL might not be the
  ;;; right thing to do.
  ;;;
  ;;; One problematic case is when the global environment (the so-called
  ;;; evaluation environment) is side effected at compile time, for
  ;;; instance as a result of evaluating a DEFUN form at compile time.
  ;;;
  ;;;   * When the Cleavir tools in question are used as extrinsic tools
  ;;;     (i.e., the host system is different from the target system),
  ;;;     then CL:EVAL would side effect the host environment, whereas
  ;;;     it is more likely that the target environment should be side
  ;;;     effected.  For instance, when a target system is bootstrapped
  ;;;     on a host system, the Cleavir tools might be used to fill up
  ;;;     the target environment with definitions of standard macros and
  