Skip to content

Commit

Permalink
1.0.34.8: Cosmetic improvements to error output on compilation abort.
Browse files Browse the repository at this point in the history
* Make sure that error output is printed on a fresh line.

* Add mandatory newline before and after so the abortion
  stands out visually.

* Make sure to report the actual condition (fatal-compiler-error
  is just an encapsulation.)
  • Loading branch information
Tobias C. Rittweiler committed Jan 20, 2010
1 parent 4205c4d commit 09e08ad
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 3 deletions.
5 changes: 3 additions & 2 deletions src/compiler/main.lisp
Original file line number Diff line number Diff line change
Expand Up @@ -1624,10 +1624,11 @@
;; the input file.
(fatal-compiler-error (condition)
(signal condition)
(fresh-line *error-output*)
(pprint-logical-block (*error-output* nil :per-line-prefix "; ")
(format *error-output*
"~@<compilation aborted because of fatal error: ~2I~_~A~:>"
condition))
"~@<~@:_compilation aborted because of fatal error: ~2I~_~A~@:_~:>"
(encapsulated-condition condition)))
(finish-output *error-output*)
(values t t t)))))

Expand Down
2 changes: 1 addition & 1 deletion version.lisp-expr
Original file line number Diff line number Diff line change
Expand Up @@ -17,4 +17,4 @@
;;; 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.34.7"
"1.0.34.8"

0 comments on commit 09e08ad

Please sign in to comment.