|[ < ]||[ > ]||[ << ]||[ Up ]||[ >> ]||[Top]||[Contents]||[Index]||[ ? ]|
This section describes two macros that test assertions, i.e., conditions which must be true if the program is operating correctly. Assertions never add to the behavior of a Lisp program; they simply make "sanity checks" to make sure everything is as it should be.
If the optimization property
speed has been set to 3, and
safety is less than 3, then the byte-compiler will optimize
away the following assertions. Because assertions might be optimized
away, it is a bad idea for them to include side-effects.
nilvalue). If so, it returns
nil. If the test is not satisfied,
assertsignals an error.
A default error message will be supplied which includes test-form.
You can specify a different error message by including a string
argument plus optional extra arguments. Those arguments are simply
error to signal the error.
If the optional second argument show-args is
nil, then the error message (with or without string)
will also include all non-constant arguments of the top-level
form. For example:
(assert (> x 10) t "x is too small: %d")
This usage of show-args is a change to Common Lisp. In
true Common Lisp, the second argument gives a list of places
which can be
setf'd by the user before continuing from the
nil. If not,
check-typesignals a continuable
wrong-type-argumenterror. The default error message lists the erroneous value along with type and place themselves. If string is specified, it is included in the error message in place of type. For example:
(check-type x (integer 1 *) "a positive integer")
See section 4.1 Type Predicates, for a description of the type specifiers that may be used for type.
Note that as in Common Lisp, the first argument to
should be a place suitable for use by
check-type signals a continuable error that allows the user to
modify place, most simply by returning a value from the debugger.
The following error-related macro is also defined:
progn, except that errors are ignored during the forms. More precisely, if an error is signalled then
ignore-errorsimmediately aborts execution of the forms and returns
nil. If the forms complete successfully,
ignore-errorsreturns the result of the last form.
|[ << ]||[ >> ]||[Top]||[Contents]||[Index]||[ ? ]|