X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcode%2Fbyte-interp.lisp;h=738f9013fd582e15cc99c9f7e69183d62f970fab;hb=3b45a7b66afe95080562d266dd447b1286abece0;hp=2de7dfd27735a0332640081ec6566e4ce0030aac;hpb=0c54eadbdfd0a1ec1e47e067de53bdf4a06330c5;p=sbcl.git

diff --git a/src/code/byte-interp.lisp b/src/code/byte-interp.lisp
index 2de7dfd..738f901 100644
--- a/src/code/byte-interp.lisp
+++ b/src/code/byte-interp.lisp
@@ -50,16 +50,13 @@
 	  ((nil)))
 	`(function ,(res) *))))))
 
-;;;; the evaluation stack
+;;;; the 'evaluation stack'
+;;;;
+;;;; (The name dates back to CMU CL, when it was used for the IR1
+;;;; interpreted implementation of EVAL. In SBCL >=0.7.0, it's just
+;;;; the byte interpreter stack.)
 
-;;; the interpreter's evaluation stack
 (defvar *eval-stack* (make-array 100)) ; will grow as needed
-;;; FIXME: This seems to be used by the ordinary (non-byte) interpreter
-;;; too, judging from a crash I had when I removed byte-interp.lisp from
-;;; the cold build sequence. It would probably be clearer to pull the
-;;; shared interpreter machinery out of the byte interpreter and ordinary
-;;; interpreter files and put them into their own file shared-interp.lisp
-;;; or something.
 
 ;;; the index of the next free element of the interpreter's evaluation stack
 (defvar *eval-stack-top* 0)