conventionally named `sod__ap_master', which it is expected to pass on to
its `next_method' function if necessary.)
- The function type protocol is implemented on DELEGATING-DIRECT-METHOD
+ The function type protocol is implemented on `delegating-direct-method'
using slot reader methods. The actual values are computed on demand in
- methods defined on SLOT-UNBOUND."))
+ methods defined on `slot-unbound'."))
(defmethod slot-unbound (class
(method delegating-direct-method)
("next_method" (* (lisp (commentify-function-type
(sod-method-next-method-type
method)))))
- . (if (varargs-message-p message)
- (cons (make-argument *sod-master-ap*
- (c-type va-list))
- method-args)
- method-args))))))
+ .
+ (if (varargs-message-p message)
+ (cons (make-argument *sod-master-ap*
+ (c-type va-list))
+ method-args)
+ method-args))))))
;;;--------------------------------------------------------------------------
;;; Effective method classes.
;; The first thing we need to do is find all of the related objects. This
;; is a bit verbose but fairly straightforward.
;;
- ;; Next, we generate the effective method body -- using COMPUTE-EFFECTIVE-
- ;; METHOD-BODY of all things. This gives us the declarations and body for
+ ;; Next, we generate the effective method body -- using `compute-effective-
+ ;; method-body' of all things. This gives us the declarations and body for
;; an effective method function, but we don't have an actual function yet.
;;
;; Now we look at the chains which are actually going to need a method