Changeset 14028

Timestamp:

07/31/12 12:26:35 (9 years ago)

Author:

ehuelsmann

Message:

When creating a generic function on top of an autoloader, don't
resolve the autoloader: that's probably what we are already doing
(but the function doesn't get replaced until autoloading has succeeded).

File:

• trunk/abcl/src/org/armedbear/lisp/clos.lisp (modified) (2 diffs)

trunk/abcl/src/org/armedbear/lisp/clos.lisp

@@ -1654 +1654 @@
                                 documentation
                                 &allow-other-keys)
-  (when (autoloadp function-name)
-    (resolve function-name))
   (setf all-keys (copy-list all-keys))  ; since we modify it
   (remf all-keys :generic-function-class)
@@ -1678 +1676 @@
         (progn
           (when (and (null *clos-booting*)
-                     (fboundp function-name))
+                     (and (fboundp function-name)
+                          ;; since we're overwriting an autoloader,
+                          ;; we're probably meant to redefine it,
+                          ;; so throwing an error here might be a bad idea.
+                          ;; also, resolving the symbol isn't
+                          ;; a good option either: we've seen that lead to
+                          ;; recursive loading of the same file
+                          (not (autoloadp function-name))))
             (error 'program-error
                    :format-control "~A already names an ordinary function, macro, or special operator."