| blob | 68f41004cede5cfe1b9294dc769007f29aeedbe2 |
1 ;;;; This software is part of the SBCL system. See the README file for
2 ;;;; more information.
4 ;;;; This software is derived from software originally released by Xerox
5 ;;;; Corporation. Copyright and release statements follow. Later modifications
6 ;;;; to the software are in the public domain and are provided with
7 ;;;; absolutely no warranty. See the COPYING and CREDITS files for more
8 ;;;; information.
10 ;;;; copyright information from original PCL sources:
11 ;;;;
12 ;;;; Copyright (c) 1985, 1986, 1987, 1988, 1989, 1990 Xerox Corporation.
13 ;;;; All rights reserved.
14 ;;;;
15 ;;;; Use and copying of this software and preparation of derivative works based
16 ;;;; upon this software are permitted. Any distribution of this software or
17 ;;;; derivative works must comply with all applicable United States export
18 ;;;; control laws.
19 ;;;;
20 ;;;; This software is made available AS IS, and Xerox Corporation makes no
21 ;;;; warranty about the software, its performance or its conformity to any
22 ;;;; specification.
25 \f
38 pv-table wrappers)))
47 t nil nil)))))))
50 method-alist wrappers)
54 method-alist wrappers))
57 method-alist-p wrappers-p)
61 ;; We have some sort of `real' effective method. Go off and get a
62 ;; compiled function for it. Most of the real hair here is done by
63 ;; the GET-FUN mechanism.
65 method-alist-p wrappers-p)))
68 form
69 method-alist-p
70 wrappers-p)
80 t
88 'fast-method-call
98 ;; The effective method is just a call to CALL-METHOD. This opens up
99 ;; the possibility of just using the method function of the method as
100 ;; the effective method function.
101 ;;
102 ;; But we have to be careful. If that method function will ask for
103 ;; the next methods we have to provide them. We do not look to see
104 ;; if there are next methods, we look at whether the method function
105 ;; asks about them. If it does, we must tell it whether there are
106 ;; or aren't to prevent the leaky next methods bug.
116 method
117 cm-args1
118 fmf-p
119 method-alist
120 wrappers))))
131 fmf-p method-alist wrappers))
134 :pv-cell pv-cell
135 :next-method-call next
142 arg
155 :qualifiers nil
157 arg))))
159 ;; FIXME: this is wrong. Very wrong.
160 ;; It assumes that the only place that
161 ;; can have make-method calls is in
162 ;; the list structure of the second
163 ;; argument to CALL-METHOD, but AMOP
164 ;; says that CALL-METHOD can be more
165 ;; complicated if
166 ;; COMPUTE-EFFECTIVE-METHOD (and
167 ;; presumably MAKE-METHOD-LAMBDA) is
168 ;; adjusted to match.
169 ;;
170 ;; On the other hand, it's a start,
171 ;; because without this calls to
172 ;; MAKE-METHOD in method combination
173 ;; where one of the methods is of a
174 ;; user-defined class don't work at
175 ;; all. -- CSR, 2006-08-05
178 mf))))
190 method-alist wrappers)
191 method))))
199 "EFFECTIVE-METHOD-GENSYM-~D"
203 new)))
221 ;; Otherwise the METHOD-COMBINATION slot is not bound.
238 ;; FIXME: Ick. Shared idiom, too, with stuff in cache.lisp
249 ,@check-applicable-keywords
254 ,@check-applicable-keywords
263 ;; the PROGN is here to defend against premature macroexpansion by
264 ;; RESTART-CASE.
272 generic-function form method-alist-p wrappers-p)))
274 'fast-method-call
275 t))
281 generic-function form method-alist-p wrappers-p)
286 generic-function form method-alist-p wrappers-p)
292 ;;; CMUCL comment (2003-10-15):
293 ;;;
294 ;;; This function is called via the GET-FUNCTION mechanism on forms
295 ;;; of an emf lambda. First value returned replaces FORM in the emf
296 ;;; lambda. Second value is a list of variable names that become
297 ;;; closure variables.
304 metatypes applyp gensym
306 generic-function form method-alist-p wrappers-p))
311 generic-function form method-alist-p wrappers-p)))
317 .dfun-rest-arg. .keyargs-start. .valid-keys.)
328 generic-function form))))
333 generic-function form))
353 generic-function effective-method)))
358 method-alist-p wrappers-p))
361 metatypes applyp
362 method-alist-p wrappers-p))
373 (.meth.
375 (.meth-list.
424 ;; By returning a single call-method `form' here we enable
425 ;; an important implementation-specific optimization; that
426 ;; is, we can use the fast method function directly as the
427 ;; effective method function.
428 ;;
429 ;; However, the requirement by ANSI (CLHS 7.6.5) on generic
430 ;; function argument checking inhibits this, as we don't
431 ;; perform this checking in fast-method-functions given
432 ;; that they are not solely used for effective method
433 ;; functions, but also in combination, when they should not
434 ;; perform argument checks.
438 ;; the PROGN inhibits the above optimization
440 call-method)))
455 main-effective-method))))))
456 \f
457 ;;; helper code for checking keywords in generic function calls.
492 ~{~S~^, ~} (valid keys are ~{~S~^, ~}).~@:>"
503 ;; only the leftmost :ALLOW-OTHER-KEYS has any effect
510 \f
511 ;;;; the STANDARD method combination type. This is coded by hand
512 ;;;; (rather than with DEFINE-METHOD-COMBINATION) for bootstrapping
513 ;;;; and efficiency reasons. Note that the definition of the
514 ;;;; FIND-METHOD-COMBINATION-METHOD appears in the file
515 ;;;; defcombin.lisp. This is because EQL methods can't appear in the
516 ;;;; bootstrap.
517 ;;;;
518 ;;;; The DEFCLASS for the METHOD-COMBINATION and
519 ;;;; STANDARD-METHOD-COMBINATION classes has to appear here for this
520 ;;;; reason. This code must conform to the code in the file
521 ;;;; defcombin.lisp, look there for more details.
525 combin
526 applicable-methods))
531 method
532 format-control
533 format-arguments)))
538 format-control
539 format-arguments)))