4.8.3 Compilation commands

Compile Defun

Editor Command

Argument: None
Key sequence: None

Compiles the current top-level form. If the current point is between two forms, the previous form is evaluated.

Compile Region

Editor Command

Argument: None
Key sequence: None

Compiles the Lisp forms in the region between the current point and the mark.

Compile File

Editor Command

Argument: file
Key sequence: None

Compiles all Lisp forms in file.

No checking is done on write dates for the source and binary files, to see if the file needs to be compiled. Also, no checking is done to see if there is a buffer for the file that should first be saved.

Compile Buffer

Editor Command

Argument: None
Key sequence: None

Compiles the Lisp forms in the current buffer.

Compile Buffer File

Editor Command

Argument: None
Key sequence: None

Compiles the file in the current buffer if its associated binary file is older than the source file or does not exist. For a file with a.lisp suffix, the corresponding binary file has a.fsl suffix. When the binary file is up to date, the user is asked if the source should be compiled anyway. WhenCompile-Buffer-File-Confirm is non-nil, the user is always asked for confirmation, even when the date of the source file is later than that of the binary file.

A prefix argument causes the file to be compiled without checking the date or existence of the binary file.

Compile-Buffer-File-Confirm

Editor variable

Default value:t

Determines whether Compile Buffer File should prompt for a compilation to proceed. If the value is non-nil, the user is always prompted for confirmation.

Compile Buffer Changed Definitions

Editor Command

Argument: None
Key sequence: None

Compiles definitions that have been changed in the current buffer during the current LispWorks session (useBuffer Changed Definitions on page 106 to see which definitions have changed). A prefix argument equal to the value ofPrefix-Argument-Default causes compilation of definitions changed since last compiled. A prefix argument of 1 causes compilation of definitions changed since last saved.

Compile Changed Definitions

Editor Command

Argument: None
Key sequence: None

Compiles definitions in all Lisp buffers that have been changed during the current LispWorks session. The effect of prefixes is the same as forCompile Buffer Changed Definitions.

Compile System

Editor Command

Argument: system
Key sequence: None

Compiles all definitions in system.

Compile System Changed Definitions

Editor Command

Argument: system
Key sequence: None

Compiles definitions that have been changed in system during the current LispWorks session.

Disassemble Definition

Editor Command

Argument: definition
Key sequence: None

Outputs assembly code for definition to the Output window, compiling it first if necessary. The name of the current top-level definition is offered as a default value for definition.

---

LispWorks Editor User Guide - 15 Oct 1998

Generated with Harlequin WebMaker