Next: Tools To Help Developers, Previous: Support For Unix, Up: Beyond the ANSI Standard
The toplevel repl prompt may be customized, and the function that reads user input may be replaced completely.
The behaviour of require when called with only one argument is
implementation-defined. In SBCL, require behaves in the
following way:
Loads a module, unless it already has been loaded.
pathnames, if supplied, is a designator for a list of pathnames to be loaded if the module needs to be. Ifpathnamesis not supplied, functions from the list*module-provider-functions*are called in order withmodule-nameas an argument, until one of them returns non-NIL. User code is responsible for callingprovideto indicate a successful load of the module.
Although SBCL does not provide a resident editor, the ed
function can be customized to hook into user-provided editing
mechanisms as follows:
Starts the editor (on a file or a function if named). Functions from the list
*ed-functions*are called in order withxas an argument until one of them returns non-NIL; these functions are responsible for signalling afile-errorto indicate failure to perform an operation on the file system.
Conditions of type warning and style-warning are
sometimes signaled at runtime, especially during execution of Common
Lisp defining forms such as defun, defmethod, etc. To
muffle these warnings at runtime, SBCL provides a variable
sb-ext:*muffled-warnings*: