| blob | 8ec70650f4f903a3715ba007c596cc41a81d0b0c |
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
26 #|
28 The CommonLoops evaluator is meta-circular.
30 Most of the code in PCL is methods on generic functions, including
31 most of the code that actually implements generic functions and method
32 lookup.
34 So, we have a classic bootstrapping problem. The solution to this is
35 to first get a cheap implementation of generic functions running,
36 these are called early generic functions. These early generic
37 functions and the corresponding early methods and early method lookup
38 are used to get enough of the system running that it is possible to
39 create real generic functions and methods and implement real method
41 !FIX-EARLY-GENERIC-FUNCTIONS is called to convert all the early generic
42 functions to real generic functions.
44 The cheap generic functions are built using the same
45 FUNCALLABLE-INSTANCE objects that real generic functions are made out of.
46 This means that as PCL is being bootstrapped, the cheap generic
47 function objects which are being created are the same objects which
48 will later be real generic functions. This is good because:
50 - we can keep pointers to the cheap generic function objects
51 during booting because those pointers will still point to
52 the right object after the generic functions are all fixed up.
54 This file defines the DEFMETHOD macro and the mechanism used to expand
55 it. This includes the mechanism for processing the body of a method.
56 DEFMETHOD basically expands into a call to LOAD-DEFMETHOD, which
57 basically calls ADD-METHOD to add the method to the generic function.
58 These expansions can be loaded either during bootstrapping or when PCL
59 is fully up and running.
61 An important effect of this arrangement is it means we can compile
62 files with DEFMETHOD forms in them in a completely running PCL, but
63 then load those files back in during bootstrapping. This makes
64 development easier. It also means there is only one set of code for
65 processing DEFMETHOD. Bootstrapping works by being sure to have
66 LOAD-METHOD be careful to call only primitives which work during
67 bootstrapping.
69 |#
72 ensure-generic-function-using-class
73 add-method remove-method))
79 ;;; For each of the early functions, arrange to have it point to its
80 ;;; early definition. Do this in a way that makes sure that if we
81 ;;; redefine one of the early definitions the redefinition will take
82 ;;; effect. This makes development easier.
90 name))))
92 ;;; *!GENERIC-FUNCTION-FIXUPS* is used by !FIX-EARLY-GENERIC-FUNCTIONS
93 ;;; to convert the few functions in the bootstrap which are supposed
94 ;;; to be generic functions but can't be early on.
95 ;;;
96 ;;; each entry is a list of name and lambda-list, class names as
97 ;;; specializers, and method body function name.
102 real-add-method))
106 real-remove-method))
110 real-get-method))
113 &key generic-function-class environment
116 real-ensure-gf-using-class--generic-function)
118 &key generic-function-class environment
121 real-ensure-gf-using-class--null))
125 real-make-method-lambda))
129 real-make-method-specializers-form))
133 real-parse-specializer-using-class))
137 real-unparse-specializer-using-class))
140 lambda-expression
141 lambda-list environment)
143 real-make-method-initargs-form))
147 standard-compute-effective-method))))
148 \f
178 DEFGENERIC: ~S~:@>"
181 ;; FIXME: this list is slightly weird.
182 ;; ANSI (on the DEFGENERIC page) in one
183 ;; place allows only OPTIMIZE; in
184 ;; another place gives this list of
185 ;; disallowed declaration specifiers.
186 ;; This seems to be the only place where
187 ;; the FUNCTION declaration is
188 ;; mentioned; TYPE seems to be missing.
189 ;; Very strange. -- CSR, 2002-10-21
191 inline notinline special))
194 is not allowed inside DEFGENERIC."
200 spec))))
201 (:method-combination
207 symbol: ~S"
211 (:argument-precedence-order
217 :ARGUMENT-PRECEDENCE-ORDER clause."
222 :ARGUMENT-PRECEDENCE-ORDER clause: ~
223 ~S and ~S"
233 (:method
236 ;; ANSI requires that unsupported things must get a
237 ;; PROGRAM-ERROR.
264 :name fun-name
272 fun-name
273 :lambda-list lambda-list
274 :definition-source source-location
275 initargs))
279 ()
287 :format-control
288 "~@<invalid ~S ~_in the generic function lambda list ~S~:>"
291 auxp aux morep more-context more-count)
298 ;; no defaults allowed for &OPTIONAL arguments
301 ;; no defaults allowed for &KEY arguments
307 ;; no &AUX allowed
310 lambda-list))
311 ;; Oh, *puhlease*... not specifically as per section 3.4.2 of
312 ;; the ANSI spec, but the CMU CL &MORE extension does not
313 ;; belong here!
315 \f
321 ;; :compile-toplevel is needed for subsequent forms
322 ;; :execute is needed for references to itself inside the body
324 ;; KLUDGE: this double expansion is quite a monumental
325 ;; workaround: it comes about because of a fantastic interaction
326 ;; between the processing rules of CLHS 3.2.3.1 and the
327 ;; bizarreness of MAKE-METHOD-LAMBDA.
328 ;;
329 ;; MAKE-METHOD-LAMBDA can be called by the user, and if the
330 ;; lambda itself doesn't refer to outside bindings the return
331 ;; value must be compileable in the null lexical environment.
332 ;; However, the function must also refer somehow to the
333 ;; associated method object, so that it can call NO-NEXT-METHOD
334 ;; with the appropriate arguments if there is no next method --
335 ;; but when the function is generated, the method object doesn't
336 ;; exist yet.
337 ;;
338 ;; In order to resolve this issue, we insert a literal cons cell
339 ;; into the body of the method lambda, return the same cons cell
340 ;; as part of the second (initargs) return value of
341 ;; MAKE-METHOD-LAMBDA, and a method on INITIALIZE-INSTANCE fills
342 ;; in the cell when the method is created. However, this
343 ;; strategy depends on having a fresh cons cell for every method
344 ;; lambda, which (without the workaround below) is skewered by
345 ;; the processing in CLHS 3.2.3.1, which permits implementations
346 ;; to macroexpand the bodies of EVAL-WHEN forms with both
347 ;; :COMPILE-TOPLEVEL and :LOAD-TOPLEVEL only once. The
348 ;; expansion below forces the double expansion in those cases,
349 ;; while expanding only once in the common case.
360 lambda-list body env)))
376 ;;; Take a name which is either a generic function name or a list specifying
377 ;;; a SETF generic function (like: (SETF <generic-function-name>)). Return
378 ;;; the prototype instance of the method-class for that generic function.
379 ;;;
380 ;;; If there is no generic function by that name, this returns the
381 ;;; default value, the prototype instance of the class
382 ;;; STANDARD-METHOD. This default value is also returned if the spec
383 ;;; names an ordinary function or even a macro. In effect, this leaves
384 ;;; the signalling of the appropriate error until load time.
385 ;;;
386 ;;; Note: During bootstrapping, this function is allowed to return NIL.
393 ; error at load time.
398 \f
399 ;;; These are used to communicate the method name and lambda-list to
400 ;;; MAKE-METHOD-LAMBDA-INTERNAL.
405 proto-gf
406 proto-method
407 qualifiers
408 lambda-list
409 body
410 env)
420 proto-gf proto-method method-function-lambda
421 initargs env))
423 proto-gf proto-method specializers env)))
425 ;; Note: We could DECLAIM the ftype of the generic function
426 ;; here, since ANSI specifies that we create it if it does
427 ;; not exist. However, I chose not to, because I think it's
428 ;; more useful to support a style of programming where every
429 ;; generic function has an explicit DEFGENERIC and any typos
430 ;; in DEFMETHODs are warned about. Otherwise
431 ;;
432 ;; (DEFGENERIC FOO-BAR-BLETCH (X))
433 ;; (DEFMETHOD FOO-BAR-BLETCH ((X HASH-TABLE)) ..)
434 ;; (DEFMETHOD FOO-BRA-BLETCH ((X SIMPLE-VECTOR)) ..)
435 ;; (DEFMETHOD FOO-BAR-BLETCH ((X VECTOR)) ..)
436 ;; (DEFMETHOD FOO-BAR-BLETCH ((X ARRAY)) ..)
437 ;; (DEFMETHOD FOO-BAR-BLETCH ((X LIST)) ..)
438 ;;
439 ;; compiles without raising an error and runs without
440 ;; raising an error (since SIMPLE-VECTOR cases fall through
441 ;; to VECTOR) but still doesn't do what was intended. I hate
442 ;; that kind of bug (code which silently gives the wrong
443 ;; answer), so we don't do a DECLAIM here. -- WHN 20000229
445 unspecialized-lambda-list
449 initargs-form)))))))
456 method-class-name initargs-form)
459 fn-lambda)
472 specializers)
483 ;; CONSTANT-FORM-VALUE? What I
484 ;; kind of want to know, though,
485 ;; is what happens if we don't do
486 ;; this for some slow-method
487 ;; function because of a hairy
488 ;; lexenv -- is the only bad
489 ;; effect that the method
490 ;; function ends up unnamed? If
491 ;; so, couldn't we arrange to
492 ;; name it later?
494 specl))
495 specializers))
503 name qualifiers `',specls
504 unspecialized-lambda-list method-class-name
506 #',mname
509 name qualifiers
510 specializers
511 #+nil
517 specializers))
518 unspecialized-lambda-list
519 method-class-name
520 initargs-form))))
524 method-class-name initargs-form)
526 ',method-class-name
527 ',name
528 ',qualifiers
529 ,specializers-form
530 ',unspecialized-lambda-list
531 ,initargs-form
540 proto-method
541 method-function-lambda
542 initargs
543 env))))
546 method-lambda initargs env)
551 is not a lambda form."
552 method-lambda))
559 ;;; When bootstrapping PCL MAKE-METHOD-LAMBDA starts out as a regular
560 ;;; functions: REAL-MAKE-METHOD-LAMBDA set to the fdefinition of
561 ;;; MAKE-METHOD-LAMBDA. Once generic functions are born, the
562 ;;; REAL-MAKE-METHOD lambda is used as the body of the default method.
563 ;;; MAKE-METHOD-LAMBDA-INTERNAL is split out into a separate function
564 ;;; so that changing it in a live image is easy, and changes actually
565 ;;; take effect.
583 is not a lambda form."
584 method-lambda))
587 ;; We have the %METHOD-NAME declaration in the place where we expect it only
588 ;; if there is are no non-standard prior MAKE-METHOD-LAMBDA methods -- or
589 ;; unless they're fantastically unintrusive.
592 ;; Macroexpansion caused by code-walking may call make-method-lambda and
593 ;; end up with wrong values
601 ;; the method-cell is a way of communicating what method a
602 ;; method-function implements, for the purpose of
603 ;; NO-NEXT-METHOD. We need something that can be shared
604 ;; between function and initargs, but not something that
605 ;; will be coalesced as a constant (because we are naughty,
606 ;; oh yes) with the expansion of any other methods in the
607 ;; same file. -- CSR, 2007-05-30
613 parameters
614 specializers))
618 ;; These declarations seem to be used by PCL to pass
619 ;; information to itself; when I tried to delete 'em
620 ;; ca. 0.6.10 it didn't work. I'm not sure how
621 ;; they work, but note the (VAR-DECLARATION '%CLASS ..)
622 ;; expression in CAN-OPTIMIZE-ACCESS1. -- WHN 2000-12-30
627 parameters
628 specializers))
629 ;; These TYPE declarations weren't in the original
630 ;; PCL code, but the Python compiler likes them a
631 ;; lot. (We're telling the compiler about our
632 ;; knowledge of specialized argument types so that
633 ;; it can avoid run-time type dispatch overhead,
634 ;; which can be a huge win for Python.)
635 ;;
636 ;; KLUDGE: when I tried moving these to
637 ;; ADD-METHOD-DECLARATIONS, things broke. No idea
638 ;; why. -- CSR, 2004-06-16
642 par spec specials env))
643 parameters
644 specializers))))
646 ;; Remove the documentation string and insert the
647 ;; appropriate class declarations. The documentation
648 ;; string is removed to make it easy for us to insert
649 ;; new declarations later, they will just go after the
650 ;; CADR of the method lambda. The class declarations
651 ;; are inserted to communicate the class of the method's
652 ;; arguments to the code walk.
654 ;; The default ignorability of method parameters
655 ;; doesn't seem to be specified by ANSI. PCL had
656 ;; them basically ignorable but was a little
657 ;; inconsistent. E.g. even though the two
658 ;; method definitions
659 ;; (DEFMETHOD FOO ((X T) (Y T)) "Z")
660 ;; (DEFMETHOD FOO ((X T) Y) "Z")
661 ;; are otherwise equivalent, PCL treated Y as
662 ;; ignorable in the first definition but not in the
663 ;; second definition. We make all required
664 ;; parameters ignorable as a way of systematizing
665 ;; the old PCL behavior. -- WHN 2000-11-24
667 ,class-declarations
668 ,@declarations
687 parameters-setqd)
689 required-parameters
690 env
691 slots)
693 walked-declarations
694 walked-documentation)
705 ,slot-name-lists
715 aux))))
718 (,lambda-list .method-args. .next-methods.
719 :call-next-method-p
725 ,@walked-declarations
728 %parameter-binding-modified))
732 %parameter-binding-modified))
747 name)
753 ;; FIXME: Document CLASS-EQ specializers.
755 :format-control
756 "~@<~S is not a valid parameter specializer name.~@:>"
769 result
771 specializer generic-function))))
779 ;; FIXME: this HANDLER-CASE is a bit of a hammer to crack a nut:
780 ;; the idea is that we want to unparse permissively, so that the
781 ;; lazy (or rather the "portable") specializer extender (who
782 ;; does not define methods on these new SBCL-specific MOP
783 ;; functions) can still subclass specializer and define methods
784 ;; without everything going wrong. Making it cleaner and
785 ;; clearer that that is what we are defending against would be
786 ;; nice. -- CSR, 2007-06-01
793 class-name
794 type))
795 type))
798 specializer generic-function)))
804 ;;; a helper function for creating Python-friendly type declarations
805 ;;; in DEFMETHOD forms.
806 ;;;
807 ;;; We're too lazy to cons up a new environment for this, so we just pass in
808 ;;; the list of locally declared specials in addition to the old environment.
813 ;; KLUDGE: ANSI, in its wisdom, says that
814 ;; EQL-SPECIALIZER-FORMs in EQL specializers are evaluated at
815 ;; DEFMETHOD expansion time. Thus, although one might think
816 ;; that in
817 ;; (DEFMETHOD FOO ((X PACKAGE)
818 ;; (Y (EQL 12))
819 ;; ..))
820 ;; the PACKAGE and (EQL 12) forms are both parallel type
821 ;; names, they're not, as is made clear when you do
822 ;; (DEFMETHOD FOO ((X PACKAGE)
823 ;; (Y (EQL 'BAR)))
824 ;; ..)
825 ;; where Y needs to be a symbol named "BAR", not some cons
826 ;; made by (CONS 'QUOTE 'BAR). I.e. when the
827 ;; EQL-SPECIALIZER-FORM is (EQL 'X), it requires an argument
828 ;; to be of type (EQL X). It'd be easy to transform one to
829 ;; the other, but it'd be somewhat messier to do so while
830 ;; ensuring that the EQL-SPECIALIZER-FORM is only EVAL'd
831 ;; once. (The new code wouldn't be messy, but it'd require a
832 ;; big transformation of the old code.) So instead we punt.
833 ;; -- WHN 20000610
836 ;; KLUDGE: For some low-level implementation
837 ;; classes, perhaps because of some problems related
838 ;; to the incomplete integration of PCL into SBCL's
839 ;; type system, some specializer classes can't be
840 ;; declared as argument types. E.g.
841 ;; (DEFMETHOD FOO ((X SLOT-OBJECT))
842 ;; (DECLARE (TYPE SLOT-OBJECT X))
843 ;; ..)
844 ;; loses when
845 ;; (DEFSTRUCT BAR A B)
846 ;; (FOO (MAKE-BAR))
847 ;; perhaps because of the way that STRUCTURE-OBJECT
848 ;; inherits both from SLOT-OBJECT and from
849 ;; SB-KERNEL:INSTANCE. In an effort to sweep such
850 ;; problems under the rug, we exclude these problem
851 ;; cases by blacklisting them here. -- WHN 2001-01-19
855 ;; KLUDGE: PCL, in its wisdom, sometimes calls methods with
856 ;; types which don't match their specializers. (Specifically,
857 ;; it calls ENSURE-CLASS-USING-CLASS (T NULL) with a non-NULL
858 ;; second argument.) Hopefully it only does this kind of
859 ;; weirdness when bootstrapping.. -- WHN 20000610
864 ;; Don't declare types for special variables -- our rebinding magic
865 ;; for SETQ cases don't work right there as SET, (SETF SYMBOL-VALUE),
866 ;; etc. make things undecidable.
869 ;; Otherwise, we can usually make Python very happy.
870 ;;
871 ;; KLUDGE: Since INFO doesn't work right for class objects here,
872 ;; and they are valid specializers, see if the specializer is
873 ;; a named class, and use the name in that case -- otherwise
874 ;; the class instance is ok, since info will just return NIL, NIL.
875 ;;
876 ;; We still need to deal with the class case too, but at
877 ;; least #.(find-class 'integer) and integer as equivalent
878 ;; specializers with this.
885 specializer))
899 ;; CLASS can be null here if the user has
900 ;; erroneously tried to use a defined type as a
901 ;; specializer; it can be a non-SYSTEM-CLASS if
902 ;; the user defines a type and calls (SETF
903 ;; FIND-CLASS) in a consistent way.
912 ;; don't declare CLOS classes as parameters;
913 ;; it's too expensive.
916 ;; we can get here, and still not have a failure
917 ;; case, by doing MOP programming like (PROGN
918 ;; (ENSURE-CLASS 'FOO) (DEFMETHOD BAR ((X FOO))
919 ;; ...)). Best to let the user know we haven't
920 ;; been able to extract enough information:
922 "~@<can't find type for specializer ~S in ~S.~@:>"
923 specializer-nameoid
929 ;;; For passing a list (groveled by the walker) of the required
930 ;;; parameters whose bindings are modified in the method body to the
931 ;;; optimized-slot-value* macros.
935 method-args
936 next-methods
947 next-method-call
948 args
949 rest-arg
958 parameters-setqd applyp method-cell))
959 &body body
963 ;; always provide the lexical function NEXT-METHOD-P.
964 ;; I would think this to be a good candidate for declaring INLINE
965 ;; but that's not the way it was done before.
976 `((%check-cnm-args cnm-args
977 ,method-args
979 nil)
987 ',method-cell
996 ;; Can't easily provide a RETRY restart here, as the return value here is
997 ;; for the method, not the generic function.
999 method args)))
1017 call-method-args)
1019 value)
1040 pv
1041 next-method-call
1042 arg-info)
1045 value)
1049 ;; The two variants of INVOKE-FAST-METHOD-CALL differ in how REST-ARGs
1050 ;; are handled. The first one will get REST-ARG as a single list (as
1051 ;; the last argument), and will thus need to use APPLY. The second one
1052 ;; will get them as a &MORE argument, so we can pass the arguments
1053 ;; directly with MULTIPLE-VALUE-CALL and %MORE-ARG-VALUES.
1062 more-context
1063 more-count
1069 ,@required-args
1072 ;; The cases with only small amounts of required arguments passed
1073 ;; are probably very common, and special-casing speeds them up by
1074 ;; a factor of 2 with very little effect on the other
1075 ;; cases. Though it'd be nice to have the generic case be equally
1076 ;; fast.
1083 ,@required-args
1094 \f
1095 ;;;; effective method functions
1101 ;;; This function was in the CMU CL version of PCL (ca Debian 2.4.8)
1102 ;;; without explanation. It appears to be intended for debugging, so
1103 ;;; it might be useful someday, so I haven't deleted it.
1104 ;;; But it isn't documented and isn't used for anything now, so
1105 ;;; I've conditionalized it out of the base system. -- WHN 19991213
1106 #+sb-show
1139 ,@more-arg
1142 ,restp
1143 ,@required-args
1148 ;; "What," you may wonder, "do these next two clauses do?" In that
1149 ;; case, you are not a PCL implementor, for they considered this to
1150 ;; be self-documenting.:-| Or CSR, for that matter, since he can
1151 ;; also figure it out by looking at it without breaking stride. For
1152 ;; the rest of us, though: From what the code is doing with .SLOTS.
1153 ;; and whatnot, evidently it's implementing SLOT-VALUEish and
1154 ;; GET-SLOT-VALUEish things. Then we can reason backwards and
1155 ;; conclude that setting EMF to a FIXNUM is an optimized way to
1156 ;; represent these slot access operations.
1167 value)))))
1175 ;; (In cmucl-2.4.8 there was a commented-out third ,@(WHEN
1176 ;; ...) clause here to handle SLOT-BOUNDish stuff. Since
1177 ;; there was no explanation and presumably the code is 10+
1178 ;; years stale, I simply deleted it. -- WHN)
1179 )))
1181 ;;; Before SBCL 0.9.16.7 instead of
1182 ;;; INVOKE-NARROW-EFFECTIVE-METHOD-FUNCTION we passed a (THE (OR
1183 ;;; FUNCTION METHOD-CALL FAST-METHOD-CALL) EMF) form as the EMF. Now,
1184 ;;; to make less work for the compiler we take a path that doesn't
1185 ;;; involve the slot-accessor clause (where EMF is a FIXNUM) at all.
1200 ,@more-arg
1203 ,restp
1204 ,@required-args
1208 emf-n restp required-args))
1231 args)
1254 args))))))
1257 args
1269 value)))
1286 \f
1289 method-cell
1290 cnm-args)
1293 ,next-method-call
1305 ,@args
1311 call-next-method-p
1312 setq-p
1313 parameters-setqd
1314 method-cell
1315 applyp))
1316 &body body
1336 nil)
1338 ,next-method-call
1340 ,method-cell
1341 cnm-args))))
1347 ;;; CMUCL comment (Gerd Moellmann):
1348 ;;;
1349 ;;; The standard says it's an error if CALL-NEXT-METHOD is called with
1350 ;;; arguments, and the set of methods applicable to those arguments is
1351 ;;; different from the set of methods applicable to the original
1352 ;;; method arguments. (According to Barry Margolin, this rule was
1353 ;;; probably added to ensure that before and around methods are always
1354 ;;; run before primary methods.)
1355 ;;;
1356 ;;; This could be optimized for the case that the generic function
1357 ;;; doesn't have hairy methods, does have standard method combination,
1358 ;;; is a standard generic function, there are no methods defined on it
1359 ;;; for COMPUTE-APPLICABLE-METHODS and probably a lot more of such
1360 ;;; preconditions. That looks hairy and is probably not worth it,
1361 ;;; because this check will never be fast.
1363 ;; 1. Check for no arguments.
1368 ;; 2. Requirement arguments pairwise: if all are EQL, the applicable
1369 ;; methods must be the same. This takes care of the relatively common
1370 ;; case of twiddling with &KEY arguments without being horribly
1371 ;; expensive.
1378 ;; 3. Only then do the full check.
1383 ~{~S~^, ~} to call-next-method is different from ~
1384 the set of methods ~S applicable to the original ~
1385 method argument~P ~{~S~^, ~}.~@:>"
1389 ;; FIXME: replacing this entire mess with DESTRUCTURING-BIND would correct
1390 ;; problems similar to those already solved by a correct implementation
1391 ;; of DESTRUCTURING-BIND, such as incorrect binding order:
1392 ;; e.g. (macroexpand-1 '(bind-args ((&optional (x nil xsp)) args) (form)))
1393 ;; -> (LET* ((.ARGS-TAIL. ARGS) (XSP (NOT (NULL .ARGS-TAIL.))) (X ...)))
1394 ;; It's mostly irrelevant unless a method uses CALL-NEXT-METHOD though.
1410 "encountered the non-standard lambda list keyword ~S"
1411 var)))
1412 nil)
1460 ,@bindings
1461 (.dummy0.
1473 ;; FIXME: Do we want to export this symbol? Or maybe use an
1474 ;; (ERROR 'SIMPLE-PROGRAM-ERROR) form?
1477 return tail))
1481 ;; method definition
1483 ;; a list of all required parameters whose bindings might be
1484 ;; modified in the method body.
1491 ;; hierarchy: nil -> :simple -> T.
1494 form)
1496 ;; The walker will split (SETQ A 1 B 2) to
1497 ;; separate (SETQ A 1) and (SETQ B 2) forms, so we
1498 ;; only need to handle the simple case of SETQ
1499 ;; here.
1504 ;; Note that we don't need to check for
1505 ;; %VARIABLE-REBINDING declarations like is
1506 ;; done in CAN-OPTIMIZE-ACCESS1, since the
1507 ;; bindings that will have that declation will
1508 ;; never be SETQd.
1510 ;; If a parameter binding is shadowed by
1511 ;; another binding it won't have a %CLASS
1512 ;; declaration anymore, and this won't get
1513 ;; executed.
1515 form)
1519 form)
1527 form))
1531 ;;; FIXME: the walker's rewriting of the source code causes
1532 ;;; trouble when doing code coverage. The rewrites should be
1533 ;;; removed, and the same operations done using
1534 ;;; compiler-macros or tranforms.
1536 walked-lambda
1537 method-lambda)
1538 call-next-method-p
1540 parameters-setqd)))))
1548 \f
1558 new-value)
1560 \f
1566 #+nil
1570 ll initargs source-location)))
1574 initargs source-location)
1583 :name gf-spec
1584 :new-location source-location
1585 :old-method method
1588 gf-spec qualifiers specializers lambda-list
1589 :definition-source source-location
1590 initargs)))
1593 ;; FIXME: should be STYLE-WARNING?
1595 "~&At the time the method with qualifiers ~:S and~%~
1596 specializers ~:S on the generic function ~S~%~
1597 was compiled, the method-class for that generic function was~%~
1598 ~S. But, the method class is now ~S, this~%~
1599 may mean that this method was compiled improperly.~%"
1600 qualifiers specializers gf-spec
1602 method))
1630 \f
1660 x)))
1669 After &REST, a DEFGENERIC lambda-list ~
1683 keywords keyword-parameters)
1692 old-ftype))))
1707 keywords)
1710 *))))
1711 \f
1712 ;;;; early generic function support
1716 ;; CLHS doesn't specify &allow-other-keys here but I guess the supposition
1717 ;; is that they'll be checked by ENSURE-GENERIC-FUNCTION-USING-CLASS.
1718 ;; Except we don't do that either, so I think the blame, if any, lies there
1719 ;; for not catching errant keywords.
1731 existing fun-name all-keys)))))
1735 'simple-program-error
1786 arg-info-precedence
1787 arg-info-metatypes
1788 arg-info-number-optional
1789 arg-info-key/rest-p
1790 arg-info-keys ;nil no &KEY or &REST allowed
1791 ;(k1 k2 ..) Each method must accept these &KEY arguments.
1792 ;T must have &KEY or &REST
1794 gf-info-simple-accessor-type ; nil, reader, writer, boundp
1797 gf-info-static-c-a-m-emf
1799 gf-info-fast-mf-p)
1817 ;;; Create a gf lambda list from a method lambda list
1823 argument-precedence-order)
1847 existing methods of ~S."
1848 lambda-list gf))))
1851 lambda-list
1867 arg-info))
1877 to the generic function~2I~_~S;~I~_~
1878 but ~?~:>"
1888 "the method has ~A required arguments than the generic function."
1892 "the method has ~A optional arguments than the generic function."
1896 "the method and generic function differ in whether they accept~_~
1900 allow-other-keys-p
1903 ~S."
1904 gf-keywords)))))))
1913 ;;; FIXME: we don't actually need this; we could test for the exact
1914 ;;; class and deal with it as appropriate. In fact we probably don't
1915 ;;; need it anyway because we only use this for METHOD-SPECIALIZERS on
1916 ;;; the standard reader method for METHOD-SPECIALIZERS. Probably.
1928 standard-writer-method standard-boundp-method
1929 global-reader-method global-writer-method
1930 global-boundp-method))
1960 nil)))
2008 nil)
2014 ;; FIXME: this test will eventually be
2015 ;; superseded by the *internal-pcl...* test,
2016 ;; above. While we are in a process of
2017 ;; transition, however, it should probably
2018 ;; remain.
2024 #'make-method-lambda
2035 arg-info)
2037 ;;; This is the early definition of ENSURE-GENERIC-FUNCTION-USING-CLASS.
2038 ;;;
2039 ;;; The STATIC-SLOTS field of the funcallable instances used as early
2040 ;;; generic functions is used to store the early methods and early
2041 ;;; discriminator code for the early generic function. The static
2042 ;;; slots field of the fins contains a list whose:
2043 ;;; CAR - a list of the early methods on this early gf
2044 ;;; CADR - the early discriminator code for this method
2047 lambda-list-p)
2048 argument-precedence-order
2049 definition-source
2050 documentation
2056 existing)
2060 argument-precedence-order definition-source
2061 documentation)
2069 argument-precedence-order definition-source
2070 documentation))))
2073 function argument-precedence-order source-location
2074 documentation)
2078 fin
2104 :lambda-list lambda-list
2107 fin))
2117 new-value)
2123 dfun)))
2126 ;; Check that we are under the lock.
2127 #+sb-thread
2132 new-state))))
2133 dfun)
2168 nil)
2183 class nor a symbol that names a class."
2187 ;; FIXME: reference MOP documentation -- this is an
2188 ;; additional requirement on our users
2205 method-class)
2210 ;; Use the existing lambda-list, if any. It is reasonable to do eg.
2211 ;;
2212 ;; (if (fboundp name)
2213 ;; (ensure-generic-function name)
2214 ;; (ensure-generic-function name :lambda-list '(foo)))
2215 ;;
2216 ;; in which case we end up here with no lambda-list in the first leg.
2220 t)
2229 ;; FIXME: Ideally we would like to not clobber it, but because generic
2230 ;; functions assert their FTYPEs callers believing the FTYPE are left with
2231 ;; unsafe assumptions. Hence the clobbering. Be quiet when the new type
2232 ;; is a subtype of the old one, though -- even though the type is not
2233 ;; trusted anymore, the warning is still not quite as interesting.
2237 for the same name with ~S.~:@>"
2238 fun-name 'ftype
2243 fun-name))
2247 fun-name
2248 &rest all-keys
2253 ;; KLUDGE: the above macro does SETQ on GENERIC-FUNCTION-CLASS,
2254 ;; which is what makes the next line work
2263 fun-name
2264 &rest all-keys
2275 \f
2282 ;;; FIXME: this function took on a slightly greater role than it
2283 ;;; previously had around 2005-11-02, when CSR fixed the bug whereby
2284 ;;; having more than one subclass of standard-generic-function caused
2285 ;;; the whole system to die horribly through a metacircle in
2286 ;;; GF-ARG-INFO. The fix is to be slightly more disciplined about
2287 ;;; calling accessor methods -- we call GET-GENERIC-FUN-INFO when
2288 ;;; computing discriminating functions, so we need to be careful about
2289 ;;; having a base case for the recursion, and we provide that with the
2290 ;;; STANDARD-GENERIC-FUNCTION case below. However, we are not (yet)
2291 ;;; as disciplined as CLISP's CLOS/MOP, and it would be nice to get to
2292 ;;; that stage, where all potentially dangerous cases are enumerated
2293 ;;; and stopped. -- CSR, 2005-11-02.
2295 ;; values nreq applyp metatypes nkeys arg-info
2302 metatypes
2303 arg-info))
2312 nkeys
2313 arg-info))))
2324 &key slot-name object-class method-class-function
2325 definition-source)
2328 ;; Figure out whether we got class objects or class names as the
2329 ;; specializers and set parsed and unparsed appropriately. If we
2330 ;; got class objects, then we can compute unparsed, but if we got
2331 ;; class names we don't try to compute parsed.
2332 ;;
2333 ;; Note that the use of not symbolp in this call to every should be
2334 ;; read as 'classp' we can't use classp itself because it doesn't
2335 ;; exist yet.
2340 specializers))
2342 parsed ()))
2352 ;; the parsed specializers. This is used by
2353 ;; EARLY-METHOD-SPECIALIZERS to cache the parse.
2354 ;; Note that this only comes into play when there is
2355 ;; more than one early method on an early gf.
2356 parsed
2358 ;; A list to which REAL-MAKE-A-METHOD can be applied
2359 ;; to make a real method corresponding to this early
2360 ;; one.
2363 initargs doc)
2369 result)))
2374 definition-source)
2385 :slot-definition slot-definition
2389 initargs)
2390 :definition-source definition-source
2391 initargs)))
2411 ;;; Fetch the specializers of an early method. This is basically just
2412 ;;; a simple accessor except that when the second argument is t, this
2413 ;;; converts the specializers from symbols into class objects. The
2414 ;;; class objects are cached in the early method, this makes
2415 ;;; bootstrapping faster because the class objects only have to be
2416 ;;; computed once.
2417 ;;;
2418 ;;; NOTE:
2419 ;;; The second argument should only be passed as T by
2420 ;;; early-lookup-method. This is to implement the rule that only when
2421 ;;; there is more than one early method on a generic function is the
2422 ;;; conversion from class names to class objects done. This
2423 ;;; corresponds to the fact that we are only allowed to have one
2424 ;;; method on any generic function up until the time classes exist.
2449 specializers arglist &rest initargs
2450 &key documentation definition-source
2453 ;; argument here because the default,
2454 ;; STANDARD-GENERIC-FUNCTION, is right for all early generic
2455 ;; functions. (See REAL-ADD-NAMED-METHOD)
2465 specializers initargs documentation
2470 ;;; This is the early version of ADD-METHOD. Later this will become a
2471 ;;; generic function. See !FIX-EARLY-GENERIC-FUNCTIONS which has
2472 ;;; special knowledge about ADD-METHOD.
2485 ;;; This is the early version of REMOVE-METHOD. See comments on
2486 ;;; the early version of ADD-METHOD.
2500 ;;; This is the early version of GET-METHOD. See comments on the early
2501 ;;; version of ADD-METHOD.
2507 specializers)
2509 specializers))
2514 nil))
2519 ;; Rearrange *!EARLY-GENERIC-FUNCTIONS* to speed up
2520 ;; FIX-EARLY-GENERIC-FUNCTIONS.
2527 generic-function-methods
2528 method-specializers
2529 specializerp
2530 specializer-type
2531 specializer-class
2532 slot-definition-location
2533 slot-definition-name
2534 class-slots
2535 gf-arg-info
2536 class-precedence-list
2537 slot-boundp-using-class
2539 slot-value-using-class
2540 structure-class-p
2541 standard-class-p
2542 funcallable-standard-class-p
2543 specializerp)))
2554 early-method))))
2557 early-method t))
2584 next-methods))
2589 ()
2590 lambda-list
2591 specializers
2592 initargs
2593 nil)))
2600 \f
2601 ;;; PARSE-DEFMETHOD is used by DEFMETHOD to parse the &REST argument
2602 ;;; into the 'real' arguments. This is where the syntax of DEFMETHOD
2603 ;;; is really implemented.
2625 \f
2630 parameters))
2636 lambda-list))
2642 specializers))
2648 required-parameters))
2652 ()
2665 ;; non-standard lambda-list-keywords are errors.
2669 keyword ~S~%"
2671 ;; no multiple &rest x &rest bla specifying
2675 specialized-lambda-list keyword ~S~%"
2677 ;; And no placing &key in front of &optional, either.
2681 keyword ~S~%"
2683 ;; When we are at a lambda-list keyword, the parameters
2684 ;; don't include the lambda-list keyword; the lambda-list
2685 ;; does include the lambda-list keyword; and no
2686 ;; specializers are allowed to follow the lambda-list
2687 ;; keywords (at least for now).
2698 specialized-lambda-list-keywords)
2701 specialized-lambda-list-keywords)))))
2703 :format-control
2704 "in a specialized-lambda-list, excactly one ~
2705 variable must follow &REST.~%"
2709 ()
2710 ())))
2712 ;; After a lambda-list keyword there can be no specializers.
2715 supplied-keywords
2716 allowed-keywords)
2719 ()
2720 ())))
2724 ;; Check for valid arguments.
2736 \f
2738 \f
2739 ;;; FIXME: In here there was a #-CMU definition of SYMBOL-MACROLET
2740 ;;; which used %WALKER stuff. That suggests to me that maybe the code
2741 ;;; walker stuff was only used for implementing stuff like that; maybe
2742 ;;; it's not needed any more? Hunt down what it was used for and see.
2749 form)))
2758 ,in
2762 slot-entry
2766 slot-entry
2768 `(,var-name
2770 slots)
2780 ,in
2785 slots)