X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcompiler%2Fpolicy.lisp;h=e780e4bc9af9e5cf2ca4ec553d82bce02927e54f;hb=db0691b05cc99ce010ecae78bb532b594aea1859;hp=d4cd154cd4d1c47147b4a26aa22a0649f3e0ec07;hpb=204f2fa9771ad9e55718dc76205afec7d11b3011;p=sbcl.git

diff --git a/src/compiler/policy.lisp b/src/compiler/policy.lisp
index d4cd154..e780e4b 100644
--- a/src/compiler/policy.lisp
+++ b/src/compiler/policy.lisp
@@ -25,7 +25,7 @@
 ;;; names of recognized optimization policy qualities
 (defvar *policy-qualities*) ; (initialized at cold init)
 
-;;; Is X the name of an optimization quality?
+;;; Is X the name of an optimization policy quality?
 (defun policy-quality-name-p (x)
   (memq x *policy-qualities*))
 
@@ -90,7 +90,7 @@
 ;;; FIXME: Doing this is slightly flaky (since we can't do it right
 ;;; without all the headaches of true code walking), and it shouldn't
 ;;; be necessary with modern Python anyway, as long as POLICY-QUALITY
-;;; is properly DEFKNOWNed to have no side-effects so that it can be
+;;; is properly DEFKNOWNed to have no side effects so that it can be
 ;;; optimized away if unused. So this should probably go away.
 (defun policy-qualities-used-by (expr)
   (let ((result nil))