X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcold%2Fwarm.lisp;h=6dbdb4c04b06717ab6e941c2639688b277b0f230;hb=a10eba73462a7203914114f3a4bdac98c741ec08;hp=70d8c95cffabeeca57f50c6e47fad75c20b0028b;hpb=c8218514d751c4d777892b79bbf1ca6597f731c0;p=sbcl.git diff --git a/src/cold/warm.lisp b/src/cold/warm.lisp index 70d8c95..6dbdb4c 100644 --- a/src/cold/warm.lisp +++ b/src/cold/warm.lisp @@ -46,9 +46,9 @@ ;; (Hopefully this will go away as we move the files above into cold load.) ;; -- WHN 19991214 (let ((fullname (concatenate 'string stem ".lisp"))) - ;; (Now that we use the byte compiler for interpretation, - ;; /SHOW doesn't get compiled properly until the src/assembly - ;; files have been loaded.) + ;; (Now that we use byte compiler for interpretation, /SHOW + ;; doesn't get compiled properly until the src/assembly files have + ;; been loaded, so we use PRINT instead.) #+sb-show (print "/about to compile src/assembly file") #+sb-show (print fullname) (multiple-value-bind @@ -146,14 +146,13 @@ ;;; ;;; FIXME: This has mutated into a hack which crudely duplicates ;;; functionality from the existing mechanism to load files from -;;; stems-and-flags.lisp-expr, without being quite parallel. (E.g. -;;; object files end up alongside the source files instead of ending -;;; up in parallel directory trees.) Maybe we could merge the -;;; filenames here into stems-and-flags.lisp-expr with some new flag -;;; (perhaps :WARM) to indicate that the files should be handled not -;;; in cold load but afterwards. Alternatively, we could call -(dolist (stem '( - ;; CLOS, derived from the PCL reference implementation +;;; build-order.lisp-expr, without being quite parallel. (E.g. object +;;; files end up alongside the source files instead of ending up in +;;; parallel directory trees.) Maybe we could merge the filenames here +;;; into build-order.lisp-expr with some new flag (perhaps :WARM) to +;;; indicate that the files should be handled not in cold load but +;;; afterwards. +(dolist (stem '(;; CLOS, derived from the PCL reference implementation ;; ;; This PCL build order is based on a particular ;; linearization of the declared build order