0.6.9.13:

[sbcl.git] / src / code / fop.lisp

diff --git a/src/code/fop.lisp b/src/code/fop.lisp
index 9522737..b47aa4e 100644 (file)
--- a/src/code/fop.lisp
+++ b/src/code/fop.lisp
@@ -2,9 +2,6 @@
 
 (in-package "SB!IMPL")
 
-(file-comment
-  "$Header$")
-
 ;;; Define NAME as a fasl operation, with op-code FOP-CODE. PUSHP
 ;;; describes what the body does to the fop stack:
 ;;;   :NOPE
@@ -209,13 +206,15 @@
                                                 ,n-size
                                                 ,n-package)))))))))
 
-  ;; Note: CMU CL had FOP-SYMBOL-SAVE and FOP-SMALL-SYMBOL-SAVE, but since they
-  ;; made the behavior of the fasloader depend on the *PACKAGE* variable, not
-  ;; only were they a pain to support (because they required various hacks to
-  ;; handle *PACKAGE*-manipulation forms) they were basically broken by design,
-  ;; because ANSI gives the user so much flexibility in manipulating *PACKAGE*
-  ;; at load-time that no reasonable hacks could possibly make things work
-  ;; right. The ones used in CMU CL certainly didn't, as shown by e.g.
+  ;; Note: CMU CL had FOP-SYMBOL-SAVE and FOP-SMALL-SYMBOL-SAVE, but
+  ;; since they made the behavior of the fasloader depend on the
+  ;; *PACKAGE* variable, not only were they a pain to support (because
+  ;; they required various hacks to handle *PACKAGE*-manipulation
+  ;; forms) they were basically broken by design, because ANSI gives
+  ;; the user so much flexibility in manipulating *PACKAGE* at
+  ;; load-time that no reasonable hacks could possibly make things
+  ;; work right. The ones used in CMU CL certainly didn't, as shown by
+  ;; e.g.
   ;;   (IN-PACKAGE :CL-USER)
   ;;     (DEFVAR CL::*FOO* 'FOO-VALUE)
   ;;     (EVAL-WHEN (:COMPILE-TOPLEVEL :LOAD-TOPLEVEL :EXECUTE)
@@ -605,9 +604,9 @@
     (sb!vm:sanctify-for-execution component)
     component))
 
-;;; This a no-op except in cold load. (In ordinary warm load, everything
-;;; involved with function definition can be handled nicely by ordinary
-;;; toplevel code.)
+;;; This a no-op except in cold load. (In ordinary warm load,
+;;; everything involved with function definition can be handled nicely
+;;; by ordinary toplevel code.)
 (define-fop (fop-fset 74 nil)
   (pop-stack)
   (pop-stack))