| blob | 97cc2880d9c40817262363777dd77052980cfbdd |
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.
259 ;; Hmm. This is similar to BECOME-DEFINED-FUN-NAME
260 ;; except that it doesn't clear an :ASSUMED-TYPE. Should it?
268 :name fun-name
276 fun-name
277 :lambda-list lambda-list
278 :definition-source source-location
279 initargs))
283 ()
291 :format-control
292 "~@<invalid ~S ~_in the generic function lambda list ~S~:>"
296 lambda-list
302 ;; no defaults allowed for &OPTIONAL arguments
305 ;; no defaults allowed for &KEY arguments
310 \f
316 ;; :compile-toplevel is needed for subsequent forms
317 ;; :execute is needed for references to itself inside the body
319 ;; KLUDGE: this double expansion is quite a monumental
320 ;; workaround: it comes about because of a fantastic interaction
321 ;; between the processing rules of CLHS 3.2.3.1 and the
322 ;; bizarreness of MAKE-METHOD-LAMBDA.
323 ;;
324 ;; MAKE-METHOD-LAMBDA can be called by the user, and if the
325 ;; lambda itself doesn't refer to outside bindings the return
326 ;; value must be compileable in the null lexical environment.
327 ;; However, the function must also refer somehow to the
328 ;; associated method object, so that it can call NO-NEXT-METHOD
329 ;; with the appropriate arguments if there is no next method --
330 ;; but when the function is generated, the method object doesn't
331 ;; exist yet.
332 ;;
333 ;; In order to resolve this issue, we insert a literal cons cell
334 ;; into the body of the method lambda, return the same cons cell
335 ;; as part of the second (initargs) return value of
336 ;; MAKE-METHOD-LAMBDA, and a method on INITIALIZE-INSTANCE fills
337 ;; in the cell when the method is created. However, this
338 ;; strategy depends on having a fresh cons cell for every method
339 ;; lambda, which (without the workaround below) is skewered by
340 ;; the processing in CLHS 3.2.3.1, which permits implementations
341 ;; to macroexpand the bodies of EVAL-WHEN forms with both
342 ;; :COMPILE-TOPLEVEL and :LOAD-TOPLEVEL only once. The
343 ;; expansion below forces the double expansion in those cases,
344 ;; while expanding only once in the common case.
355 lambda-list body env)))
371 ;;; Take a name which is either a generic function name or a list specifying
372 ;;; a SETF generic function (like: (SETF <generic-function-name>)). Return
373 ;;; the prototype instance of the method-class for that generic function.
374 ;;;
375 ;;; If there is no generic function by that name, this returns the
376 ;;; default value, the prototype instance of the class
377 ;;; STANDARD-METHOD. This default value is also returned if the spec
378 ;;; names an ordinary function or even a macro. In effect, this leaves
379 ;;; the signalling of the appropriate error until load time.
380 ;;;
381 ;;; Note: During bootstrapping, this function is allowed to return NIL.
388 ; error at load time.
393 \f
394 ;;; These are used to communicate the method name and lambda-list to
395 ;;; MAKE-METHOD-LAMBDA-INTERNAL.
400 proto-gf
401 proto-method
402 qualifiers
403 lambda-list
404 body
405 env)
412 specializers)
419 proto-gf proto-method method-function-lambda
420 initargs env))
422 proto-gf proto-method specializers env)))
424 ;; Note: We could DECLAIM the ftype of the generic function
425 ;; here, since ANSI specifies that we create it if it does
426 ;; not exist. However, I chose not to, because I think it's
427 ;; more useful to support a style of programming where every
428 ;; generic function has an explicit DEFGENERIC and any typos
429 ;; in DEFMETHODs are warned about. Otherwise
430 ;;
431 ;; (DEFGENERIC FOO-BAR-BLETCH (X))
432 ;; (DEFMETHOD FOO-BAR-BLETCH ((X HASH-TABLE)) ..)
433 ;; (DEFMETHOD FOO-BRA-BLETCH ((X SIMPLE-VECTOR)) ..)
434 ;; (DEFMETHOD FOO-BAR-BLETCH ((X VECTOR)) ..)
435 ;; (DEFMETHOD FOO-BAR-BLETCH ((X ARRAY)) ..)
436 ;; (DEFMETHOD FOO-BAR-BLETCH ((X LIST)) ..)
437 ;;
438 ;; compiles without raising an error and runs without
439 ;; raising an error (since SIMPLE-VECTOR cases fall through
440 ;; to VECTOR) but still doesn't do what was intended. I hate
441 ;; that kind of bug (code which silently gives the wrong
442 ;; answer), so we don't do a DECLAIM here. -- WHN 20000229
444 unspecialized-lambda-list
448 initargs-form)))))))
455 method-class-name initargs-form)
458 fn-lambda)
471 specializers)
482 ;; CONSTANT-FORM-VALUE? What I
483 ;; kind of want to know, though,
484 ;; is what happens if we don't do
485 ;; this for some slow-method
486 ;; function because of a hairy
487 ;; lexenv -- is the only bad
488 ;; effect that the method
489 ;; function ends up unnamed? If
490 ;; so, couldn't we arrange to
491 ;; name it later?
493 specl))
494 specializers))
502 name qualifiers `',specls
503 unspecialized-lambda-list method-class-name
505 #',mname
508 name qualifiers
509 specializers
510 #+nil
516 specializers))
517 unspecialized-lambda-list
518 method-class-name
519 initargs-form))))
523 method-class-name initargs-form)
525 ',method-class-name
526 ',name
527 ',qualifiers
528 ,specializers-form
529 ',unspecialized-lambda-list
530 ,initargs-form
539 proto-method
540 method-function-lambda
541 initargs
542 env))))
545 method-lambda initargs env)
550 is not a lambda form."
551 method-lambda))
558 ;;; When bootstrapping PCL MAKE-METHOD-LAMBDA starts out as a regular
559 ;;; functions: REAL-MAKE-METHOD-LAMBDA set to the fdefinition of
560 ;;; MAKE-METHOD-LAMBDA. Once generic functions are born, the
561 ;;; REAL-MAKE-METHOD lambda is used as the body of the default method.
562 ;;; MAKE-METHOD-LAMBDA-INTERNAL is split out into a separate function
563 ;;; so that changing it in a live image is easy, and changes actually
564 ;;; take effect.
582 is not a lambda form."
583 method-lambda))
586 ;; We have the %METHOD-NAME declaration in the place where we expect it only
587 ;; if there is are no non-standard prior MAKE-METHOD-LAMBDA methods -- or
588 ;; unless they're fantastically unintrusive.
591 ;; Macroexpansion caused by code-walking may call make-method-lambda and
592 ;; end up with wrong values
600 ;; the method-cell is a way of communicating what method a
601 ;; method-function implements, for the purpose of
602 ;; NO-NEXT-METHOD. We need something that can be shared
603 ;; between function and initargs, but not something that
604 ;; will be coalesced as a constant (because we are naughty,
605 ;; oh yes) with the expansion of any other methods in the
606 ;; same file. -- CSR, 2007-05-30
612 parameters
613 specializers))
617 ;; These declarations seem to be used by PCL to pass
618 ;; information to itself; when I tried to delete 'em
619 ;; ca. 0.6.10 it didn't work. I'm not sure how
620 ;; they work, but note the (VAR-DECLARATION '%CLASS ..)
621 ;; expression in CAN-OPTIMIZE-ACCESS1. -- WHN 2000-12-30
626 parameters
627 specializers))
628 ;; These TYPE declarations weren't in the original
629 ;; PCL code, but the Python compiler likes them a
630 ;; lot. (We're telling the compiler about our
631 ;; knowledge of specialized argument types so that
632 ;; it can avoid run-time type dispatch overhead,
633 ;; which can be a huge win for Python.)
634 ;;
635 ;; KLUDGE: when I tried moving these to
636 ;; ADD-METHOD-DECLARATIONS, things broke. No idea
637 ;; why. -- CSR, 2004-06-16
641 par spec specials env))
642 parameters
643 specializers))))
645 ;; Remove the documentation string and insert the
646 ;; appropriate class declarations. The documentation
647 ;; string is removed to make it easy for us to insert
648 ;; new declarations later, they will just go after the
649 ;; CADR of the method lambda. The class declarations
650 ;; are inserted to communicate the class of the method's
651 ;; arguments to the code walk.
653 ;; The default ignorability of method parameters
654 ;; doesn't seem to be specified by ANSI. PCL had
655 ;; them basically ignorable but was a little
656 ;; inconsistent. E.g. even though the two
657 ;; method definitions
658 ;; (DEFMETHOD FOO ((X T) (Y T)) "Z")
659 ;; (DEFMETHOD FOO ((X T) Y) "Z")
660 ;; are otherwise equivalent, PCL treated Y as
661 ;; ignorable in the first definition but not in the
662 ;; second definition. We make all required
663 ;; parameters ignorable as a way of systematizing
664 ;; the old PCL behavior. -- WHN 2000-11-24
666 ,class-declarations
667 ,@declarations
686 parameters-setqd)
688 required-parameters
689 env
690 slots)
692 walked-declarations
693 walked-documentation)
704 ,slot-name-lists
714 aux))))
717 (,lambda-list .method-args. .next-methods.
718 :call-next-method-p
724 ,@walked-declarations
727 %parameter-binding-modified))
731 %parameter-binding-modified))
746 name)
752 ;; FIXME: Document CLASS-EQ specializers.
754 :format-control
755 "~@<~S is not a valid parameter specializer name.~@:>"
768 result
770 specializer generic-function))))
778 ;; FIXME: this HANDLER-CASE is a bit of a hammer to crack a nut:
779 ;; the idea is that we want to unparse permissively, so that the
780 ;; lazy (or rather the "portable") specializer extender (who
781 ;; does not define methods on these new SBCL-specific MOP
782 ;; functions) can still subclass specializer and define methods
783 ;; without everything going wrong. Making it cleaner and
784 ;; clearer that that is what we are defending against would be
785 ;; nice. -- CSR, 2007-06-01
792 class-name
793 type))
794 type))
797 specializer generic-function)))
803 ;;; a helper function for creating Python-friendly type declarations
804 ;;; in DEFMETHOD forms.
805 ;;;
806 ;;; We're too lazy to cons up a new environment for this, so we just pass in
807 ;;; the list of locally declared specials in addition to the old environment.
812 ;; KLUDGE: ANSI, in its wisdom, says that
813 ;; EQL-SPECIALIZER-FORMs in EQL specializers are evaluated at
814 ;; DEFMETHOD expansion time. Thus, although one might think
815 ;; that in
816 ;; (DEFMETHOD FOO ((X PACKAGE)
817 ;; (Y (EQL 12))
818 ;; ..))
819 ;; the PACKAGE and (EQL 12) forms are both parallel type
820 ;; names, they're not, as is made clear when you do
821 ;; (DEFMETHOD FOO ((X PACKAGE)
822 ;; (Y (EQL 'BAR)))
823 ;; ..)
824 ;; where Y needs to be a symbol named "BAR", not some cons
825 ;; made by (CONS 'QUOTE 'BAR). I.e. when the
826 ;; EQL-SPECIALIZER-FORM is (EQL 'X), it requires an argument
827 ;; to be of type (EQL X). It'd be easy to transform one to
828 ;; the other, but it'd be somewhat messier to do so while
829 ;; ensuring that the EQL-SPECIALIZER-FORM is only EVAL'd
830 ;; once. (The new code wouldn't be messy, but it'd require a
831 ;; big transformation of the old code.) So instead we punt.
832 ;; -- WHN 20000610
835 ;; KLUDGE: For some low-level implementation
836 ;; classes, perhaps because of some problems related
837 ;; to the incomplete integration of PCL into SBCL's
838 ;; type system, some specializer classes can't be
839 ;; declared as argument types. E.g.
840 ;; (DEFMETHOD FOO ((X SLOT-OBJECT))
841 ;; (DECLARE (TYPE SLOT-OBJECT X))
842 ;; ..)
843 ;; loses when
844 ;; (DEFSTRUCT BAR A B)
845 ;; (FOO (MAKE-BAR))
846 ;; perhaps because of the way that STRUCTURE-OBJECT
847 ;; inherits both from SLOT-OBJECT and from
848 ;; SB-KERNEL:INSTANCE. In an effort to sweep such
849 ;; problems under the rug, we exclude these problem
850 ;; cases by blacklisting them here. -- WHN 2001-01-19
854 ;; KLUDGE: PCL, in its wisdom, sometimes calls methods with
855 ;; types which don't match their specializers. (Specifically,
856 ;; it calls ENSURE-CLASS-USING-CLASS (T NULL) with a non-NULL
857 ;; second argument.) Hopefully it only does this kind of
858 ;; weirdness when bootstrapping.. -- WHN 20000610
863 ;; Don't declare types for special variables -- our rebinding magic
864 ;; for SETQ cases don't work right there as SET, (SETF SYMBOL-VALUE),
865 ;; etc. make things undecidable.
868 ;; Otherwise, we can usually make Python very happy.
869 ;;
870 ;; KLUDGE: Since INFO doesn't work right for class objects here,
871 ;; and they are valid specializers, see if the specializer is
872 ;; a named class, and use the name in that case -- otherwise
873 ;; the class instance is ok, since info will just return NIL, NIL.
874 ;;
875 ;; We still need to deal with the class case too, but at
876 ;; least #.(find-class 'integer) and integer as equivalent
877 ;; specializers with this.
884 specializer))
898 ;; CLASS can be null here if the user has
899 ;; erroneously tried to use a defined type as a
900 ;; specializer; it can be a non-SYSTEM-CLASS if
901 ;; the user defines a type and calls (SETF
902 ;; FIND-CLASS) in a consistent way.
911 ;; don't declare CLOS classes as parameters;
912 ;; it's too expensive.
915 ;; we can get here, and still not have a failure
916 ;; case, by doing MOP programming like (PROGN
917 ;; (ENSURE-CLASS 'FOO) (DEFMETHOD BAR ((X FOO))
918 ;; ...)). Best to let the user know we haven't
919 ;; been able to extract enough information:
921 "~@<can't find type for specializer ~S in ~S.~@:>"
922 specializer-nameoid
928 ;;; For passing a list (groveled by the walker) of the required
929 ;;; parameters whose bindings are modified in the method body to the
930 ;;; optimized-slot-value* macros.
934 method-args
935 next-methods
946 next-method-call
947 args
948 rest-arg
957 parameters-setqd applyp method-cell))
958 &body body
962 ;; always provide the lexical function NEXT-METHOD-P.
963 ;; I would think this to be a good candidate for declaring INLINE
964 ;; but that's not the way it was done before.
975 `((%check-cnm-args cnm-args
976 ,method-args
978 nil)
986 ',method-cell
995 ;; Can't easily provide a RETRY restart here, as the return value here is
996 ;; for the method, not the generic function.
998 method args)))
1016 call-method-args)
1018 value)
1039 pv
1040 next-method-call
1041 arg-info)
1044 value)
1048 ;; The two variants of INVOKE-FAST-METHOD-CALL differ in how REST-ARGs
1049 ;; are handled. The first one will get REST-ARG as a single list (as
1050 ;; the last argument), and will thus need to use APPLY. The second one
1051 ;; will get them as a &MORE argument, so we can pass the arguments
1052 ;; directly with MULTIPLE-VALUE-CALL and %MORE-ARG-VALUES.
1061 more-context
1062 more-count
1068 ,@required-args
1071 ;; The cases with only small amounts of required arguments passed
1072 ;; are probably very common, and special-casing speeds them up by
1073 ;; a factor of 2 with very little effect on the other
1074 ;; cases. Though it'd be nice to have the generic case be equally
1075 ;; fast.
1082 ,@required-args
1093 \f
1094 ;;;; effective method functions
1100 ;;; This function was in the CMU CL version of PCL (ca Debian 2.4.8)
1101 ;;; without explanation. It appears to be intended for debugging, so
1102 ;;; it might be useful someday, so I haven't deleted it.
1103 ;;; But it isn't documented and isn't used for anything now, so
1104 ;;; I've conditionalized it out of the base system. -- WHN 19991213
1105 #+sb-show
1138 ,@more-arg
1141 ,restp
1142 ,@required-args
1147 ;; "What," you may wonder, "do these next two clauses do?" In that
1148 ;; case, you are not a PCL implementor, for they considered this to
1149 ;; be self-documenting.:-| Or CSR, for that matter, since he can
1150 ;; also figure it out by looking at it without breaking stride. For
1151 ;; the rest of us, though: From what the code is doing with .SLOTS.
1152 ;; and whatnot, evidently it's implementing SLOT-VALUEish and
1153 ;; GET-SLOT-VALUEish things. Then we can reason backwards and
1154 ;; conclude that setting EMF to a FIXNUM is an optimized way to
1155 ;; represent these slot access operations.
1166 value)))))
1174 ;; (In cmucl-2.4.8 there was a commented-out third ,@(WHEN
1175 ;; ...) clause here to handle SLOT-BOUNDish stuff. Since
1176 ;; there was no explanation and presumably the code is 10+
1177 ;; years stale, I simply deleted it. -- WHN)
1178 )))
1180 ;;; Before SBCL 0.9.16.7 instead of
1181 ;;; INVOKE-NARROW-EFFECTIVE-METHOD-FUNCTION we passed a (THE (OR
1182 ;;; FUNCTION METHOD-CALL FAST-METHOD-CALL) EMF) form as the EMF. Now,
1183 ;;; to make less work for the compiler we take a path that doesn't
1184 ;;; involve the slot-accessor clause (where EMF is a FIXNUM) at all.
1199 ,@more-arg
1202 ,restp
1203 ,@required-args
1207 emf-n restp required-args))
1230 args)
1253 args))))))
1256 args
1268 value)))
1285 \f
1288 method-cell
1289 cnm-args)
1292 ,next-method-call
1304 ,@args
1310 call-next-method-p
1311 setq-p
1312 parameters-setqd
1313 method-cell
1314 applyp))
1315 &body body
1335 nil)
1337 ,next-method-call
1339 ,method-cell
1340 cnm-args))))
1346 ;;; CMUCL comment (Gerd Moellmann):
1347 ;;;
1348 ;;; The standard says it's an error if CALL-NEXT-METHOD is called with
1349 ;;; arguments, and the set of methods applicable to those arguments is
1350 ;;; different from the set of methods applicable to the original
1351 ;;; method arguments. (According to Barry Margolin, this rule was
1352 ;;; probably added to ensure that before and around methods are always
1353 ;;; run before primary methods.)
1354 ;;;
1355 ;;; This could be optimized for the case that the generic function
1356 ;;; doesn't have hairy methods, does have standard method combination,
1357 ;;; is a standard generic function, there are no methods defined on it
1358 ;;; for COMPUTE-APPLICABLE-METHODS and probably a lot more of such
1359 ;;; preconditions. That looks hairy and is probably not worth it,
1360 ;;; because this check will never be fast.
1362 ;; 1. Check for no arguments.
1367 ;; 2. Requirement arguments pairwise: if all are EQL, the applicable
1368 ;; methods must be the same. This takes care of the relatively common
1369 ;; case of twiddling with &KEY arguments without being horribly
1370 ;; expensive.
1377 ;; 3. Only then do the full check.
1382 ~{~S~^, ~} to call-next-method is different from ~
1383 the set of methods ~S applicable to the original ~
1384 method argument~P ~{~S~^, ~}.~@:>"
1388 ;; FIXME: replacing this entire mess with DESTRUCTURING-BIND would correct
1389 ;; problems similar to those already solved by a correct implementation
1390 ;; of DESTRUCTURING-BIND, such as incorrect binding order:
1391 ;; e.g. (macroexpand-1 '(bind-args ((&optional (x nil xsp)) args) (form)))
1392 ;; -> (LET* ((.ARGS-TAIL. ARGS) (XSP (NOT (NULL .ARGS-TAIL.))) (X ...)))
1393 ;; It's mostly irrelevant unless a method uses CALL-NEXT-METHOD though.
1409 "encountered the non-standard lambda list keyword ~S"
1410 var)))
1411 nil)
1459 ,@bindings
1460 (.dummy0.
1472 ;; FIXME: Do we want to export this symbol? Or maybe use an
1473 ;; (ERROR 'SIMPLE-PROGRAM-ERROR) form?
1476 return tail))
1480 ;; method definition
1482 ;; a list of all required parameters whose bindings might be
1483 ;; modified in the method body.
1490 ;; hierarchy: nil -> :simple -> T.
1493 form)
1495 ;; The walker will split (SETQ A 1 B 2) to
1496 ;; separate (SETQ A 1) and (SETQ B 2) forms, so we
1497 ;; only need to handle the simple case of SETQ
1498 ;; here.
1503 ;; Note that we don't need to check for
1504 ;; %VARIABLE-REBINDING declarations like is
1505 ;; done in CAN-OPTIMIZE-ACCESS1, since the
1506 ;; bindings that will have that declation will
1507 ;; never be SETQd.
1509 ;; If a parameter binding is shadowed by
1510 ;; another binding it won't have a %CLASS
1511 ;; declaration anymore, and this won't get
1512 ;; executed.
1514 form)
1518 form)
1526 form))
1530 ;;; FIXME: the walker's rewriting of the source code causes
1531 ;;; trouble when doing code coverage. The rewrites should be
1532 ;;; removed, and the same operations done using
1533 ;;; compiler-macros or tranforms.
1535 walked-lambda
1536 method-lambda)
1537 call-next-method-p
1539 parameters-setqd)))))
1547 \f
1557 new-value)
1559 \f
1565 #+nil
1569 ll initargs source-location)))
1573 initargs source-location)
1582 :name gf-spec
1583 :new-location source-location
1584 :old-method method
1587 gf-spec qualifiers specializers lambda-list
1588 :definition-source source-location
1589 initargs)))
1592 ;; FIXME: should be STYLE-WARNING?
1594 "~&At the time the method with qualifiers ~:S and~%~
1595 specializers ~:S on the generic function ~S~%~
1596 was compiled, the method-class for that generic function was~%~
1597 ~S. But, the method class is now ~S, this~%~
1598 may mean that this method was compiled improperly.~%"
1599 qualifiers specializers gf-spec
1601 method))
1629 \f
1632 ;; We say "&MUMBLE is not allowed in a generic function lambda list"
1633 ;; whether this is called by DEFMETHOD or DEFGENERIC.
1634 ;; [It is used for either. Why else recognize and silently ignore &AUX?]
1638 :silent t
1644 ;; FIXME: this does more than return an FTYPE from a lambda list -
1645 ;; it unions the type with an existing ctype object. It needs a better name,
1646 ;; and to be reimplemented as "union and call sb-c::ftype-from-lambda-list".
1657 old-ftype))))
1672 keywords)
1675 *))))
1676 \f
1677 ;;;; early generic function support
1681 ;; CLHS doesn't specify &allow-other-keys here but I guess the supposition
1682 ;; is that they'll be checked by ENSURE-GENERIC-FUNCTION-USING-CLASS.
1683 ;; Except we don't do that either, so I think the blame, if any, lies there
1684 ;; for not catching errant keywords.
1696 existing fun-name all-keys)))))
1700 'simple-program-error
1751 arg-info-precedence
1752 arg-info-metatypes
1753 arg-info-number-optional
1754 arg-info-key/rest-p
1755 arg-info-keys ;nil no &KEY or &REST allowed
1756 ;(k1 k2 ..) Each method must accept these &KEY arguments.
1757 ;T must have &KEY or &REST
1759 gf-info-simple-accessor-type ; nil, reader, writer, boundp
1762 gf-info-static-c-a-m-emf
1764 gf-info-fast-mf-p)
1782 ;;; Create a gf lambda list from a method lambda list
1791 argument-precedence-order)
1815 existing methods of ~S."
1816 lambda-list gf))))
1819 lambda-list
1835 arg-info))
1845 to the generic function~2I~_~S;~I~_~
1846 but ~?~:>"
1856 "the method has ~A required arguments than the generic function."
1860 "the method has ~A optional arguments than the generic function."
1864 "the method and generic function differ in whether they accept~_~
1871 ~S."
1872 gf-keywords)))))))
1881 ;;; FIXME: we don't actually need this; we could test for the exact
1882 ;;; class and deal with it as appropriate. In fact we probably don't
1883 ;;; need it anyway because we only use this for METHOD-SPECIALIZERS on
1884 ;;; the standard reader method for METHOD-SPECIALIZERS. Probably.
1896 standard-writer-method standard-boundp-method
1897 global-reader-method global-writer-method
1898 global-boundp-method))
1928 nil)))
1976 nil)
1982 ;; FIXME: this test will eventually be
1983 ;; superseded by the *internal-pcl...* test,
1984 ;; above. While we are in a process of
1985 ;; transition, however, it should probably
1986 ;; remain.
1992 #'make-method-lambda
2003 arg-info)
2005 ;;; This is the early definition of ENSURE-GENERIC-FUNCTION-USING-CLASS.
2006 ;;;
2007 ;;; The STATIC-SLOTS field of the funcallable instances used as early
2008 ;;; generic functions is used to store the early methods and early
2009 ;;; discriminator code for the early generic function. The static
2010 ;;; slots field of the fins contains a list whose:
2011 ;;; CAR - a list of the early methods on this early gf
2012 ;;; CADR - the early discriminator code for this method
2015 lambda-list-p)
2016 argument-precedence-order
2017 definition-source
2018 documentation
2024 existing)
2028 argument-precedence-order definition-source
2029 documentation)
2037 argument-precedence-order definition-source
2038 documentation))))
2041 function argument-precedence-order source-location
2042 documentation)
2046 fin
2072 :lambda-list lambda-list
2075 fin))
2085 new-value)
2091 dfun)))
2094 ;; Check that we are under the lock.
2095 #+sb-thread
2100 new-state))))
2101 dfun)
2136 nil)
2151 class nor a symbol that names a class."
2155 ;; FIXME: reference MOP documentation -- this is an
2156 ;; additional requirement on our users
2173 method-class)
2178 ;; Use the existing lambda-list, if any. It is reasonable to do eg.
2179 ;;
2180 ;; (if (fboundp name)
2181 ;; (ensure-generic-function name)
2182 ;; (ensure-generic-function name :lambda-list '(foo)))
2183 ;;
2184 ;; in which case we end up here with no lambda-list in the first leg.
2188 t)
2197 ;; FIXME: Ideally we would like to not clobber it, but because generic
2198 ;; functions assert their FTYPEs callers believing the FTYPE are left with
2199 ;; unsafe assumptions. Hence the clobbering. Be quiet when the new type
2200 ;; is a subtype of the old one, though -- even though the type is not
2201 ;; trusted anymore, the warning is still not quite as interesting.
2205 for the same name with ~S.~:@>"
2206 fun-name 'ftype
2211 fun-name))
2215 fun-name
2216 &rest all-keys
2221 ;; KLUDGE: the above macro does SETQ on GENERIC-FUNCTION-CLASS,
2222 ;; which is what makes the next line work
2231 fun-name
2232 &rest all-keys
2243 \f
2250 ;;; FIXME: this function took on a slightly greater role than it
2251 ;;; previously had around 2005-11-02, when CSR fixed the bug whereby
2252 ;;; having more than one subclass of standard-generic-function caused
2253 ;;; the whole system to die horribly through a metacircle in
2254 ;;; GF-ARG-INFO. The fix is to be slightly more disciplined about
2255 ;;; calling accessor methods -- we call GET-GENERIC-FUN-INFO when
2256 ;;; computing discriminating functions, so we need to be careful about
2257 ;;; having a base case for the recursion, and we provide that with the
2258 ;;; STANDARD-GENERIC-FUNCTION case below. However, we are not (yet)
2259 ;;; as disciplined as CLISP's CLOS/MOP, and it would be nice to get to
2260 ;;; that stage, where all potentially dangerous cases are enumerated
2261 ;;; and stopped. -- CSR, 2005-11-02.
2263 ;; values nreq applyp metatypes nkeys arg-info
2270 metatypes
2271 arg-info))
2280 nkeys
2281 arg-info))))
2292 &key slot-name object-class method-class-function
2293 definition-source)
2296 ;; Figure out whether we got class objects or class names as the
2297 ;; specializers and set parsed and unparsed appropriately. If we
2298 ;; got class objects, then we can compute unparsed, but if we got
2299 ;; class names we don't try to compute parsed.
2300 ;;
2301 ;; Note that the use of not symbolp in this call to every should be
2302 ;; read as 'classp' we can't use classp itself because it doesn't
2303 ;; exist yet.
2308 specializers))
2310 parsed ()))
2320 ;; the parsed specializers. This is used by
2321 ;; EARLY-METHOD-SPECIALIZERS to cache the parse.
2322 ;; Note that this only comes into play when there is
2323 ;; more than one early method on an early gf.
2324 parsed
2326 ;; A list to which REAL-MAKE-A-METHOD can be applied
2327 ;; to make a real method corresponding to this early
2328 ;; one.
2331 initargs doc)
2337 result)))
2342 definition-source)
2353 :slot-definition slot-definition
2357 initargs)
2358 :definition-source definition-source
2359 initargs)))
2379 ;;; Fetch the specializers of an early method. This is basically just
2380 ;;; a simple accessor except that when the second argument is t, this
2381 ;;; converts the specializers from symbols into class objects. The
2382 ;;; class objects are cached in the early method, this makes
2383 ;;; bootstrapping faster because the class objects only have to be
2384 ;;; computed once.
2385 ;;;
2386 ;;; NOTE:
2387 ;;; The second argument should only be passed as T by
2388 ;;; early-lookup-method. This is to implement the rule that only when
2389 ;;; there is more than one early method on a generic function is the
2390 ;;; conversion from class names to class objects done. This
2391 ;;; corresponds to the fact that we are only allowed to have one
2392 ;;; method on any generic function up until the time classes exist.
2417 specializers arglist &rest initargs
2418 &key documentation definition-source
2421 ;; argument here because the default,
2422 ;; STANDARD-GENERIC-FUNCTION, is right for all early generic
2423 ;; functions. (See REAL-ADD-NAMED-METHOD)
2433 specializers initargs documentation
2438 ;;; This is the early version of ADD-METHOD. Later this will become a
2439 ;;; generic function. See !FIX-EARLY-GENERIC-FUNCTIONS which has
2440 ;;; special knowledge about ADD-METHOD.
2453 ;;; This is the early version of REMOVE-METHOD. See comments on
2454 ;;; the early version of ADD-METHOD.
2468 ;;; This is the early version of GET-METHOD. See comments on the early
2469 ;;; version of ADD-METHOD.
2475 specializers)
2477 specializers))
2482 nil))
2485 ;; minor KLUDGE: a separate code component for this function allows GCing
2486 ;; a few symbols and their associated code that would otherwise be retained:
2487 ;; *!EARLY-{GENERIC-}FUNCTIONS*, *!GENERIC-FUNCTION-FIXUPS*
2495 ;; Rearrange *!EARLY-GENERIC-FUNCTIONS* to speed up
2496 ;; FIX-EARLY-GENERIC-FUNCTIONS.
2503 generic-function-methods
2504 method-specializers
2505 specializerp
2506 specializer-type
2507 specializer-class
2508 slot-definition-location
2509 slot-definition-name
2510 class-slots
2511 gf-arg-info
2512 class-precedence-list
2513 slot-boundp-using-class
2515 slot-value-using-class
2516 structure-class-p
2517 standard-class-p
2518 funcallable-standard-class-p
2519 specializerp)))
2530 early-method))))
2533 early-method t))
2562 ()
2563 lambda-list
2564 specializers
2565 initargs
2566 nil)))
2573 \f
2574 ;;; PARSE-DEFMETHOD is used by DEFMETHOD to parse the &REST argument
2575 ;;; into the 'real' arguments. This is where the syntax of DEFMETHOD
2576 ;;; is really implemented.
2598 \f
2603 parameters))
2609 lambda-list))
2615 specializers))
2621 required-parameters))
2625 ()
2638 ;; non-standard lambda-list-keywords are errors.
2642 keyword ~S~%"
2644 ;; no multiple &rest x &rest bla specifying
2648 specialized-lambda-list keyword ~S~%"
2650 ;; And no placing &key in front of &optional, either.
2654 keyword ~S~%"
2656 ;; When we are at a lambda-list keyword, the parameters
2657 ;; don't include the lambda-list keyword; the lambda-list
2658 ;; does include the lambda-list keyword; and no
2659 ;; specializers are allowed to follow the lambda-list
2660 ;; keywords (at least for now).
2671 specialized-lambda-list-keywords)
2674 specialized-lambda-list-keywords)))))
2676 :format-control
2677 "in a specialized-lambda-list, excactly one ~
2678 variable must follow &REST.~%"
2682 ()
2683 ())))
2685 ;; After a lambda-list keyword there can be no specializers.
2688 supplied-keywords
2689 allowed-keywords)
2692 ()
2693 ())))
2697 ;; Check for valid arguments.
2709 \f
2711 \f
2712 ;;; FIXME: In here there was a #-CMU definition of SYMBOL-MACROLET
2713 ;;; which used %WALKER stuff. That suggests to me that maybe the code
2714 ;;; walker stuff was only used for implementing stuff like that; maybe
2715 ;;; it's not needed any more? Hunt down what it was used for and see.
2722 form)))
2731 ,in
2735 slot-entry
2739 slot-entry
2741 `(,var-name
2743 slots)
2753 ,in
2758 slots)