anchor.diff:  ;;;     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. 
  +;;;     environment is passed instead.
   ;;;
   ;;;   * Supply one or more methods on the generic MACRO-FUNCTION,
   ;;;     specialized to the implementation-specific global environment
  
positive.code: ;;; situation of :COMPILE-TOPLEVEL by calling the EVAL generic
  ;;; function.
  ;;;
  ;;; 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.  The 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 will 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
  
negative.code: ;;; Generic function MACRO-FUNCTION.
  ;;;
  ;;; We define MACRO-FUNCTION as a generic function with two arguments:
  ;;; a symbol and an environment.
  ;;;
  ;;; An implementation can use this function in the following way.
  ;;; Rather than defining implementation-specific methods on
  