.\" Copyright (c) 1980 Regents of the University of California.
.\" All rights reserved. The Berkeley software License Agreement
.\" specifies the terms and conditions for redistribution.
.\" @(#)liszt.1 6.1 (Berkeley) 4/29/85
.TH LISZT 1 "April 29, 1985"
liszt \- compile a Franz Lisp program
takes a file whose names ends in `.l' and compiles the F\s-2RANZ\s0 L\s-2ISP\s0
code there leaving an object program on the file whose name is that of the
source with `.o' substituted for `.l'.
The following options are interpreted by
Evaluate the given form before compilation begins.
Compile a M\s-2ACLISP\s0 file, by changing the readtable to conform to
\s-2MACLISP\s0 syntax and including a macro-defined compatibility package.
Put the object code in the specified file, rather than the default `.o' file.
places profiling code at the beginning of each non-local function.
If the lisp system is also created with profiling in it, this allows
function calling frequency to be determined (see
Only print warning and error messages.
Compilation statistics and notes on correct but unusual constructs
place bootstrap code at the beginning of the object file, which when
the object file is executed will cause a lisp system to be invoked
and the object file fasl'ed in.
Compile a UCI-lispfile, by changing the readtable to conform to
UCI-Lisp syntax and including a macro-defined compatibility package.
Suppress warning diagnostics.
Create a lisp cross reference file with the same name as the source
file but with `.x' appended.
reads this file and creates a human readable cross
put comments in the assembler output of the compiler. Useful
for debugging the compiler.
Print compilation statistics and warn of strange constructs.
Compile the named program and leave the assembler-language output on
the corresponding file suffixed `.s'.
This will also prevent the assembler language file from being assembled.
send the assembler output to standard output.
no source file is specified, then the compiler will run interactively.
You will find yourself talking to the
top-level command interpreter.
You can compile a file by using the
(an nlambda) with the same arguments as you use on the command line.
For example to compile `foo', a M\s-2ACLISP\s0 file, you would use:
supplies the ``.l'' extension for you.
/usr/lib/lisp/machacks.l M\s-2ACLISP\s0 compatibility package
/usr/lib/lisp/syscall.l macro definitions of Unix system calls
/usr/lib/lisp/ucifnc.l UCI Lisp compatibility package