1
.TH GCL 1L "17 March 1997"
3
gcl \- GCL Common Lisp interpreter/compiler
14
is an implementation of a subset of the Common Lisp Ansi standard.
15
It is written in C and in Common Lisp, and is highly portable. It
16
includes those features in the original definition of Common Lisp,
17
(Guy Steele version 1.), as well as some features from the proposed
20
The best documentation is available in
22
form, with there being three groups of information.
24
for basic common lisp descriptions, and features unique to
28
info refers to the connection with
30
window system, allowing all the power of the
32
interaction system to be used from lisp.
35
details the Ansi standard for common lisp, to which this subset
36
tries to adhere. It is highly recommended to write programs,
37
which will be in the intersection of gcl and ansi common lisp.
38
Unfortunately the Ansi standard is huge, and will require a substantial
39
effort, and increase in the size of gcl, to include all of it.
44
is invoked from the shell, the variable
46
is set to the list of command line arguments.
54
Call read and then eval on the
65
Replace si::*command-args* by the the list starting after
67
Open the file following
68
.BR \-f for input, skip the first line, and
69
then read and eval the rest of the forms in the file. This can
70
be used as with the shells to write small shell programs:
74
#!/usr/local/bin/gcl.exe -f
76
(format t "hello world ~a~%" (nth 1 si::*command-args*))
82
will have the appropriate value.
83
Thus if the above 2 line file is made executable and called
96
NOTE: On many systems (eg SunOs) the first line of an executable
99
#!/usr/local/bin/gcl.exe -f
100
only reads the first 32 characters! So if your pathname where
101
the executable together with the '-f' amount to more than 32
102
characters the file will not be recognized. Also the executable
103
must be the actual large binary file, [or a link to it], and not
106
script. In latter case the
108
interpreter would get invoked on the file.
110
Alternately one could invoke the file
117
tutorial% gcl -f foo "from bill"
119
hello world from bill
125
Do not enter the command print loop. Useful if the other command
126
line arguments do something. Do not print the License and
127
acknowledgement information. Note if your program does print any
128
License information, it must print the GCL header information also.
133
Directory where the executable binary that is running is located.
134
Needed by save and friends. This gets set as
135
si::*system-directory*
144
would mean that the files like gcl-tk/tk.o would be found by
145
concatting the path to the libdir path, ie in
146
.RB /d/wfs/gcl-2.0/gcl-tk/tk.o
151
Invoke the compiler on the filename following
154
flags affect compilation.
161
then do not produce an
170
is specified, leave the intermediate
178
is specified, leave the intermediate
186
is specified, leave the intermediate
195
is specified then invoke
199
keyword argument, meaning that the C init function
200
will bear a name based on the name of the file, so that it may be
201
invoked by name by C code.
206
This GNU package should not be confused with the proprietary program
207
distributed by FRANZ, Inc.
208
Nor should it be confused with the public domain \*(Fl or the proprietary
210
For anything other than program development,
211
use of the lisp compiler \fIglc\fP(1L) is strongly
212
recommended in preference to use of the interpreter,
213
due to much higher speed.
215
.\"This program may be used in conjunction with the UCSF
218
.\".SH "LOCAL ACCESS"
219
.\"Locally, access to all L\s-2ISP\s0 systems is made through a shared
220
.\"interactive front-end which assumes that the job is be run in batch mode
221
.\"unless the \fB\-i\fP option is activated, which starts an interactive session.
222
.\"Interactive sessions are limited to 30 cpu minutes.
225
\fI/site/subsys/gcl/bin/gcl
228
\fI/site/subsys/gcl/bin/gclc
231
\fI/usr/include/cmpinclude.h
235
\fICommon LISP: The Language\fP, Guy L. Steele, Jr., Digital Press, Bedford, MA,
238
\fICommon LISPcraft\fP, Robert Wilensky, W. W. Norton & Co., New York, 1984.
241
The GCL system contains C and Lisp source files to build a Common Lisp
243
CGL is derived from Kyoto Common LISP (\fIkcl\fP),
244
which was written in 1984 by T. Yuasa and M. Hagiya
245
(working under Professor R. Nakajima at the Research
246
Institute for Mathematical Sciences, Kyoto University).
247
The AKCL system work was begun in 1987 by
248
William Schelter at the University of Texas, Austin, and continued through 1994.
249
In 1994 AKCL was released as GCL (GNU Common Lisp) under the
250
GNU public library license.