I have a hard time coming up with a case where either is
desirable in a script, and they can be hard to avoid in
some cases.
Fixes lp#677779, and then some.
;;;; -*- coding: utf-8; fill-column: 78 -*-
changes relative to sbcl-1.0.46:
+ * enhancement: --script muffles style-warnings and compiler notes. (lp#677779)
* bug fix: SB-DEBUG:BACKTRACE-AS-LIST guards against potentially leaking
stack-allocated values out of their dynamic-extent. (lp#310175)
* bug fix: attempts to use SB-SPROF for wallclock profiling on threaded
(handling-end-of-the-world
(with-open-file (f pathname :element-type :default)
(sb!fasl::maybe-skip-shebang-line f)
- (load f :verbose nil :print nil)
+ ;; Scripts don't need to be stylish or fast, but silence is usually a
+ ;; desirable quality...
+ (handler-bind (((or style-warning compiler-note) #'muffle-warning))
+ (load f :verbose nil :print nil))
(quit)))))
;; Errors while processing the command line cause the system to QUIT,
;;; checkins which aren't released. (And occasionally for internal
;;; versions, especially for internal versions off the main CVS
;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"1.0.46.2"
+"1.0.46.3"