+\f
+;;;; helpers for C library calls
+
+;;; Signal a SIMPLE-CONDITION/ERROR condition associated with an ANSI C
+;;; errno problem, arranging for the condition's print representation
+;;; to be similar to the ANSI C perror(3) style.
+(defun simple-perror (prefix-string
+ &key
+ (errno (get-errno))
+ (simple-error 'simple-error)
+ other-condition-args)
+ (declare (type symbol simple-error))
+ (aver (subtypep simple-error 'simple-condition))
+ (aver (subtypep simple-error 'error))
+ (apply #'error
+ simple-error
+ :format-control "~@<~A: ~2I~_~A~:>"
+ :format-arguments (list prefix-string (strerror errno))
+ other-condition-args))
+\f
+;;;; optimization idioms
+
+(eval-when (:compile-toplevel :load-toplevel :execute)
+
+ ;; Byte compile this thing if possible.
+ (defvar *optimize-byte-compilation*
+ '(optimize (speed 0) (safety 1)))
+
+ ;; This thing is externally visible, so compiling meta-information
+ ;; is more important than byte-compiling it; but it's otherwise
+ ;; suitable for byte-compilation.
+ ;;
+ ;; (As long as the byte compiler isn't capable of compiling
+ ;; meta-information such as the argument list required by functions
+ ;; (as in sbcl-0.6.12, anyway), it's not suitable for compiling
+ ;; externally visible things like CL:INSPECT even if their speed
+ ;; requirements are small enough that it'd otherwise be OK. If some
+ ;; later version of the byte compiler learns to compile such
+ ;; meta-information, we'll probably change the implementation of
+ ;; this idiom so that it causes byte compilation of the thing after
+ ;; all.)
+ (defvar *optimize-external-despite-byte-compilation*
+ '(optimize (speed 1)
+ ;; still might as well be as small as possible..
+ (space 3))))