Mercurial > emacs
annotate man/cl.texi @ 64851:7dd34112023a
*** empty log message ***
author | Richard M. Stallman <rms@gnu.org> |
---|---|
date | Tue, 09 Aug 2005 13:35:12 +0000 |
parents | c0646b78dca7 |
children | 3723093a21fd 187d6a1f84f7 |
rev | line source |
---|---|
25829 | 1 \input texinfo @c -*-texinfo-*- |
2 @setfilename ../info/cl | |
3 @settitle Common Lisp Extensions | |
4 | |
47737
0a70200bde27
use @copying instead of @ifinfo.
Karl Berry <karl@gnu.org>
parents:
42136
diff
changeset
|
5 @copying |
25829 | 6 This file documents the GNU Emacs Common Lisp emulation package. |
7 | |
60927
bae786986f2e
* calc.texi, cl.texi, gnus.texi, idlwave.texi, reftex.texi: Replace
Werner LEMBERG <wl@gnu.org>
parents:
55833
diff
changeset
|
8 Copyright (C) 1993, 2002, 2005 Free Software Foundation, Inc. |
47737
0a70200bde27
use @copying instead of @ifinfo.
Karl Berry <karl@gnu.org>
parents:
42136
diff
changeset
|
9 |
0a70200bde27
use @copying instead of @ifinfo.
Karl Berry <karl@gnu.org>
parents:
42136
diff
changeset
|
10 @quotation |
32315 | 11 Permission is granted to copy, distribute and/or modify this document |
12 under the terms of the GNU Free Documentation License, Version 1.1 or | |
13 any later version published by the Free Software Foundation; with no | |
14 Invariant Sections, with the Front-Cover texts being ``A GNU | |
15 Manual'', and with the Back-Cover Texts as in (a) below. A copy of the | |
16 license is included in the section entitled ``GNU Free Documentation | |
17 License'' in the Emacs manual. | |
18 | |
19 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify | |
20 this GNU Manual, like GNU software. Copies published by the Free | |
21 Software Foundation raise funds for GNU development.'' | |
22 | |
23 This document is part of a collection distributed under the GNU Free | |
24 Documentation License. If you want to distribute this document | |
25 separately from the collection, you can do so by adding a copy of the | |
26 license to the document, as described in section 6 of the license. | |
47737
0a70200bde27
use @copying instead of @ifinfo.
Karl Berry <karl@gnu.org>
parents:
42136
diff
changeset
|
27 @end quotation |
0a70200bde27
use @copying instead of @ifinfo.
Karl Berry <karl@gnu.org>
parents:
42136
diff
changeset
|
28 @end copying |
0a70200bde27
use @copying instead of @ifinfo.
Karl Berry <karl@gnu.org>
parents:
42136
diff
changeset
|
29 |
0a70200bde27
use @copying instead of @ifinfo.
Karl Berry <karl@gnu.org>
parents:
42136
diff
changeset
|
30 @dircategory Emacs |
0a70200bde27
use @copying instead of @ifinfo.
Karl Berry <karl@gnu.org>
parents:
42136
diff
changeset
|
31 @direntry |
0a70200bde27
use @copying instead of @ifinfo.
Karl Berry <karl@gnu.org>
parents:
42136
diff
changeset
|
32 * CL: (cl). Partial Common Lisp support for Emacs Lisp. |
0a70200bde27
use @copying instead of @ifinfo.
Karl Berry <karl@gnu.org>
parents:
42136
diff
changeset
|
33 @end direntry |
0a70200bde27
use @copying instead of @ifinfo.
Karl Berry <karl@gnu.org>
parents:
42136
diff
changeset
|
34 |
0a70200bde27
use @copying instead of @ifinfo.
Karl Berry <karl@gnu.org>
parents:
42136
diff
changeset
|
35 @finalout |
25829 | 36 |
37 @titlepage | |
38 @sp 6 | |
39 @center @titlefont{Common Lisp Extensions} | |
40 @sp 4 | |
41 @center For GNU Emacs Lisp | |
42 @sp 1 | |
43 @center Version 2.02 | |
44 @sp 5 | |
45 @center Dave Gillespie | |
46 @center daveg@@synaptics.com | |
47 @page | |
48 @vskip 0pt plus 1filll | |
47737
0a70200bde27
use @copying instead of @ifinfo.
Karl Berry <karl@gnu.org>
parents:
42136
diff
changeset
|
49 @insertcopying |
25829 | 50 @end titlepage |
51 | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
52 @node Top, Overview, (dir), (dir) |
55833
1986f67220dd
(Top): Call this chapter `Introduction'.
Richard M. Stallman <rms@gnu.org>
parents:
54379
diff
changeset
|
53 @chapter Introduction |
25829 | 54 |
55 @noindent | |
56 This document describes a set of Emacs Lisp facilities borrowed from | |
57 Common Lisp. All the facilities are described here in detail. While | |
58 this document does not assume any prior knowledge of Common Lisp, it | |
59 does assume a basic familiarity with Emacs Lisp. | |
60 | |
61 @menu | |
62 * Overview:: Installation, usage, etc. | |
63 * Program Structure:: Arglists, `eval-when', `defalias' | |
64 * Predicates:: `typep', `eql', and `equalp' | |
65 * Control Structure:: `setf', `do', `loop', etc. | |
66 * Macros:: Destructuring, `define-compiler-macro' | |
67 * Declarations:: `proclaim', `declare', etc. | |
68 * Symbols:: Property lists, `gensym' | |
69 * Numbers:: Predicates, functions, random numbers | |
70 * Sequences:: Mapping, functions, searching, sorting | |
71 * Lists:: `cadr', `sublis', `member*', `assoc*', etc. | |
72 * Structures:: `defstruct' | |
73 * Assertions:: `check-type', `assert', `ignore-errors'. | |
74 | |
75 * Efficiency Concerns:: Hints and techniques | |
76 * Common Lisp Compatibility:: All known differences with Steele | |
77 * Old CL Compatibility:: All known differences with old cl.el | |
78 * Porting Common Lisp:: Hints for porting Common Lisp code | |
79 | |
80 * Function Index:: | |
81 * Variable Index:: | |
82 @end menu | |
83 | |
84 @node Overview, Program Structure, Top, Top | |
55833
1986f67220dd
(Top): Call this chapter `Introduction'.
Richard M. Stallman <rms@gnu.org>
parents:
54379
diff
changeset
|
85 @ifnottex |
25829 | 86 @chapter Overview |
55833
1986f67220dd
(Top): Call this chapter `Introduction'.
Richard M. Stallman <rms@gnu.org>
parents:
54379
diff
changeset
|
87 @end ifnottex |
25829 | 88 |
89 @noindent | |
90 Common Lisp is a huge language, and Common Lisp systems tend to be | |
91 massive and extremely complex. Emacs Lisp, by contrast, is rather | |
92 minimalist in the choice of Lisp features it offers the programmer. | |
93 As Emacs Lisp programmers have grown in number, and the applications | |
94 they write have grown more ambitious, it has become clear that Emacs | |
95 Lisp could benefit from many of the conveniences of Common Lisp. | |
96 | |
97 The @dfn{CL} package adds a number of Common Lisp functions and | |
98 control structures to Emacs Lisp. While not a 100% complete | |
99 implementation of Common Lisp, @dfn{CL} adds enough functionality | |
100 to make Emacs Lisp programming significantly more convenient. | |
101 | |
40590
e9ca70d27e37
Explain when not to use CL.
Richard M. Stallman <rms@gnu.org>
parents:
36931
diff
changeset
|
102 @strong{Please note:} the @dfn{CL} functions are not standard parts of |
e9ca70d27e37
Explain when not to use CL.
Richard M. Stallman <rms@gnu.org>
parents:
36931
diff
changeset
|
103 the Emacs Lisp name space, so it is legitimate for users to define |
e9ca70d27e37
Explain when not to use CL.
Richard M. Stallman <rms@gnu.org>
parents:
36931
diff
changeset
|
104 them with other, conflicting meanings. To avoid conflicting with |
e9ca70d27e37
Explain when not to use CL.
Richard M. Stallman <rms@gnu.org>
parents:
36931
diff
changeset
|
105 those user activities, we have a policy that packages installed in |
e9ca70d27e37
Explain when not to use CL.
Richard M. Stallman <rms@gnu.org>
parents:
36931
diff
changeset
|
106 Emacs must not load @dfn{CL} at run time. (It is ok for them to load |
e9ca70d27e37
Explain when not to use CL.
Richard M. Stallman <rms@gnu.org>
parents:
36931
diff
changeset
|
107 @dfn{CL} at compile time only, with @code{eval-when-compile}, and use |
e9ca70d27e37
Explain when not to use CL.
Richard M. Stallman <rms@gnu.org>
parents:
36931
diff
changeset
|
108 the macros it provides.) If you are writing packages that you plan to |
e9ca70d27e37
Explain when not to use CL.
Richard M. Stallman <rms@gnu.org>
parents:
36931
diff
changeset
|
109 distribute and invite widespread use for, you might want to observe |
e9ca70d27e37
Explain when not to use CL.
Richard M. Stallman <rms@gnu.org>
parents:
36931
diff
changeset
|
110 the same rule. |
e9ca70d27e37
Explain when not to use CL.
Richard M. Stallman <rms@gnu.org>
parents:
36931
diff
changeset
|
111 |
25829 | 112 Some Common Lisp features have been omitted from this package |
113 for various reasons: | |
114 | |
115 @itemize @bullet | |
116 @item | |
117 Some features are too complex or bulky relative to their benefit | |
118 to Emacs Lisp programmers. CLOS and Common Lisp streams are fine | |
119 examples of this group. | |
120 | |
121 @item | |
122 Other features cannot be implemented without modification to the | |
123 Emacs Lisp interpreter itself, such as multiple return values, | |
124 lexical scoping, case-insensitive symbols, and complex numbers. | |
125 The @dfn{CL} package generally makes no attempt to emulate these | |
126 features. | |
127 | |
128 @item | |
129 Some features conflict with existing things in Emacs Lisp. For | |
130 example, Emacs' @code{assoc} function is incompatible with the | |
131 Common Lisp @code{assoc}. In such cases, this package usually | |
132 adds the suffix @samp{*} to the function name of the Common | |
133 Lisp version of the function (e.g., @code{assoc*}). | |
134 @end itemize | |
135 | |
136 The package described here was written by Dave Gillespie, | |
137 @file{daveg@@synaptics.com}. It is a total rewrite of the original | |
138 1986 @file{cl.el} package by Cesar Quiroz. Most features of the | |
64455
c0646b78dca7
(Overview): Delete duplicate words.
Juri Linkov <juri@jurta.org>
parents:
64366
diff
changeset
|
139 Quiroz package have been retained; any incompatibilities are |
25829 | 140 noted in the descriptions below. Care has been taken in this |
141 version to ensure that each function is defined efficiently, | |
142 concisely, and with minimal impact on the rest of the Emacs | |
143 environment. | |
144 | |
145 @menu | |
146 * Usage:: How to use the CL package | |
147 * Organization:: The package's five component files | |
148 * Installation:: Compiling and installing CL | |
149 * Naming Conventions:: Notes on CL function names | |
150 @end menu | |
151 | |
152 @node Usage, Organization, Overview, Overview | |
153 @section Usage | |
154 | |
155 @noindent | |
156 Lisp code that uses features from the @dfn{CL} package should | |
157 include at the beginning: | |
158 | |
159 @example | |
160 (require 'cl) | |
161 @end example | |
162 | |
163 @noindent | |
164 If you want to ensure that the new (Gillespie) version of @dfn{CL} | |
165 is the one that is present, add an additional @code{(require 'cl-19)} | |
166 call: | |
167 | |
168 @example | |
169 (require 'cl) | |
170 (require 'cl-19) | |
171 @end example | |
172 | |
173 @noindent | |
174 The second call will fail (with ``@file{cl-19.el} not found'') if | |
175 the old @file{cl.el} package was in use. | |
176 | |
177 It is safe to arrange to load @dfn{CL} at all times, e.g., | |
178 in your @file{.emacs} file. But it's a good idea, for portability, | |
179 to @code{(require 'cl)} in your code even if you do this. | |
180 | |
181 @node Organization, Installation, Usage, Overview | |
182 @section Organization | |
183 | |
184 @noindent | |
185 The Common Lisp package is organized into four files: | |
186 | |
187 @table @file | |
188 @item cl.el | |
189 This is the ``main'' file, which contains basic functions | |
190 and information about the package. This file is relatively | |
191 compact---about 700 lines. | |
192 | |
193 @item cl-extra.el | |
194 This file contains the larger, more complex or unusual functions. | |
195 It is kept separate so that packages which only want to use Common | |
196 Lisp fundamentals like the @code{cadr} function won't need to pay | |
197 the overhead of loading the more advanced functions. | |
198 | |
199 @item cl-seq.el | |
200 This file contains most of the advanced functions for operating | |
201 on sequences or lists, such as @code{delete-if} and @code{assoc*}. | |
202 | |
203 @item cl-macs.el | |
204 This file contains the features of the packages which are macros | |
205 instead of functions. Macros expand when the caller is compiled, | |
206 not when it is run, so the macros generally only need to be | |
207 present when the byte-compiler is running (or when the macros are | |
208 used in uncompiled code such as a @file{.emacs} file). Most of | |
209 the macros of this package are isolated in @file{cl-macs.el} so | |
210 that they won't take up memory unless you are compiling. | |
211 @end table | |
212 | |
213 The file @file{cl.el} includes all necessary @code{autoload} | |
214 commands for the functions and macros in the other three files. | |
215 All you have to do is @code{(require 'cl)}, and @file{cl.el} | |
216 will take care of pulling in the other files when they are | |
217 needed. | |
218 | |
219 There is another file, @file{cl-compat.el}, which defines some | |
220 routines from the older @file{cl.el} package that are no longer | |
221 present in the new package. This includes internal routines | |
222 like @code{setelt} and @code{zip-lists}, deprecated features | |
223 like @code{defkeyword}, and an emulation of the old-style | |
224 multiple-values feature. @xref{Old CL Compatibility}. | |
225 | |
226 @node Installation, Naming Conventions, Organization, Overview | |
227 @section Installation | |
228 | |
229 @noindent | |
230 Installation of the @dfn{CL} package is simple: Just put the | |
231 byte-compiled files @file{cl.elc}, @file{cl-extra.elc}, | |
232 @file{cl-seq.elc}, @file{cl-macs.elc}, and @file{cl-compat.elc} | |
233 into a directory on your @code{load-path}. | |
234 | |
235 There are no special requirements to compile this package: | |
236 The files do not have to be loaded before they are compiled, | |
237 nor do they need to be compiled in any particular order. | |
238 | |
239 You may choose to put the files into your main @file{lisp/} | |
240 directory, replacing the original @file{cl.el} file there. Or, | |
241 you could put them into a directory that comes before @file{lisp/} | |
242 on your @code{load-path} so that the old @file{cl.el} is | |
243 effectively hidden. | |
244 | |
245 Also, format the @file{cl.texinfo} file and put the resulting | |
246 Info files in the @file{info/} directory or another suitable place. | |
247 | |
248 You may instead wish to leave this package's components all in | |
249 their own directory, and then add this directory to your | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
250 @code{load-path} and @code{Info-directory-list}. |
25829 | 251 Add the directory to the front of the list so the old @dfn{CL} |
252 package and its documentation are hidden. | |
253 | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
254 @node Naming Conventions, , Installation, Overview |
25829 | 255 @section Naming Conventions |
256 | |
257 @noindent | |
258 Except where noted, all functions defined by this package have the | |
259 same names and calling conventions as their Common Lisp counterparts. | |
260 | |
261 Following is a complete list of functions whose names were changed | |
262 from Common Lisp, usually to avoid conflicts with Emacs. In each | |
263 case, a @samp{*} has been appended to the Common Lisp name to obtain | |
264 the Emacs name: | |
265 | |
266 @example | |
267 defun* defsubst* defmacro* function* | |
268 member* assoc* rassoc* get* | |
269 remove* delete* mapcar* sort* | |
270 floor* ceiling* truncate* round* | |
36931 | 271 mod* rem* random* |
25829 | 272 @end example |
273 | |
274 Internal function and variable names in the package are prefixed | |
275 by @code{cl-}. Here is a complete list of functions @emph{not} | |
276 prefixed by @code{cl-} which were not taken from Common Lisp: | |
277 | |
278 @example | |
28039
c3a446101beb
Remove references to rassoc, delete, expt.
Dave Love <fx@gnu.org>
parents:
27511
diff
changeset
|
279 floatp-safe lexical-let lexical-let* |
25829 | 280 callf callf2 letf letf* |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
281 defsubst* |
25829 | 282 @end example |
283 | |
284 The following simple functions and macros are defined in @file{cl.el}; | |
285 they do not cause other components like @file{cl-extra} to be loaded. | |
286 | |
287 @example | |
27225
ee242fddb1ab
Remove various old stuff and references thereto.
Dave Love <fx@gnu.org>
parents:
25829
diff
changeset
|
288 eql floatp-safe endp |
25829 | 289 evenp oddp plusp minusp |
35089 | 290 caaar .. cddddr |
25829 | 291 list* ldiff rest first .. tenth |
27225
ee242fddb1ab
Remove various old stuff and references thereto.
Dave Love <fx@gnu.org>
parents:
25829
diff
changeset
|
292 copy-list subst mapcar* [2] |
25829 | 293 adjoin [3] acons pairlis pop [4] |
294 push [4] pushnew [3,4] incf [4] decf [4] | |
295 proclaim declaim | |
296 @end example | |
297 | |
298 @noindent | |
299 [2] Only for one sequence argument or two list arguments. | |
300 | |
301 @noindent | |
302 [3] Only if @code{:test} is @code{eq}, @code{equal}, or unspecified, | |
303 and @code{:key} is not used. | |
304 | |
305 @noindent | |
306 [4] Only when @var{place} is a plain variable name. | |
307 | |
308 @iftex | |
309 @chapno=4 | |
310 @end iftex | |
311 | |
312 @node Program Structure, Predicates, Overview, Top | |
313 @chapter Program Structure | |
314 | |
315 @noindent | |
316 This section describes features of the @dfn{CL} package which have to | |
317 do with programs as a whole: advanced argument lists for functions, | |
318 and the @code{eval-when} construct. | |
319 | |
320 @menu | |
321 * Argument Lists:: `&key', `&aux', `defun*', `defmacro*'. | |
322 * Time of Evaluation:: The `eval-when' construct. | |
323 @end menu | |
324 | |
325 @iftex | |
326 @secno=1 | |
327 @end iftex | |
328 | |
329 @node Argument Lists, Time of Evaluation, Program Structure, Program Structure | |
330 @section Argument Lists | |
331 | |
332 @noindent | |
333 Emacs Lisp's notation for argument lists of functions is a subset of | |
334 the Common Lisp notation. As well as the familiar @code{&optional} | |
335 and @code{&rest} markers, Common Lisp allows you to specify default | |
336 values for optional arguments, and it provides the additional markers | |
337 @code{&key} and @code{&aux}. | |
338 | |
339 Since argument parsing is built-in to Emacs, there is no way for | |
340 this package to implement Common Lisp argument lists seamlessly. | |
341 Instead, this package defines alternates for several Lisp forms | |
342 which you must use if you need Common Lisp argument lists. | |
343 | |
344 @defspec defun* name arglist body... | |
345 This form is identical to the regular @code{defun} form, except | |
346 that @var{arglist} is allowed to be a full Common Lisp argument | |
347 list. Also, the function body is enclosed in an implicit block | |
348 called @var{name}; @pxref{Blocks and Exits}. | |
349 @end defspec | |
350 | |
351 @defspec defsubst* name arglist body... | |
352 This is just like @code{defun*}, except that the function that | |
353 is defined is automatically proclaimed @code{inline}, i.e., | |
354 calls to it may be expanded into in-line code by the byte compiler. | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
355 This is analogous to the @code{defsubst} form; |
25829 | 356 @code{defsubst*} uses a different method (compiler macros) which |
357 works in all version of Emacs, and also generates somewhat more | |
358 efficient inline expansions. In particular, @code{defsubst*} | |
359 arranges for the processing of keyword arguments, default values, | |
360 etc., to be done at compile-time whenever possible. | |
361 @end defspec | |
362 | |
363 @defspec defmacro* name arglist body... | |
364 This is identical to the regular @code{defmacro} form, | |
365 except that @var{arglist} is allowed to be a full Common Lisp | |
366 argument list. The @code{&environment} keyword is supported as | |
367 described in Steele. The @code{&whole} keyword is supported only | |
368 within destructured lists (see below); top-level @code{&whole} | |
369 cannot be implemented with the current Emacs Lisp interpreter. | |
370 The macro expander body is enclosed in an implicit block called | |
371 @var{name}. | |
372 @end defspec | |
373 | |
374 @defspec function* symbol-or-lambda | |
375 This is identical to the regular @code{function} form, | |
376 except that if the argument is a @code{lambda} form then that | |
377 form may use a full Common Lisp argument list. | |
378 @end defspec | |
379 | |
380 Also, all forms (such as @code{defsetf} and @code{flet}) defined | |
381 in this package that include @var{arglist}s in their syntax allow | |
382 full Common Lisp argument lists. | |
383 | |
384 Note that it is @emph{not} necessary to use @code{defun*} in | |
385 order to have access to most @dfn{CL} features in your function. | |
386 These features are always present; @code{defun*}'s only | |
387 difference from @code{defun} is its more flexible argument | |
388 lists and its implicit block. | |
389 | |
390 The full form of a Common Lisp argument list is | |
391 | |
392 @example | |
393 (@var{var}... | |
394 &optional (@var{var} @var{initform} @var{svar})... | |
395 &rest @var{var} | |
396 &key ((@var{keyword} @var{var}) @var{initform} @var{svar})... | |
397 &aux (@var{var} @var{initform})...) | |
398 @end example | |
399 | |
400 Each of the five argument list sections is optional. The @var{svar}, | |
401 @var{initform}, and @var{keyword} parts are optional; if they are | |
402 omitted, then @samp{(@var{var})} may be written simply @samp{@var{var}}. | |
403 | |
404 The first section consists of zero or more @dfn{required} arguments. | |
405 These arguments must always be specified in a call to the function; | |
406 there is no difference between Emacs Lisp and Common Lisp as far as | |
407 required arguments are concerned. | |
408 | |
409 The second section consists of @dfn{optional} arguments. These | |
410 arguments may be specified in the function call; if they are not, | |
411 @var{initform} specifies the default value used for the argument. | |
412 (No @var{initform} means to use @code{nil} as the default.) The | |
413 @var{initform} is evaluated with the bindings for the preceding | |
414 arguments already established; @code{(a &optional (b (1+ a)))} | |
415 matches one or two arguments, with the second argument defaulting | |
416 to one plus the first argument. If the @var{svar} is specified, | |
417 it is an auxiliary variable which is bound to @code{t} if the optional | |
418 argument was specified, or to @code{nil} if the argument was omitted. | |
419 If you don't use an @var{svar}, then there will be no way for your | |
420 function to tell whether it was called with no argument, or with | |
421 the default value passed explicitly as an argument. | |
422 | |
423 The third section consists of a single @dfn{rest} argument. If | |
424 more arguments were passed to the function than are accounted for | |
425 by the required and optional arguments, those extra arguments are | |
426 collected into a list and bound to the ``rest'' argument variable. | |
427 Common Lisp's @code{&rest} is equivalent to that of Emacs Lisp. | |
428 Common Lisp accepts @code{&body} as a synonym for @code{&rest} in | |
429 macro contexts; this package accepts it all the time. | |
430 | |
431 The fourth section consists of @dfn{keyword} arguments. These | |
432 are optional arguments which are specified by name rather than | |
433 positionally in the argument list. For example, | |
434 | |
435 @example | |
436 (defun* foo (a &optional b &key c d (e 17))) | |
437 @end example | |
438 | |
439 @noindent | |
440 defines a function which may be called with one, two, or more | |
441 arguments. The first two arguments are bound to @code{a} and | |
442 @code{b} in the usual way. The remaining arguments must be | |
443 pairs of the form @code{:c}, @code{:d}, or @code{:e} followed | |
444 by the value to be bound to the corresponding argument variable. | |
445 (Symbols whose names begin with a colon are called @dfn{keywords}, | |
446 and they are self-quoting in the same way as @code{nil} and | |
447 @code{t}.) | |
448 | |
449 For example, the call @code{(foo 1 2 :d 3 :c 4)} sets the five | |
450 arguments to 1, 2, 4, 3, and 17, respectively. If the same keyword | |
451 appears more than once in the function call, the first occurrence | |
452 takes precedence over the later ones. Note that it is not possible | |
453 to specify keyword arguments without specifying the optional | |
454 argument @code{b} as well, since @code{(foo 1 :c 2)} would bind | |
455 @code{b} to the keyword @code{:c}, then signal an error because | |
456 @code{2} is not a valid keyword. | |
457 | |
458 If a @var{keyword} symbol is explicitly specified in the argument | |
459 list as shown in the above diagram, then that keyword will be | |
460 used instead of just the variable name prefixed with a colon. | |
461 You can specify a @var{keyword} symbol which does not begin with | |
462 a colon at all, but such symbols will not be self-quoting; you | |
463 will have to quote them explicitly with an apostrophe in the | |
464 function call. | |
465 | |
466 Ordinarily it is an error to pass an unrecognized keyword to | |
467 a function, e.g., @code{(foo 1 2 :c 3 :goober 4)}. You can ask | |
468 Lisp to ignore unrecognized keywords, either by adding the | |
469 marker @code{&allow-other-keys} after the keyword section | |
470 of the argument list, or by specifying an @code{:allow-other-keys} | |
471 argument in the call whose value is non-@code{nil}. If the | |
472 function uses both @code{&rest} and @code{&key} at the same time, | |
473 the ``rest'' argument is bound to the keyword list as it appears | |
474 in the call. For example: | |
475 | |
476 @smallexample | |
477 (defun* find-thing (thing &rest rest &key need &allow-other-keys) | |
478 (or (apply 'member* thing thing-list :allow-other-keys t rest) | |
479 (if need (error "Thing not found")))) | |
480 @end smallexample | |
481 | |
482 @noindent | |
483 This function takes a @code{:need} keyword argument, but also | |
484 accepts other keyword arguments which are passed on to the | |
485 @code{member*} function. @code{allow-other-keys} is used to | |
486 keep both @code{find-thing} and @code{member*} from complaining | |
487 about each others' keywords in the arguments. | |
488 | |
489 The fifth section of the argument list consists of @dfn{auxiliary | |
490 variables}. These are not really arguments at all, but simply | |
491 variables which are bound to @code{nil} or to the specified | |
492 @var{initforms} during execution of the function. There is no | |
493 difference between the following two functions, except for a | |
494 matter of stylistic taste: | |
495 | |
496 @example | |
497 (defun* foo (a b &aux (c (+ a b)) d) | |
498 @var{body}) | |
499 | |
500 (defun* foo (a b) | |
501 (let ((c (+ a b)) d) | |
502 @var{body})) | |
503 @end example | |
504 | |
505 Argument lists support @dfn{destructuring}. In Common Lisp, | |
506 destructuring is only allowed with @code{defmacro}; this package | |
507 allows it with @code{defun*} and other argument lists as well. | |
508 In destructuring, any argument variable (@var{var} in the above | |
509 diagram) can be replaced by a list of variables, or more generally, | |
510 a recursive argument list. The corresponding argument value must | |
511 be a list whose elements match this recursive argument list. | |
512 For example: | |
513 | |
514 @example | |
515 (defmacro* dolist ((var listform &optional resultform) | |
516 &rest body) | |
517 ...) | |
518 @end example | |
519 | |
520 This says that the first argument of @code{dolist} must be a list | |
521 of two or three items; if there are other arguments as well as this | |
522 list, they are stored in @code{body}. All features allowed in | |
523 regular argument lists are allowed in these recursive argument lists. | |
524 In addition, the clause @samp{&whole @var{var}} is allowed at the | |
525 front of a recursive argument list. It binds @var{var} to the | |
526 whole list being matched; thus @code{(&whole all a b)} matches | |
527 a list of two things, with @code{a} bound to the first thing, | |
528 @code{b} bound to the second thing, and @code{all} bound to the | |
529 list itself. (Common Lisp allows @code{&whole} in top-level | |
530 @code{defmacro} argument lists as well, but Emacs Lisp does not | |
531 support this usage.) | |
532 | |
533 One last feature of destructuring is that the argument list may be | |
534 dotted, so that the argument list @code{(a b . c)} is functionally | |
535 equivalent to @code{(a b &rest c)}. | |
536 | |
537 If the optimization quality @code{safety} is set to 0 | |
538 (@pxref{Declarations}), error checking for wrong number of | |
539 arguments and invalid keyword arguments is disabled. By default, | |
540 argument lists are rigorously checked. | |
541 | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
542 @node Time of Evaluation, , Argument Lists, Program Structure |
25829 | 543 @section Time of Evaluation |
544 | |
545 @noindent | |
546 Normally, the byte-compiler does not actually execute the forms in | |
547 a file it compiles. For example, if a file contains @code{(setq foo t)}, | |
548 the act of compiling it will not actually set @code{foo} to @code{t}. | |
549 This is true even if the @code{setq} was a top-level form (i.e., not | |
550 enclosed in a @code{defun} or other form). Sometimes, though, you | |
551 would like to have certain top-level forms evaluated at compile-time. | |
552 For example, the compiler effectively evaluates @code{defmacro} forms | |
553 at compile-time so that later parts of the file can refer to the | |
554 macros that are defined. | |
555 | |
556 @defspec eval-when (situations...) forms... | |
557 This form controls when the body @var{forms} are evaluated. | |
558 The @var{situations} list may contain any set of the symbols | |
559 @code{compile}, @code{load}, and @code{eval} (or their long-winded | |
560 ANSI equivalents, @code{:compile-toplevel}, @code{:load-toplevel}, | |
561 and @code{:execute}). | |
562 | |
563 The @code{eval-when} form is handled differently depending on | |
564 whether or not it is being compiled as a top-level form. | |
565 Specifically, it gets special treatment if it is being compiled | |
566 by a command such as @code{byte-compile-file} which compiles files | |
567 or buffers of code, and it appears either literally at the | |
568 top level of the file or inside a top-level @code{progn}. | |
569 | |
570 For compiled top-level @code{eval-when}s, the body @var{forms} are | |
571 executed at compile-time if @code{compile} is in the @var{situations} | |
572 list, and the @var{forms} are written out to the file (to be executed | |
573 at load-time) if @code{load} is in the @var{situations} list. | |
574 | |
575 For non-compiled-top-level forms, only the @code{eval} situation is | |
576 relevant. (This includes forms executed by the interpreter, forms | |
577 compiled with @code{byte-compile} rather than @code{byte-compile-file}, | |
578 and non-top-level forms.) The @code{eval-when} acts like a | |
579 @code{progn} if @code{eval} is specified, and like @code{nil} | |
580 (ignoring the body @var{forms}) if not. | |
581 | |
582 The rules become more subtle when @code{eval-when}s are nested; | |
583 consult Steele (second edition) for the gruesome details (and | |
584 some gruesome examples). | |
585 | |
586 Some simple examples: | |
587 | |
588 @example | |
589 ;; Top-level forms in foo.el: | |
590 (eval-when (compile) (setq foo1 'bar)) | |
591 (eval-when (load) (setq foo2 'bar)) | |
592 (eval-when (compile load) (setq foo3 'bar)) | |
593 (eval-when (eval) (setq foo4 'bar)) | |
594 (eval-when (eval compile) (setq foo5 'bar)) | |
595 (eval-when (eval load) (setq foo6 'bar)) | |
596 (eval-when (eval compile load) (setq foo7 'bar)) | |
597 @end example | |
598 | |
599 When @file{foo.el} is compiled, these variables will be set during | |
600 the compilation itself: | |
601 | |
602 @example | |
603 foo1 foo3 foo5 foo7 ; `compile' | |
604 @end example | |
605 | |
606 When @file{foo.elc} is loaded, these variables will be set: | |
607 | |
608 @example | |
609 foo2 foo3 foo6 foo7 ; `load' | |
610 @end example | |
611 | |
612 And if @file{foo.el} is loaded uncompiled, these variables will | |
613 be set: | |
614 | |
615 @example | |
616 foo4 foo5 foo6 foo7 ; `eval' | |
617 @end example | |
618 | |
619 If these seven @code{eval-when}s had been, say, inside a @code{defun}, | |
620 then the first three would have been equivalent to @code{nil} and the | |
621 last four would have been equivalent to the corresponding @code{setq}s. | |
622 | |
623 Note that @code{(eval-when (load eval) @dots{})} is equivalent | |
624 to @code{(progn @dots{})} in all contexts. The compiler treats | |
625 certain top-level forms, like @code{defmacro} (sort-of) and | |
626 @code{require}, as if they were wrapped in @code{(eval-when | |
627 (compile load eval) @dots{})}. | |
628 @end defspec | |
629 | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
630 Emacs includes two special forms related to @code{eval-when}. |
25829 | 631 One of these, @code{eval-when-compile}, is not quite equivalent to |
27225
ee242fddb1ab
Remove various old stuff and references thereto.
Dave Love <fx@gnu.org>
parents:
25829
diff
changeset
|
632 any @code{eval-when} construct and is described below. |
25829 | 633 |
634 The other form, @code{(eval-and-compile @dots{})}, is exactly | |
635 equivalent to @samp{(eval-when (compile load eval) @dots{})} and | |
636 so is not itself defined by this package. | |
637 | |
638 @defspec eval-when-compile forms... | |
639 The @var{forms} are evaluated at compile-time; at execution time, | |
640 this form acts like a quoted constant of the resulting value. Used | |
641 at top-level, @code{eval-when-compile} is just like @samp{eval-when | |
642 (compile eval)}. In other contexts, @code{eval-when-compile} | |
643 allows code to be evaluated once at compile-time for efficiency | |
644 or other reasons. | |
645 | |
646 This form is similar to the @samp{#.} syntax of true Common Lisp. | |
647 @end defspec | |
648 | |
649 @defspec load-time-value form | |
650 The @var{form} is evaluated at load-time; at execution time, | |
651 this form acts like a quoted constant of the resulting value. | |
652 | |
653 Early Common Lisp had a @samp{#,} syntax that was similar to | |
654 this, but ANSI Common Lisp replaced it with @code{load-time-value} | |
655 and gave it more well-defined semantics. | |
656 | |
657 In a compiled file, @code{load-time-value} arranges for @var{form} | |
658 to be evaluated when the @file{.elc} file is loaded and then used | |
659 as if it were a quoted constant. In code compiled by | |
660 @code{byte-compile} rather than @code{byte-compile-file}, the | |
661 effect is identical to @code{eval-when-compile}. In uncompiled | |
662 code, both @code{eval-when-compile} and @code{load-time-value} | |
663 act exactly like @code{progn}. | |
664 | |
665 @example | |
666 (defun report () | |
667 (insert "This function was executed on: " | |
668 (current-time-string) | |
669 ", compiled on: " | |
670 (eval-when-compile (current-time-string)) | |
671 ;; or '#.(current-time-string) in real Common Lisp | |
672 ", and loaded on: " | |
673 (load-time-value (current-time-string)))) | |
674 @end example | |
675 | |
676 @noindent | |
677 Byte-compiled, the above defun will result in the following code | |
678 (or its compiled equivalent, of course) in the @file{.elc} file: | |
679 | |
680 @example | |
681 (setq --temp-- (current-time-string)) | |
682 (defun report () | |
683 (insert "This function was executed on: " | |
684 (current-time-string) | |
685 ", compiled on: " | |
686 '"Wed Jun 23 18:33:43 1993" | |
687 ", and loaded on: " | |
688 --temp--)) | |
689 @end example | |
690 @end defspec | |
691 | |
692 @node Predicates, Control Structure, Program Structure, Top | |
693 @chapter Predicates | |
694 | |
695 @noindent | |
696 This section describes functions for testing whether various | |
697 facts are true or false. | |
698 | |
699 @menu | |
700 * Type Predicates:: `typep', `deftype', and `coerce' | |
701 * Equality Predicates:: `eql' and `equalp' | |
702 @end menu | |
703 | |
704 @node Type Predicates, Equality Predicates, Predicates, Predicates | |
705 @section Type Predicates | |
706 | |
707 @noindent | |
708 The @dfn{CL} package defines a version of the Common Lisp @code{typep} | |
709 predicate. | |
710 | |
711 @defun typep object type | |
712 Check if @var{object} is of type @var{type}, where @var{type} is a | |
713 (quoted) type name of the sort used by Common Lisp. For example, | |
714 @code{(typep foo 'integer)} is equivalent to @code{(integerp foo)}. | |
715 @end defun | |
716 | |
717 The @var{type} argument to the above function is either a symbol | |
718 or a list beginning with a symbol. | |
719 | |
720 @itemize @bullet | |
721 @item | |
722 If the type name is a symbol, Emacs appends @samp{-p} to the | |
723 symbol name to form the name of a predicate function for testing | |
724 the type. (Built-in predicates whose names end in @samp{p} rather | |
725 than @samp{-p} are used when appropriate.) | |
726 | |
727 @item | |
728 The type symbol @code{t} stands for the union of all types. | |
729 @code{(typep @var{object} t)} is always true. Likewise, the | |
730 type symbol @code{nil} stands for nothing at all, and | |
731 @code{(typep @var{object} nil)} is always false. | |
732 | |
733 @item | |
734 The type symbol @code{null} represents the symbol @code{nil}. | |
735 Thus @code{(typep @var{object} 'null)} is equivalent to | |
736 @code{(null @var{object})}. | |
737 | |
738 @item | |
64366
c1cb0b064667
(Type Predicates): Document `atom' type.
Eli Zaretskii <eliz@gnu.org>
parents:
61442
diff
changeset
|
739 The type symbol @code{atom} represents all objects that are not cons |
c1cb0b064667
(Type Predicates): Document `atom' type.
Eli Zaretskii <eliz@gnu.org>
parents:
61442
diff
changeset
|
740 cells. Thus @code{(typep @var{object} 'atom)} is equivalent to |
c1cb0b064667
(Type Predicates): Document `atom' type.
Eli Zaretskii <eliz@gnu.org>
parents:
61442
diff
changeset
|
741 @code{(atom @var{object})}. |
c1cb0b064667
(Type Predicates): Document `atom' type.
Eli Zaretskii <eliz@gnu.org>
parents:
61442
diff
changeset
|
742 |
c1cb0b064667
(Type Predicates): Document `atom' type.
Eli Zaretskii <eliz@gnu.org>
parents:
61442
diff
changeset
|
743 @item |
25829 | 744 The type symbol @code{real} is a synonym for @code{number}, and |
745 @code{fixnum} is a synonym for @code{integer}. | |
746 | |
747 @item | |
748 The type symbols @code{character} and @code{string-char} match | |
749 integers in the range from 0 to 255. | |
750 | |
751 @item | |
752 The type symbol @code{float} uses the @code{floatp-safe} predicate | |
753 defined by this package rather than @code{floatp}, so it will work | |
754 correctly even in Emacs versions without floating-point support. | |
755 | |
756 @item | |
757 The type list @code{(integer @var{low} @var{high})} represents all | |
758 integers between @var{low} and @var{high}, inclusive. Either bound | |
759 may be a list of a single integer to specify an exclusive limit, | |
760 or a @code{*} to specify no limit. The type @code{(integer * *)} | |
761 is thus equivalent to @code{integer}. | |
762 | |
763 @item | |
764 Likewise, lists beginning with @code{float}, @code{real}, or | |
765 @code{number} represent numbers of that type falling in a particular | |
766 range. | |
767 | |
768 @item | |
769 Lists beginning with @code{and}, @code{or}, and @code{not} form | |
770 combinations of types. For example, @code{(or integer (float 0 *))} | |
771 represents all objects that are integers or non-negative floats. | |
772 | |
773 @item | |
774 Lists beginning with @code{member} or @code{member*} represent | |
775 objects @code{eql} to any of the following values. For example, | |
776 @code{(member 1 2 3 4)} is equivalent to @code{(integer 1 4)}, | |
777 and @code{(member nil)} is equivalent to @code{null}. | |
778 | |
779 @item | |
780 Lists of the form @code{(satisfies @var{predicate})} represent | |
781 all objects for which @var{predicate} returns true when called | |
782 with that object as an argument. | |
783 @end itemize | |
784 | |
785 The following function and macro (not technically predicates) are | |
786 related to @code{typep}. | |
787 | |
788 @defun coerce object type | |
789 This function attempts to convert @var{object} to the specified | |
790 @var{type}. If @var{object} is already of that type as determined by | |
791 @code{typep}, it is simply returned. Otherwise, certain types of | |
792 conversions will be made: If @var{type} is any sequence type | |
793 (@code{string}, @code{list}, etc.) then @var{object} will be | |
794 converted to that type if possible. If @var{type} is | |
795 @code{character}, then strings of length one and symbols with | |
796 one-character names can be coerced. If @var{type} is @code{float}, | |
797 then integers can be coerced in versions of Emacs that support | |
798 floats. In all other circumstances, @code{coerce} signals an | |
799 error. | |
800 @end defun | |
801 | |
802 @defspec deftype name arglist forms... | |
803 This macro defines a new type called @var{name}. It is similar | |
804 to @code{defmacro} in many ways; when @var{name} is encountered | |
805 as a type name, the body @var{forms} are evaluated and should | |
806 return a type specifier that is equivalent to the type. The | |
807 @var{arglist} is a Common Lisp argument list of the sort accepted | |
808 by @code{defmacro*}. The type specifier @samp{(@var{name} @var{args}...)} | |
809 is expanded by calling the expander with those arguments; the type | |
810 symbol @samp{@var{name}} is expanded by calling the expander with | |
811 no arguments. The @var{arglist} is processed the same as for | |
812 @code{defmacro*} except that optional arguments without explicit | |
813 defaults use @code{*} instead of @code{nil} as the ``default'' | |
814 default. Some examples: | |
815 | |
816 @example | |
817 (deftype null () '(satisfies null)) ; predefined | |
818 (deftype list () '(or null cons)) ; predefined | |
819 (deftype unsigned-byte (&optional bits) | |
820 (list 'integer 0 (if (eq bits '*) bits (1- (lsh 1 bits))))) | |
821 (unsigned-byte 8) @equiv{} (integer 0 255) | |
822 (unsigned-byte) @equiv{} (integer 0 *) | |
823 unsigned-byte @equiv{} (integer 0 *) | |
824 @end example | |
825 | |
826 @noindent | |
827 The last example shows how the Common Lisp @code{unsigned-byte} | |
828 type specifier could be implemented if desired; this package does | |
829 not implement @code{unsigned-byte} by default. | |
830 @end defspec | |
831 | |
832 The @code{typecase} and @code{check-type} macros also use type | |
833 names. @xref{Conditionals}. @xref{Assertions}. The @code{map}, | |
834 @code{concatenate}, and @code{merge} functions take type-name | |
835 arguments to specify the type of sequence to return. @xref{Sequences}. | |
836 | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
837 @node Equality Predicates, , Type Predicates, Predicates |
25829 | 838 @section Equality Predicates |
839 | |
840 @noindent | |
841 This package defines two Common Lisp predicates, @code{eql} and | |
842 @code{equalp}. | |
843 | |
844 @defun eql a b | |
845 This function is almost the same as @code{eq}, except that if @var{a} | |
846 and @var{b} are numbers of the same type, it compares them for numeric | |
847 equality (as if by @code{equal} instead of @code{eq}). This makes a | |
848 difference only for versions of Emacs that are compiled with | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
849 floating-point support. Emacs floats are allocated |
25829 | 850 objects just like cons cells, which means that @code{(eq 3.0 3.0)} |
851 will not necessarily be true---if the two @code{3.0}s were allocated | |
852 separately, the pointers will be different even though the numbers are | |
853 the same. But @code{(eql 3.0 3.0)} will always be true. | |
854 | |
855 The types of the arguments must match, so @code{(eql 3 3.0)} is | |
856 still false. | |
857 | |
858 Note that Emacs integers are ``direct'' rather than allocated, which | |
859 basically means @code{(eq 3 3)} will always be true. Thus @code{eq} | |
860 and @code{eql} behave differently only if floating-point numbers are | |
861 involved, and are indistinguishable on Emacs versions that don't | |
862 support floats. | |
863 | |
864 There is a slight inconsistency with Common Lisp in the treatment of | |
865 positive and negative zeros. Some machines, notably those with IEEE | |
866 standard arithmetic, represent @code{+0} and @code{-0} as distinct | |
867 values. Normally this doesn't matter because the standard specifies | |
868 that @code{(= 0.0 -0.0)} should always be true, and this is indeed | |
869 what Emacs Lisp and Common Lisp do. But the Common Lisp standard | |
870 states that @code{(eql 0.0 -0.0)} and @code{(equal 0.0 -0.0)} should | |
871 be false on IEEE-like machines; Emacs Lisp does not do this, and in | |
872 fact the only known way to distinguish between the two zeros in Emacs | |
873 Lisp is to @code{format} them and check for a minus sign. | |
874 @end defun | |
875 | |
876 @defun equalp a b | |
877 This function is a more flexible version of @code{equal}. In | |
878 particular, it compares strings case-insensitively, and it compares | |
879 numbers without regard to type (so that @code{(equalp 3 3.0)} is | |
880 true). Vectors and conses are compared recursively. All other | |
881 objects are compared as if by @code{equal}. | |
882 | |
883 This function differs from Common Lisp @code{equalp} in several | |
884 respects. First, Common Lisp's @code{equalp} also compares | |
885 @emph{characters} case-insensitively, which would be impractical | |
886 in this package since Emacs does not distinguish between integers | |
887 and characters. In keeping with the idea that strings are less | |
888 vector-like in Emacs Lisp, this package's @code{equalp} also will | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
889 not compare strings against vectors of integers. |
25829 | 890 @end defun |
891 | |
892 Also note that the Common Lisp functions @code{member} and @code{assoc} | |
893 use @code{eql} to compare elements, whereas Emacs Lisp follows the | |
894 MacLisp tradition and uses @code{equal} for these two functions. | |
895 In Emacs, use @code{member*} and @code{assoc*} to get functions | |
896 which use @code{eql} for comparisons. | |
897 | |
898 @node Control Structure, Macros, Predicates, Top | |
899 @chapter Control Structure | |
900 | |
901 @noindent | |
902 The features described in the following sections implement | |
903 various advanced control structures, including the powerful | |
904 @code{setf} facility and a number of looping and conditional | |
905 constructs. | |
906 | |
907 @menu | |
908 * Assignment:: The `psetq' form | |
909 * Generalized Variables:: `setf', `incf', `push', etc. | |
910 * Variable Bindings:: `progv', `lexical-let', `flet', `macrolet' | |
911 * Conditionals:: `case', `typecase' | |
912 * Blocks and Exits:: `block', `return', `return-from' | |
27511
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
913 * Iteration:: `do', `dotimes', `dolist', `do-symbols' |
25829 | 914 * Loop Facility:: The Common Lisp `loop' macro |
915 * Multiple Values:: `values', `multiple-value-bind', etc. | |
916 @end menu | |
917 | |
918 @node Assignment, Generalized Variables, Control Structure, Control Structure | |
919 @section Assignment | |
920 | |
921 @noindent | |
922 The @code{psetq} form is just like @code{setq}, except that multiple | |
923 assignments are done in parallel rather than sequentially. | |
924 | |
925 @defspec psetq [symbol form]@dots{} | |
926 This special form (actually a macro) is used to assign to several | |
927 variables simultaneously. Given only one @var{symbol} and @var{form}, | |
928 it has the same effect as @code{setq}. Given several @var{symbol} | |
929 and @var{form} pairs, it evaluates all the @var{form}s in advance | |
930 and then stores the corresponding variables afterwards. | |
931 | |
932 @example | |
933 (setq x 2 y 3) | |
934 (setq x (+ x y) y (* x y)) | |
935 x | |
936 @result{} 5 | |
937 y ; @r{@code{y} was computed after @code{x} was set.} | |
938 @result{} 15 | |
939 (setq x 2 y 3) | |
940 (psetq x (+ x y) y (* x y)) | |
941 x | |
942 @result{} 5 | |
943 y ; @r{@code{y} was computed before @code{x} was set.} | |
944 @result{} 6 | |
945 @end example | |
946 | |
947 The simplest use of @code{psetq} is @code{(psetq x y y x)}, which | |
948 exchanges the values of two variables. (The @code{rotatef} form | |
949 provides an even more convenient way to swap two variables; | |
950 @pxref{Modify Macros}.) | |
951 | |
952 @code{psetq} always returns @code{nil}. | |
953 @end defspec | |
954 | |
955 @node Generalized Variables, Variable Bindings, Assignment, Control Structure | |
956 @section Generalized Variables | |
957 | |
958 @noindent | |
959 A ``generalized variable'' or ``place form'' is one of the many places | |
960 in Lisp memory where values can be stored. The simplest place form is | |
961 a regular Lisp variable. But the cars and cdrs of lists, elements | |
962 of arrays, properties of symbols, and many other locations are also | |
963 places where Lisp values are stored. | |
964 | |
965 The @code{setf} form is like @code{setq}, except that it accepts | |
966 arbitrary place forms on the left side rather than just | |
967 symbols. For example, @code{(setf (car a) b)} sets the car of | |
968 @code{a} to @code{b}, doing the same operation as @code{(setcar a b)} | |
969 but without having to remember two separate functions for setting | |
970 and accessing every type of place. | |
971 | |
972 Generalized variables are analogous to ``lvalues'' in the C | |
973 language, where @samp{x = a[i]} gets an element from an array | |
974 and @samp{a[i] = x} stores an element using the same notation. | |
975 Just as certain forms like @code{a[i]} can be lvalues in C, there | |
976 is a set of forms that can be generalized variables in Lisp. | |
977 | |
978 @menu | |
979 * Basic Setf:: `setf' and place forms | |
980 * Modify Macros:: `incf', `push', `rotatef', `letf', `callf', etc. | |
981 * Customizing Setf:: `define-modify-macro', `defsetf', `define-setf-method' | |
982 @end menu | |
983 | |
984 @node Basic Setf, Modify Macros, Generalized Variables, Generalized Variables | |
985 @subsection Basic Setf | |
986 | |
987 @noindent | |
988 The @code{setf} macro is the most basic way to operate on generalized | |
989 variables. | |
990 | |
991 @defspec setf [place form]@dots{} | |
992 This macro evaluates @var{form} and stores it in @var{place}, which | |
993 must be a valid generalized variable form. If there are several | |
994 @var{place} and @var{form} pairs, the assignments are done sequentially | |
995 just as with @code{setq}. @code{setf} returns the value of the last | |
996 @var{form}. | |
997 | |
998 The following Lisp forms will work as generalized variables, and | |
60927
bae786986f2e
* calc.texi, cl.texi, gnus.texi, idlwave.texi, reftex.texi: Replace
Werner LEMBERG <wl@gnu.org>
parents:
55833
diff
changeset
|
999 so may appear in the @var{place} argument of @code{setf}: |
25829 | 1000 |
1001 @itemize @bullet | |
1002 @item | |
1003 A symbol naming a variable. In other words, @code{(setf x y)} is | |
1004 exactly equivalent to @code{(setq x y)}, and @code{setq} itself is | |
1005 strictly speaking redundant now that @code{setf} exists. Many | |
1006 programmers continue to prefer @code{setq} for setting simple | |
1007 variables, though, purely for stylistic or historical reasons. | |
1008 The macro @code{(setf x y)} actually expands to @code{(setq x y)}, | |
1009 so there is no performance penalty for using it in compiled code. | |
1010 | |
1011 @item | |
1012 A call to any of the following Lisp functions: | |
1013 | |
1014 @smallexample | |
1015 car cdr caar .. cddddr | |
1016 nth rest first .. tenth | |
1017 aref elt nthcdr | |
1018 symbol-function symbol-value symbol-plist | |
1019 get get* getf | |
1020 gethash subseq | |
1021 @end smallexample | |
1022 | |
1023 @noindent | |
1024 Note that for @code{nthcdr} and @code{getf}, the list argument | |
1025 of the function must itself be a valid @var{place} form. For | |
1026 example, @code{(setf (nthcdr 0 foo) 7)} will set @code{foo} itself | |
1027 to 7. Note that @code{push} and @code{pop} on an @code{nthcdr} | |
1028 place can be used to insert or delete at any position in a list. | |
1029 The use of @code{nthcdr} as a @var{place} form is an extension | |
1030 to standard Common Lisp. | |
1031 | |
1032 @item | |
1033 The following Emacs-specific functions are also @code{setf}-able. | |
1034 | |
1035 @smallexample | |
49600
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1036 buffer-file-name marker-position |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1037 buffer-modified-p match-data |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1038 buffer-name mouse-position |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1039 buffer-string overlay-end |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1040 buffer-substring overlay-get |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1041 current-buffer overlay-start |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1042 current-case-table point |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1043 current-column point-marker |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1044 current-global-map point-max |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1045 current-input-mode point-min |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1046 current-local-map process-buffer |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1047 current-window-configuration process-filter |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1048 default-file-modes process-sentinel |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1049 default-value read-mouse-position |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1050 documentation-property screen-height |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1051 extent-data screen-menubar |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1052 extent-end-position screen-width |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1053 extent-start-position selected-window |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1054 face-background selected-screen |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1055 face-background-pixmap selected-frame |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1056 face-font standard-case-table |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1057 face-foreground syntax-table |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1058 face-underline-p window-buffer |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1059 file-modes window-dedicated-p |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1060 frame-height window-display-table |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1061 frame-parameters window-height |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1062 frame-visible-p window-hscroll |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1063 frame-width window-point |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1064 get-register window-start |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1065 getenv window-width |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1066 global-key-binding x-get-cut-buffer |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1067 keymap-parent x-get-cutbuffer |
25829 | 1068 local-key-binding x-get-secondary-selection |
49600
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1069 mark x-get-selection |
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
1070 mark-marker |
25829 | 1071 @end smallexample |
1072 | |
1073 Most of these have directly corresponding ``set'' functions, like | |
1074 @code{use-local-map} for @code{current-local-map}, or @code{goto-char} | |
1075 for @code{point}. A few, like @code{point-min}, expand to longer | |
1076 sequences of code when they are @code{setf}'d (@code{(narrow-to-region | |
1077 x (point-max))} in this case). | |
1078 | |
1079 @item | |
1080 A call of the form @code{(substring @var{subplace} @var{n} [@var{m}])}, | |
60927
bae786986f2e
* calc.texi, cl.texi, gnus.texi, idlwave.texi, reftex.texi: Replace
Werner LEMBERG <wl@gnu.org>
parents:
55833
diff
changeset
|
1081 where @var{subplace} is itself a valid generalized variable whose |
25829 | 1082 current value is a string, and where the value stored is also a |
1083 string. The new string is spliced into the specified part of the | |
1084 destination string. For example: | |
1085 | |
1086 @example | |
1087 (setq a (list "hello" "world")) | |
1088 @result{} ("hello" "world") | |
1089 (cadr a) | |
1090 @result{} "world" | |
1091 (substring (cadr a) 2 4) | |
1092 @result{} "rl" | |
1093 (setf (substring (cadr a) 2 4) "o") | |
1094 @result{} "o" | |
1095 (cadr a) | |
1096 @result{} "wood" | |
1097 a | |
1098 @result{} ("hello" "wood") | |
1099 @end example | |
1100 | |
1101 The generalized variable @code{buffer-substring}, listed above, | |
1102 also works in this way by replacing a portion of the current buffer. | |
1103 | |
1104 @item | |
1105 A call of the form @code{(apply '@var{func} @dots{})} or | |
1106 @code{(apply (function @var{func}) @dots{})}, where @var{func} | |
1107 is a @code{setf}-able function whose store function is ``suitable'' | |
1108 in the sense described in Steele's book; since none of the standard | |
1109 Emacs place functions are suitable in this sense, this feature is | |
1110 only interesting when used with places you define yourself with | |
1111 @code{define-setf-method} or the long form of @code{defsetf}. | |
1112 | |
1113 @item | |
1114 A macro call, in which case the macro is expanded and @code{setf} | |
1115 is applied to the resulting form. | |
1116 | |
1117 @item | |
1118 Any form for which a @code{defsetf} or @code{define-setf-method} | |
1119 has been made. | |
1120 @end itemize | |
1121 | |
1122 Using any forms other than these in the @var{place} argument to | |
1123 @code{setf} will signal an error. | |
1124 | |
1125 The @code{setf} macro takes care to evaluate all subforms in | |
1126 the proper left-to-right order; for example, | |
1127 | |
1128 @example | |
1129 (setf (aref vec (incf i)) i) | |
1130 @end example | |
1131 | |
1132 @noindent | |
1133 looks like it will evaluate @code{(incf i)} exactly once, before the | |
1134 following access to @code{i}; the @code{setf} expander will insert | |
1135 temporary variables as necessary to ensure that it does in fact work | |
1136 this way no matter what setf-method is defined for @code{aref}. | |
1137 (In this case, @code{aset} would be used and no such steps would | |
1138 be necessary since @code{aset} takes its arguments in a convenient | |
1139 order.) | |
1140 | |
1141 However, if the @var{place} form is a macro which explicitly | |
1142 evaluates its arguments in an unusual order, this unusual order | |
1143 will be preserved. Adapting an example from Steele, given | |
1144 | |
1145 @example | |
1146 (defmacro wrong-order (x y) (list 'aref y x)) | |
1147 @end example | |
1148 | |
1149 @noindent | |
1150 the form @code{(setf (wrong-order @var{a} @var{b}) 17)} will | |
1151 evaluate @var{b} first, then @var{a}, just as in an actual call | |
1152 to @code{wrong-order}. | |
1153 @end defspec | |
1154 | |
1155 @node Modify Macros, Customizing Setf, Basic Setf, Generalized Variables | |
1156 @subsection Modify Macros | |
1157 | |
1158 @noindent | |
1159 This package defines a number of other macros besides @code{setf} | |
1160 that operate on generalized variables. Many are interesting and | |
1161 useful even when the @var{place} is just a variable name. | |
1162 | |
1163 @defspec psetf [place form]@dots{} | |
1164 This macro is to @code{setf} what @code{psetq} is to @code{setq}: | |
1165 When several @var{place}s and @var{form}s are involved, the | |
1166 assignments take place in parallel rather than sequentially. | |
1167 Specifically, all subforms are evaluated from left to right, then | |
1168 all the assignments are done (in an undefined order). | |
1169 @end defspec | |
1170 | |
1171 @defspec incf place &optional x | |
1172 This macro increments the number stored in @var{place} by one, or | |
1173 by @var{x} if specified. The incremented value is returned. For | |
1174 example, @code{(incf i)} is equivalent to @code{(setq i (1+ i))}, and | |
1175 @code{(incf (car x) 2)} is equivalent to @code{(setcar x (+ (car x) 2))}. | |
1176 | |
1177 Once again, care is taken to preserve the ``apparent'' order of | |
1178 evaluation. For example, | |
1179 | |
1180 @example | |
1181 (incf (aref vec (incf i))) | |
1182 @end example | |
1183 | |
1184 @noindent | |
1185 appears to increment @code{i} once, then increment the element of | |
1186 @code{vec} addressed by @code{i}; this is indeed exactly what it | |
1187 does, which means the above form is @emph{not} equivalent to the | |
1188 ``obvious'' expansion, | |
1189 | |
1190 @example | |
1191 (setf (aref vec (incf i)) (1+ (aref vec (incf i)))) ; Wrong! | |
1192 @end example | |
1193 | |
1194 @noindent | |
1195 but rather to something more like | |
1196 | |
1197 @example | |
1198 (let ((temp (incf i))) | |
1199 (setf (aref vec temp) (1+ (aref vec temp)))) | |
1200 @end example | |
1201 | |
1202 @noindent | |
1203 Again, all of this is taken care of automatically by @code{incf} and | |
1204 the other generalized-variable macros. | |
1205 | |
1206 As a more Emacs-specific example of @code{incf}, the expression | |
1207 @code{(incf (point) @var{n})} is essentially equivalent to | |
1208 @code{(forward-char @var{n})}. | |
1209 @end defspec | |
1210 | |
1211 @defspec decf place &optional x | |
1212 This macro decrements the number stored in @var{place} by one, or | |
1213 by @var{x} if specified. | |
1214 @end defspec | |
1215 | |
1216 @defspec pop place | |
1217 This macro removes and returns the first element of the list stored | |
1218 in @var{place}. It is analogous to @code{(prog1 (car @var{place}) | |
1219 (setf @var{place} (cdr @var{place})))}, except that it takes care | |
1220 to evaluate all subforms only once. | |
1221 @end defspec | |
1222 | |
1223 @defspec push x place | |
1224 This macro inserts @var{x} at the front of the list stored in | |
1225 @var{place}. It is analogous to @code{(setf @var{place} (cons | |
1226 @var{x} @var{place}))}, except for evaluation of the subforms. | |
1227 @end defspec | |
1228 | |
1229 @defspec pushnew x place @t{&key :test :test-not :key} | |
1230 This macro inserts @var{x} at the front of the list stored in | |
1231 @var{place}, but only if @var{x} was not @code{eql} to any | |
1232 existing element of the list. The optional keyword arguments | |
1233 are interpreted in the same way as for @code{adjoin}. | |
1234 @xref{Lists as Sets}. | |
1235 @end defspec | |
1236 | |
1237 @defspec shiftf place@dots{} newvalue | |
1238 This macro shifts the @var{place}s left by one, shifting in the | |
1239 value of @var{newvalue} (which may be any Lisp expression, not just | |
1240 a generalized variable), and returning the value shifted out of | |
1241 the first @var{place}. Thus, @code{(shiftf @var{a} @var{b} @var{c} | |
1242 @var{d})} is equivalent to | |
1243 | |
1244 @example | |
1245 (prog1 | |
1246 @var{a} | |
1247 (psetf @var{a} @var{b} | |
1248 @var{b} @var{c} | |
1249 @var{c} @var{d})) | |
1250 @end example | |
1251 | |
1252 @noindent | |
1253 except that the subforms of @var{a}, @var{b}, and @var{c} are actually | |
1254 evaluated only once each and in the apparent order. | |
1255 @end defspec | |
1256 | |
1257 @defspec rotatef place@dots{} | |
1258 This macro rotates the @var{place}s left by one in circular fashion. | |
1259 Thus, @code{(rotatef @var{a} @var{b} @var{c} @var{d})} is equivalent to | |
1260 | |
1261 @example | |
1262 (psetf @var{a} @var{b} | |
1263 @var{b} @var{c} | |
1264 @var{c} @var{d} | |
1265 @var{d} @var{a}) | |
1266 @end example | |
1267 | |
1268 @noindent | |
1269 except for the evaluation of subforms. @code{rotatef} always | |
1270 returns @code{nil}. Note that @code{(rotatef @var{a} @var{b})} | |
1271 conveniently exchanges @var{a} and @var{b}. | |
1272 @end defspec | |
1273 | |
1274 The following macros were invented for this package; they have no | |
1275 analogues in Common Lisp. | |
1276 | |
1277 @defspec letf (bindings@dots{}) forms@dots{} | |
1278 This macro is analogous to @code{let}, but for generalized variables | |
1279 rather than just symbols. Each @var{binding} should be of the form | |
1280 @code{(@var{place} @var{value})}; the original contents of the | |
1281 @var{place}s are saved, the @var{value}s are stored in them, and | |
1282 then the body @var{form}s are executed. Afterwards, the @var{places} | |
1283 are set back to their original saved contents. This cleanup happens | |
1284 even if the @var{form}s exit irregularly due to a @code{throw} or an | |
1285 error. | |
1286 | |
1287 For example, | |
1288 | |
1289 @example | |
1290 (letf (((point) (point-min)) | |
1291 (a 17)) | |
1292 ...) | |
1293 @end example | |
1294 | |
1295 @noindent | |
1296 moves ``point'' in the current buffer to the beginning of the buffer, | |
1297 and also binds @code{a} to 17 (as if by a normal @code{let}, since | |
1298 @code{a} is just a regular variable). After the body exits, @code{a} | |
1299 is set back to its original value and point is moved back to its | |
1300 original position. | |
1301 | |
1302 Note that @code{letf} on @code{(point)} is not quite like a | |
1303 @code{save-excursion}, as the latter effectively saves a marker | |
1304 which tracks insertions and deletions in the buffer. Actually, | |
1305 a @code{letf} of @code{(point-marker)} is much closer to this | |
1306 behavior. (@code{point} and @code{point-marker} are equivalent | |
1307 as @code{setf} places; each will accept either an integer or a | |
1308 marker as the stored value.) | |
1309 | |
1310 Since generalized variables look like lists, @code{let}'s shorthand | |
1311 of using @samp{foo} for @samp{(foo nil)} as a @var{binding} would | |
1312 be ambiguous in @code{letf} and is not allowed. | |
1313 | |
1314 However, a @var{binding} specifier may be a one-element list | |
1315 @samp{(@var{place})}, which is similar to @samp{(@var{place} | |
1316 @var{place})}. In other words, the @var{place} is not disturbed | |
1317 on entry to the body, and the only effect of the @code{letf} is | |
1318 to restore the original value of @var{place} afterwards. (The | |
1319 redundant access-and-store suggested by the @code{(@var{place} | |
1320 @var{place})} example does not actually occur.) | |
1321 | |
1322 In most cases, the @var{place} must have a well-defined value on | |
1323 entry to the @code{letf} form. The only exceptions are plain | |
1324 variables and calls to @code{symbol-value} and @code{symbol-function}. | |
1325 If the symbol is not bound on entry, it is simply made unbound by | |
1326 @code{makunbound} or @code{fmakunbound} on exit. | |
1327 @end defspec | |
1328 | |
1329 @defspec letf* (bindings@dots{}) forms@dots{} | |
1330 This macro is to @code{letf} what @code{let*} is to @code{let}: | |
1331 It does the bindings in sequential rather than parallel order. | |
1332 @end defspec | |
1333 | |
1334 @defspec callf @var{function} @var{place} @var{args}@dots{} | |
1335 This is the ``generic'' modify macro. It calls @var{function}, | |
1336 which should be an unquoted function name, macro name, or lambda. | |
1337 It passes @var{place} and @var{args} as arguments, and assigns the | |
1338 result back to @var{place}. For example, @code{(incf @var{place} | |
1339 @var{n})} is the same as @code{(callf + @var{place} @var{n})}. | |
1340 Some more examples: | |
1341 | |
1342 @example | |
1343 (callf abs my-number) | |
1344 (callf concat (buffer-name) "<" (int-to-string n) ">") | |
1345 (callf union happy-people (list joe bob) :test 'same-person) | |
1346 @end example | |
1347 | |
1348 @xref{Customizing Setf}, for @code{define-modify-macro}, a way | |
1349 to create even more concise notations for modify macros. Note | |
1350 again that @code{callf} is an extension to standard Common Lisp. | |
1351 @end defspec | |
1352 | |
1353 @defspec callf2 @var{function} @var{arg1} @var{place} @var{args}@dots{} | |
1354 This macro is like @code{callf}, except that @var{place} is | |
1355 the @emph{second} argument of @var{function} rather than the | |
1356 first. For example, @code{(push @var{x} @var{place})} is | |
1357 equivalent to @code{(callf2 cons @var{x} @var{place})}. | |
1358 @end defspec | |
1359 | |
1360 The @code{callf} and @code{callf2} macros serve as building | |
1361 blocks for other macros like @code{incf}, @code{pushnew}, and | |
1362 @code{define-modify-macro}. The @code{letf} and @code{letf*} | |
1363 macros are used in the processing of symbol macros; | |
1364 @pxref{Macro Bindings}. | |
1365 | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
1366 @node Customizing Setf, , Modify Macros, Generalized Variables |
25829 | 1367 @subsection Customizing Setf |
1368 | |
1369 @noindent | |
1370 Common Lisp defines three macros, @code{define-modify-macro}, | |
1371 @code{defsetf}, and @code{define-setf-method}, that allow the | |
1372 user to extend generalized variables in various ways. | |
1373 | |
1374 @defspec define-modify-macro name arglist function [doc-string] | |
1375 This macro defines a ``read-modify-write'' macro similar to | |
1376 @code{incf} and @code{decf}. The macro @var{name} is defined | |
1377 to take a @var{place} argument followed by additional arguments | |
1378 described by @var{arglist}. The call | |
1379 | |
1380 @example | |
1381 (@var{name} @var{place} @var{args}...) | |
1382 @end example | |
1383 | |
1384 @noindent | |
1385 will be expanded to | |
1386 | |
1387 @example | |
1388 (callf @var{func} @var{place} @var{args}...) | |
1389 @end example | |
1390 | |
1391 @noindent | |
1392 which in turn is roughly equivalent to | |
1393 | |
1394 @example | |
1395 (setf @var{place} (@var{func} @var{place} @var{args}...)) | |
1396 @end example | |
1397 | |
1398 For example: | |
1399 | |
1400 @example | |
1401 (define-modify-macro incf (&optional (n 1)) +) | |
1402 (define-modify-macro concatf (&rest args) concat) | |
1403 @end example | |
1404 | |
1405 Note that @code{&key} is not allowed in @var{arglist}, but | |
1406 @code{&rest} is sufficient to pass keywords on to the function. | |
1407 | |
1408 Most of the modify macros defined by Common Lisp do not exactly | |
1409 follow the pattern of @code{define-modify-macro}. For example, | |
1410 @code{push} takes its arguments in the wrong order, and @code{pop} | |
1411 is completely irregular. You can define these macros ``by hand'' | |
1412 using @code{get-setf-method}, or consult the source file | |
1413 @file{cl-macs.el} to see how to use the internal @code{setf} | |
1414 building blocks. | |
1415 @end defspec | |
1416 | |
1417 @defspec defsetf access-fn update-fn | |
1418 This is the simpler of two @code{defsetf} forms. Where | |
1419 @var{access-fn} is the name of a function which accesses a place, | |
1420 this declares @var{update-fn} to be the corresponding store | |
1421 function. From now on, | |
1422 | |
1423 @example | |
1424 (setf (@var{access-fn} @var{arg1} @var{arg2} @var{arg3}) @var{value}) | |
1425 @end example | |
1426 | |
1427 @noindent | |
1428 will be expanded to | |
1429 | |
1430 @example | |
1431 (@var{update-fn} @var{arg1} @var{arg2} @var{arg3} @var{value}) | |
1432 @end example | |
1433 | |
1434 @noindent | |
1435 The @var{update-fn} is required to be either a true function, or | |
1436 a macro which evaluates its arguments in a function-like way. Also, | |
1437 the @var{update-fn} is expected to return @var{value} as its result. | |
1438 Otherwise, the above expansion would not obey the rules for the way | |
1439 @code{setf} is supposed to behave. | |
1440 | |
1441 As a special (non-Common-Lisp) extension, a third argument of @code{t} | |
1442 to @code{defsetf} says that the @code{update-fn}'s return value is | |
1443 not suitable, so that the above @code{setf} should be expanded to | |
1444 something more like | |
1445 | |
1446 @example | |
1447 (let ((temp @var{value})) | |
1448 (@var{update-fn} @var{arg1} @var{arg2} @var{arg3} temp) | |
1449 temp) | |
1450 @end example | |
1451 | |
1452 Some examples of the use of @code{defsetf}, drawn from the standard | |
1453 suite of setf methods, are: | |
1454 | |
1455 @example | |
1456 (defsetf car setcar) | |
1457 (defsetf symbol-value set) | |
1458 (defsetf buffer-name rename-buffer t) | |
1459 @end example | |
1460 @end defspec | |
1461 | |
1462 @defspec defsetf access-fn arglist (store-var) forms@dots{} | |
1463 This is the second, more complex, form of @code{defsetf}. It is | |
1464 rather like @code{defmacro} except for the additional @var{store-var} | |
1465 argument. The @var{forms} should return a Lisp form which stores | |
1466 the value of @var{store-var} into the generalized variable formed | |
1467 by a call to @var{access-fn} with arguments described by @var{arglist}. | |
1468 The @var{forms} may begin with a string which documents the @code{setf} | |
1469 method (analogous to the doc string that appears at the front of a | |
1470 function). | |
1471 | |
1472 For example, the simple form of @code{defsetf} is shorthand for | |
1473 | |
1474 @example | |
1475 (defsetf @var{access-fn} (&rest args) (store) | |
1476 (append '(@var{update-fn}) args (list store))) | |
1477 @end example | |
1478 | |
1479 The Lisp form that is returned can access the arguments from | |
1480 @var{arglist} and @var{store-var} in an unrestricted fashion; | |
1481 macros like @code{setf} and @code{incf} which invoke this | |
1482 setf-method will insert temporary variables as needed to make | |
1483 sure the apparent order of evaluation is preserved. | |
1484 | |
1485 Another example drawn from the standard package: | |
1486 | |
1487 @example | |
1488 (defsetf nth (n x) (store) | |
1489 (list 'setcar (list 'nthcdr n x) store)) | |
1490 @end example | |
1491 @end defspec | |
1492 | |
1493 @defspec define-setf-method access-fn arglist forms@dots{} | |
1494 This is the most general way to create new place forms. When | |
1495 a @code{setf} to @var{access-fn} with arguments described by | |
1496 @var{arglist} is expanded, the @var{forms} are evaluated and | |
1497 must return a list of five items: | |
1498 | |
1499 @enumerate | |
1500 @item | |
1501 A list of @dfn{temporary variables}. | |
1502 | |
1503 @item | |
1504 A list of @dfn{value forms} corresponding to the temporary variables | |
1505 above. The temporary variables will be bound to these value forms | |
1506 as the first step of any operation on the generalized variable. | |
1507 | |
1508 @item | |
1509 A list of exactly one @dfn{store variable} (generally obtained | |
1510 from a call to @code{gensym}). | |
1511 | |
1512 @item | |
1513 A Lisp form which stores the contents of the store variable into | |
1514 the generalized variable, assuming the temporaries have been | |
1515 bound as described above. | |
1516 | |
1517 @item | |
1518 A Lisp form which accesses the contents of the generalized variable, | |
1519 assuming the temporaries have been bound. | |
1520 @end enumerate | |
1521 | |
1522 This is exactly like the Common Lisp macro of the same name, | |
1523 except that the method returns a list of five values rather | |
1524 than the five values themselves, since Emacs Lisp does not | |
1525 support Common Lisp's notion of multiple return values. | |
1526 | |
1527 Once again, the @var{forms} may begin with a documentation string. | |
1528 | |
1529 A setf-method should be maximally conservative with regard to | |
1530 temporary variables. In the setf-methods generated by | |
1531 @code{defsetf}, the second return value is simply the list of | |
1532 arguments in the place form, and the first return value is a | |
1533 list of a corresponding number of temporary variables generated | |
1534 by @code{gensym}. Macros like @code{setf} and @code{incf} which | |
1535 use this setf-method will optimize away most temporaries that | |
1536 turn out to be unnecessary, so there is little reason for the | |
1537 setf-method itself to optimize. | |
1538 @end defspec | |
1539 | |
1540 @defun get-setf-method place &optional env | |
1541 This function returns the setf-method for @var{place}, by | |
1542 invoking the definition previously recorded by @code{defsetf} | |
1543 or @code{define-setf-method}. The result is a list of five | |
1544 values as described above. You can use this function to build | |
1545 your own @code{incf}-like modify macros. (Actually, it is | |
1546 better to use the internal functions @code{cl-setf-do-modify} | |
1547 and @code{cl-setf-do-store}, which are a bit easier to use and | |
1548 which also do a number of optimizations; consult the source | |
1549 code for the @code{incf} function for a simple example.) | |
1550 | |
1551 The argument @var{env} specifies the ``environment'' to be | |
1552 passed on to @code{macroexpand} if @code{get-setf-method} should | |
1553 need to expand a macro in @var{place}. It should come from | |
1554 an @code{&environment} argument to the macro or setf-method | |
1555 that called @code{get-setf-method}. | |
1556 | |
1557 See also the source code for the setf-methods for @code{apply} | |
1558 and @code{substring}, each of which works by calling | |
1559 @code{get-setf-method} on a simpler case, then massaging | |
1560 the result in various ways. | |
1561 @end defun | |
1562 | |
1563 Modern Common Lisp defines a second, independent way to specify | |
1564 the @code{setf} behavior of a function, namely ``@code{setf} | |
1565 functions'' whose names are lists @code{(setf @var{name})} | |
1566 rather than symbols. For example, @code{(defun (setf foo) @dots{})} | |
1567 defines the function that is used when @code{setf} is applied to | |
1568 @code{foo}. This package does not currently support @code{setf} | |
1569 functions. In particular, it is a compile-time error to use | |
1570 @code{setf} on a form which has not already been @code{defsetf}'d | |
1571 or otherwise declared; in newer Common Lisps, this would not be | |
1572 an error since the function @code{(setf @var{func})} might be | |
1573 defined later. | |
1574 | |
1575 @iftex | |
1576 @secno=4 | |
1577 @end iftex | |
1578 | |
1579 @node Variable Bindings, Conditionals, Generalized Variables, Control Structure | |
1580 @section Variable Bindings | |
1581 | |
1582 @noindent | |
1583 These Lisp forms make bindings to variables and function names, | |
1584 analogous to Lisp's built-in @code{let} form. | |
1585 | |
1586 @xref{Modify Macros}, for the @code{letf} and @code{letf*} forms which | |
1587 are also related to variable bindings. | |
1588 | |
1589 @menu | |
1590 * Dynamic Bindings:: The `progv' form | |
1591 * Lexical Bindings:: `lexical-let' and lexical closures | |
1592 * Function Bindings:: `flet' and `labels' | |
1593 * Macro Bindings:: `macrolet' and `symbol-macrolet' | |
1594 @end menu | |
1595 | |
1596 @node Dynamic Bindings, Lexical Bindings, Variable Bindings, Variable Bindings | |
1597 @subsection Dynamic Bindings | |
1598 | |
1599 @noindent | |
1600 The standard @code{let} form binds variables whose names are known | |
1601 at compile-time. The @code{progv} form provides an easy way to | |
1602 bind variables whose names are computed at run-time. | |
1603 | |
1604 @defspec progv symbols values forms@dots{} | |
1605 This form establishes @code{let}-style variable bindings on a | |
1606 set of variables computed at run-time. The expressions | |
1607 @var{symbols} and @var{values} are evaluated, and must return lists | |
1608 of symbols and values, respectively. The symbols are bound to the | |
1609 corresponding values for the duration of the body @var{form}s. | |
1610 If @var{values} is shorter than @var{symbols}, the last few symbols | |
1611 are made unbound (as if by @code{makunbound}) inside the body. | |
1612 If @var{symbols} is shorter than @var{values}, the excess values | |
1613 are ignored. | |
1614 @end defspec | |
1615 | |
1616 @node Lexical Bindings, Function Bindings, Dynamic Bindings, Variable Bindings | |
1617 @subsection Lexical Bindings | |
1618 | |
1619 @noindent | |
1620 The @dfn{CL} package defines the following macro which | |
1621 more closely follows the Common Lisp @code{let} form: | |
1622 | |
1623 @defspec lexical-let (bindings@dots{}) forms@dots{} | |
1624 This form is exactly like @code{let} except that the bindings it | |
1625 establishes are purely lexical. Lexical bindings are similar to | |
1626 local variables in a language like C: Only the code physically | |
1627 within the body of the @code{lexical-let} (after macro expansion) | |
1628 may refer to the bound variables. | |
1629 | |
1630 @example | |
1631 (setq a 5) | |
1632 (defun foo (b) (+ a b)) | |
1633 (let ((a 2)) (foo a)) | |
1634 @result{} 4 | |
1635 (lexical-let ((a 2)) (foo a)) | |
1636 @result{} 7 | |
1637 @end example | |
1638 | |
1639 @noindent | |
1640 In this example, a regular @code{let} binding of @code{a} actually | |
1641 makes a temporary change to the global variable @code{a}, so @code{foo} | |
1642 is able to see the binding of @code{a} to 2. But @code{lexical-let} | |
1643 actually creates a distinct local variable @code{a} for use within its | |
1644 body, without any effect on the global variable of the same name. | |
1645 | |
1646 The most important use of lexical bindings is to create @dfn{closures}. | |
1647 A closure is a function object that refers to an outside lexical | |
1648 variable. For example: | |
1649 | |
1650 @example | |
1651 (defun make-adder (n) | |
1652 (lexical-let ((n n)) | |
1653 (function (lambda (m) (+ n m))))) | |
1654 (setq add17 (make-adder 17)) | |
1655 (funcall add17 4) | |
1656 @result{} 21 | |
1657 @end example | |
1658 | |
1659 @noindent | |
1660 The call @code{(make-adder 17)} returns a function object which adds | |
1661 17 to its argument. If @code{let} had been used instead of | |
1662 @code{lexical-let}, the function object would have referred to the | |
1663 global @code{n}, which would have been bound to 17 only during the | |
1664 call to @code{make-adder} itself. | |
1665 | |
1666 @example | |
1667 (defun make-counter () | |
1668 (lexical-let ((n 0)) | |
1669 (function* (lambda (&optional (m 1)) (incf n m))))) | |
1670 (setq count-1 (make-counter)) | |
1671 (funcall count-1 3) | |
1672 @result{} 3 | |
1673 (funcall count-1 14) | |
1674 @result{} 17 | |
1675 (setq count-2 (make-counter)) | |
1676 (funcall count-2 5) | |
1677 @result{} 5 | |
1678 (funcall count-1 2) | |
1679 @result{} 19 | |
1680 (funcall count-2) | |
1681 @result{} 6 | |
1682 @end example | |
1683 | |
1684 @noindent | |
1685 Here we see that each call to @code{make-counter} creates a distinct | |
1686 local variable @code{n}, which serves as a private counter for the | |
1687 function object that is returned. | |
1688 | |
1689 Closed-over lexical variables persist until the last reference to | |
1690 them goes away, just like all other Lisp objects. For example, | |
1691 @code{count-2} refers to a function object which refers to an | |
1692 instance of the variable @code{n}; this is the only reference | |
1693 to that variable, so after @code{(setq count-2 nil)} the garbage | |
1694 collector would be able to delete this instance of @code{n}. | |
1695 Of course, if a @code{lexical-let} does not actually create any | |
1696 closures, then the lexical variables are free as soon as the | |
1697 @code{lexical-let} returns. | |
1698 | |
1699 Many closures are used only during the extent of the bindings they | |
1700 refer to; these are known as ``downward funargs'' in Lisp parlance. | |
1701 When a closure is used in this way, regular Emacs Lisp dynamic | |
1702 bindings suffice and will be more efficient than @code{lexical-let} | |
1703 closures: | |
1704 | |
1705 @example | |
1706 (defun add-to-list (x list) | |
28344
54fda0e8528a
Weed out redundant uses of `function'
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
28039
diff
changeset
|
1707 (mapcar (lambda (y) (+ x y))) list) |
25829 | 1708 (add-to-list 7 '(1 2 5)) |
1709 @result{} (8 9 12) | |
1710 @end example | |
1711 | |
1712 @noindent | |
1713 Since this lambda is only used while @code{x} is still bound, | |
1714 it is not necessary to make a true closure out of it. | |
1715 | |
1716 You can use @code{defun} or @code{flet} inside a @code{lexical-let} | |
1717 to create a named closure. If several closures are created in the | |
1718 body of a single @code{lexical-let}, they all close over the same | |
1719 instance of the lexical variable. | |
1720 | |
1721 The @code{lexical-let} form is an extension to Common Lisp. In | |
1722 true Common Lisp, all bindings are lexical unless declared otherwise. | |
1723 @end defspec | |
1724 | |
1725 @defspec lexical-let* (bindings@dots{}) forms@dots{} | |
1726 This form is just like @code{lexical-let}, except that the bindings | |
1727 are made sequentially in the manner of @code{let*}. | |
1728 @end defspec | |
1729 | |
1730 @node Function Bindings, Macro Bindings, Lexical Bindings, Variable Bindings | |
1731 @subsection Function Bindings | |
1732 | |
1733 @noindent | |
1734 These forms make @code{let}-like bindings to functions instead | |
1735 of variables. | |
1736 | |
1737 @defspec flet (bindings@dots{}) forms@dots{} | |
1738 This form establishes @code{let}-style bindings on the function | |
1739 cells of symbols rather than on the value cells. Each @var{binding} | |
1740 must be a list of the form @samp{(@var{name} @var{arglist} | |
1741 @var{forms}@dots{})}, which defines a function exactly as if | |
1742 it were a @code{defun*} form. The function @var{name} is defined | |
1743 accordingly for the duration of the body of the @code{flet}; then | |
1744 the old function definition, or lack thereof, is restored. | |
1745 | |
1746 While @code{flet} in Common Lisp establishes a lexical binding of | |
1747 @var{name}, Emacs Lisp @code{flet} makes a dynamic binding. The | |
1748 result is that @code{flet} affects indirect calls to a function as | |
1749 well as calls directly inside the @code{flet} form itself. | |
1750 | |
1751 You can use @code{flet} to disable or modify the behavior of a | |
1752 function in a temporary fashion. This will even work on Emacs | |
1753 primitives, although note that some calls to primitive functions | |
1754 internal to Emacs are made without going through the symbol's | |
1755 function cell, and so will not be affected by @code{flet}. For | |
1756 example, | |
1757 | |
1758 @example | |
1759 (flet ((message (&rest args) (push args saved-msgs))) | |
1760 (do-something)) | |
1761 @end example | |
1762 | |
1763 This code attempts to replace the built-in function @code{message} | |
1764 with a function that simply saves the messages in a list rather | |
1765 than displaying them. The original definition of @code{message} | |
1766 will be restored after @code{do-something} exits. This code will | |
1767 work fine on messages generated by other Lisp code, but messages | |
1768 generated directly inside Emacs will not be caught since they make | |
1769 direct C-language calls to the message routines rather than going | |
1770 through the Lisp @code{message} function. | |
1771 | |
1772 Functions defined by @code{flet} may use the full Common Lisp | |
1773 argument notation supported by @code{defun*}; also, the function | |
1774 body is enclosed in an implicit block as if by @code{defun*}. | |
1775 @xref{Program Structure}. | |
1776 @end defspec | |
1777 | |
1778 @defspec labels (bindings@dots{}) forms@dots{} | |
1779 The @code{labels} form is like @code{flet}, except that it | |
1780 makes lexical bindings of the function names rather than | |
1781 dynamic bindings. (In true Common Lisp, both @code{flet} and | |
1782 @code{labels} make lexical bindings of slightly different sorts; | |
1783 since Emacs Lisp is dynamically bound by default, it seemed | |
1784 more appropriate for @code{flet} also to use dynamic binding. | |
1785 The @code{labels} form, with its lexical binding, is fully | |
1786 compatible with Common Lisp.) | |
1787 | |
1788 Lexical scoping means that all references to the named | |
1789 functions must appear physically within the body of the | |
1790 @code{labels} form. References may appear both in the body | |
1791 @var{forms} of @code{labels} itself, and in the bodies of | |
1792 the functions themselves. Thus, @code{labels} can define | |
1793 local recursive functions, or mutually-recursive sets of | |
1794 functions. | |
1795 | |
1796 A ``reference'' to a function name is either a call to that | |
1797 function, or a use of its name quoted by @code{quote} or | |
1798 @code{function} to be passed on to, say, @code{mapcar}. | |
1799 @end defspec | |
1800 | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
1801 @node Macro Bindings, , Function Bindings, Variable Bindings |
25829 | 1802 @subsection Macro Bindings |
1803 | |
1804 @noindent | |
1805 These forms create local macros and ``symbol macros.'' | |
1806 | |
1807 @defspec macrolet (bindings@dots{}) forms@dots{} | |
1808 This form is analogous to @code{flet}, but for macros instead of | |
1809 functions. Each @var{binding} is a list of the same form as the | |
1810 arguments to @code{defmacro*} (i.e., a macro name, argument list, | |
1811 and macro-expander forms). The macro is defined accordingly for | |
1812 use within the body of the @code{macrolet}. | |
1813 | |
1814 Because of the nature of macros, @code{macrolet} is lexically | |
1815 scoped even in Emacs Lisp: The @code{macrolet} binding will | |
1816 affect only calls that appear physically within the body | |
1817 @var{forms}, possibly after expansion of other macros in the | |
1818 body. | |
1819 @end defspec | |
1820 | |
1821 @defspec symbol-macrolet (bindings@dots{}) forms@dots{} | |
1822 This form creates @dfn{symbol macros}, which are macros that look | |
1823 like variable references rather than function calls. Each | |
1824 @var{binding} is a list @samp{(@var{var} @var{expansion})}; | |
1825 any reference to @var{var} within the body @var{forms} is | |
1826 replaced by @var{expansion}. | |
1827 | |
1828 @example | |
1829 (setq bar '(5 . 9)) | |
1830 (symbol-macrolet ((foo (car bar))) | |
1831 (incf foo)) | |
1832 bar | |
1833 @result{} (6 . 9) | |
1834 @end example | |
1835 | |
1836 A @code{setq} of a symbol macro is treated the same as a @code{setf}. | |
1837 I.e., @code{(setq foo 4)} in the above would be equivalent to | |
1838 @code{(setf foo 4)}, which in turn expands to @code{(setf (car bar) 4)}. | |
1839 | |
1840 Likewise, a @code{let} or @code{let*} binding a symbol macro is | |
1841 treated like a @code{letf} or @code{letf*}. This differs from true | |
1842 Common Lisp, where the rules of lexical scoping cause a @code{let} | |
1843 binding to shadow a @code{symbol-macrolet} binding. In this package, | |
1844 only @code{lexical-let} and @code{lexical-let*} will shadow a symbol | |
1845 macro. | |
1846 | |
1847 There is no analogue of @code{defmacro} for symbol macros; all symbol | |
1848 macros are local. A typical use of @code{symbol-macrolet} is in the | |
1849 expansion of another macro: | |
1850 | |
1851 @example | |
1852 (defmacro* my-dolist ((x list) &rest body) | |
1853 (let ((var (gensym))) | |
1854 (list 'loop 'for var 'on list 'do | |
1855 (list* 'symbol-macrolet (list (list x (list 'car var))) | |
1856 body)))) | |
1857 | |
1858 (setq mylist '(1 2 3 4)) | |
1859 (my-dolist (x mylist) (incf x)) | |
1860 mylist | |
1861 @result{} (2 3 4 5) | |
1862 @end example | |
1863 | |
1864 @noindent | |
1865 In this example, the @code{my-dolist} macro is similar to @code{dolist} | |
27511
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
1866 (@pxref{Iteration}) except that the variable @code{x} becomes a true |
25829 | 1867 reference onto the elements of the list. The @code{my-dolist} call |
1868 shown here expands to | |
1869 | |
1870 @example | |
1871 (loop for G1234 on mylist do | |
1872 (symbol-macrolet ((x (car G1234))) | |
1873 (incf x))) | |
1874 @end example | |
1875 | |
1876 @noindent | |
1877 which in turn expands to | |
1878 | |
1879 @example | |
1880 (loop for G1234 on mylist do (incf (car G1234))) | |
1881 @end example | |
1882 | |
1883 @xref{Loop Facility}, for a description of the @code{loop} macro. | |
1884 This package defines a nonstandard @code{in-ref} loop clause that | |
1885 works much like @code{my-dolist}. | |
1886 @end defspec | |
1887 | |
1888 @node Conditionals, Blocks and Exits, Variable Bindings, Control Structure | |
1889 @section Conditionals | |
1890 | |
1891 @noindent | |
1892 These conditional forms augment Emacs Lisp's simple @code{if}, | |
1893 @code{and}, @code{or}, and @code{cond} forms. | |
1894 | |
1895 @defspec case keyform clause@dots{} | |
1896 This macro evaluates @var{keyform}, then compares it with the key | |
1897 values listed in the various @var{clause}s. Whichever clause matches | |
1898 the key is executed; comparison is done by @code{eql}. If no clause | |
1899 matches, the @code{case} form returns @code{nil}. The clauses are | |
1900 of the form | |
1901 | |
1902 @example | |
1903 (@var{keylist} @var{body-forms}@dots{}) | |
1904 @end example | |
1905 | |
1906 @noindent | |
1907 where @var{keylist} is a list of key values. If there is exactly | |
1908 one value, and it is not a cons cell or the symbol @code{nil} or | |
1909 @code{t}, then it can be used by itself as a @var{keylist} without | |
1910 being enclosed in a list. All key values in the @code{case} form | |
1911 must be distinct. The final clauses may use @code{t} in place of | |
1912 a @var{keylist} to indicate a default clause that should be taken | |
1913 if none of the other clauses match. (The symbol @code{otherwise} | |
1914 is also recognized in place of @code{t}. To make a clause that | |
1915 matches the actual symbol @code{t}, @code{nil}, or @code{otherwise}, | |
1916 enclose the symbol in a list.) | |
1917 | |
1918 For example, this expression reads a keystroke, then does one of | |
1919 four things depending on whether it is an @samp{a}, a @samp{b}, | |
1920 a @key{RET} or @kbd{C-j}, or anything else. | |
1921 | |
1922 @example | |
1923 (case (read-char) | |
1924 (?a (do-a-thing)) | |
1925 (?b (do-b-thing)) | |
1926 ((?\r ?\n) (do-ret-thing)) | |
1927 (t (do-other-thing))) | |
1928 @end example | |
1929 @end defspec | |
1930 | |
1931 @defspec ecase keyform clause@dots{} | |
1932 This macro is just like @code{case}, except that if the key does | |
1933 not match any of the clauses, an error is signaled rather than | |
1934 simply returning @code{nil}. | |
1935 @end defspec | |
1936 | |
1937 @defspec typecase keyform clause@dots{} | |
1938 This macro is a version of @code{case} that checks for types | |
1939 rather than values. Each @var{clause} is of the form | |
1940 @samp{(@var{type} @var{body}...)}. @xref{Type Predicates}, | |
1941 for a description of type specifiers. For example, | |
1942 | |
1943 @example | |
1944 (typecase x | |
1945 (integer (munch-integer x)) | |
1946 (float (munch-float x)) | |
1947 (string (munch-integer (string-to-int x))) | |
1948 (t (munch-anything x))) | |
1949 @end example | |
1950 | |
1951 The type specifier @code{t} matches any type of object; the word | |
1952 @code{otherwise} is also allowed. To make one clause match any of | |
1953 several types, use an @code{(or ...)} type specifier. | |
1954 @end defspec | |
1955 | |
1956 @defspec etypecase keyform clause@dots{} | |
1957 This macro is just like @code{typecase}, except that if the key does | |
1958 not match any of the clauses, an error is signaled rather than | |
1959 simply returning @code{nil}. | |
1960 @end defspec | |
1961 | |
1962 @node Blocks and Exits, Iteration, Conditionals, Control Structure | |
1963 @section Blocks and Exits | |
1964 | |
1965 @noindent | |
1966 Common Lisp @dfn{blocks} provide a non-local exit mechanism very | |
1967 similar to @code{catch} and @code{throw}, but lexically rather than | |
1968 dynamically scoped. This package actually implements @code{block} | |
1969 in terms of @code{catch}; however, the lexical scoping allows the | |
1970 optimizing byte-compiler to omit the costly @code{catch} step if the | |
1971 body of the block does not actually @code{return-from} the block. | |
1972 | |
1973 @defspec block name forms@dots{} | |
1974 The @var{forms} are evaluated as if by a @code{progn}. However, | |
1975 if any of the @var{forms} execute @code{(return-from @var{name})}, | |
1976 they will jump out and return directly from the @code{block} form. | |
1977 The @code{block} returns the result of the last @var{form} unless | |
1978 a @code{return-from} occurs. | |
1979 | |
1980 The @code{block}/@code{return-from} mechanism is quite similar to | |
1981 the @code{catch}/@code{throw} mechanism. The main differences are | |
1982 that block @var{name}s are unevaluated symbols, rather than forms | |
1983 (such as quoted symbols) which evaluate to a tag at run-time; and | |
1984 also that blocks are lexically scoped whereas @code{catch}/@code{throw} | |
1985 are dynamically scoped. This means that functions called from the | |
1986 body of a @code{catch} can also @code{throw} to the @code{catch}, | |
1987 but the @code{return-from} referring to a block name must appear | |
1988 physically within the @var{forms} that make up the body of the block. | |
1989 They may not appear within other called functions, although they may | |
1990 appear within macro expansions or @code{lambda}s in the body. Block | |
1991 names and @code{catch} names form independent name-spaces. | |
1992 | |
1993 In true Common Lisp, @code{defun} and @code{defmacro} surround | |
1994 the function or expander bodies with implicit blocks with the | |
1995 same name as the function or macro. This does not occur in Emacs | |
1996 Lisp, but this package provides @code{defun*} and @code{defmacro*} | |
1997 forms which do create the implicit block. | |
1998 | |
1999 The Common Lisp looping constructs defined by this package, | |
27511
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2000 such as @code{loop} and @code{dolist}, also create implicit blocks |
25829 | 2001 just as in Common Lisp. |
2002 | |
2003 Because they are implemented in terms of Emacs Lisp @code{catch} | |
2004 and @code{throw}, blocks have the same overhead as actual | |
2005 @code{catch} constructs (roughly two function calls). However, | |
49600
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
47737
diff
changeset
|
2006 the optimizing byte compiler will optimize away the @code{catch} |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
2007 if the block does |
25829 | 2008 not in fact contain any @code{return} or @code{return-from} calls |
2009 that jump to it. This means that @code{do} loops and @code{defun*} | |
2010 functions which don't use @code{return} don't pay the overhead to | |
2011 support it. | |
2012 @end defspec | |
2013 | |
2014 @defspec return-from name [result] | |
2015 This macro returns from the block named @var{name}, which must be | |
2016 an (unevaluated) symbol. If a @var{result} form is specified, it | |
2017 is evaluated to produce the result returned from the @code{block}. | |
2018 Otherwise, @code{nil} is returned. | |
2019 @end defspec | |
2020 | |
2021 @defspec return [result] | |
2022 This macro is exactly like @code{(return-from nil @var{result})}. | |
27511
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2023 Common Lisp loops like @code{do} and @code{dolist} implicitly enclose |
25829 | 2024 themselves in @code{nil} blocks. |
2025 @end defspec | |
2026 | |
2027 @node Iteration, Loop Facility, Blocks and Exits, Control Structure | |
2028 @section Iteration | |
2029 | |
2030 @noindent | |
2031 The macros described here provide more sophisticated, high-level | |
2032 looping constructs to complement Emacs Lisp's basic @code{while} | |
2033 loop. | |
2034 | |
2035 @defspec loop forms@dots{} | |
2036 The @dfn{CL} package supports both the simple, old-style meaning of | |
2037 @code{loop} and the extremely powerful and flexible feature known as | |
2038 the @dfn{Loop Facility} or @dfn{Loop Macro}. This more advanced | |
2039 facility is discussed in the following section; @pxref{Loop Facility}. | |
2040 The simple form of @code{loop} is described here. | |
2041 | |
2042 If @code{loop} is followed by zero or more Lisp expressions, | |
2043 then @code{(loop @var{exprs}@dots{})} simply creates an infinite | |
2044 loop executing the expressions over and over. The loop is | |
2045 enclosed in an implicit @code{nil} block. Thus, | |
2046 | |
2047 @example | |
2048 (loop (foo) (if (no-more) (return 72)) (bar)) | |
2049 @end example | |
2050 | |
2051 @noindent | |
2052 is exactly equivalent to | |
2053 | |
2054 @example | |
2055 (block nil (while t (foo) (if (no-more) (return 72)) (bar))) | |
2056 @end example | |
2057 | |
2058 If any of the expressions are plain symbols, the loop is instead | |
2059 interpreted as a Loop Macro specification as described later. | |
2060 (This is not a restriction in practice, since a plain symbol | |
2061 in the above notation would simply access and throw away the | |
2062 value of a variable.) | |
2063 @end defspec | |
2064 | |
2065 @defspec do (spec@dots{}) (end-test [result@dots{}]) forms@dots{} | |
2066 This macro creates a general iterative loop. Each @var{spec} is | |
2067 of the form | |
2068 | |
2069 @example | |
2070 (@var{var} [@var{init} [@var{step}]]) | |
2071 @end example | |
2072 | |
2073 The loop works as follows: First, each @var{var} is bound to the | |
2074 associated @var{init} value as if by a @code{let} form. Then, in | |
2075 each iteration of the loop, the @var{end-test} is evaluated; if | |
2076 true, the loop is finished. Otherwise, the body @var{forms} are | |
2077 evaluated, then each @var{var} is set to the associated @var{step} | |
2078 expression (as if by a @code{psetq} form) and the next iteration | |
2079 begins. Once the @var{end-test} becomes true, the @var{result} | |
2080 forms are evaluated (with the @var{var}s still bound to their | |
2081 values) to produce the result returned by @code{do}. | |
2082 | |
2083 The entire @code{do} loop is enclosed in an implicit @code{nil} | |
2084 block, so that you can use @code{(return)} to break out of the | |
2085 loop at any time. | |
2086 | |
2087 If there are no @var{result} forms, the loop returns @code{nil}. | |
2088 If a given @var{var} has no @var{step} form, it is bound to its | |
2089 @var{init} value but not otherwise modified during the @code{do} | |
2090 loop (unless the code explicitly modifies it); this case is just | |
2091 a shorthand for putting a @code{(let ((@var{var} @var{init})) @dots{})} | |
2092 around the loop. If @var{init} is also omitted it defaults to | |
2093 @code{nil}, and in this case a plain @samp{@var{var}} can be used | |
2094 in place of @samp{(@var{var})}, again following the analogy with | |
2095 @code{let}. | |
2096 | |
2097 This example (from Steele) illustrates a loop which applies the | |
2098 function @code{f} to successive pairs of values from the lists | |
2099 @code{foo} and @code{bar}; it is equivalent to the call | |
2100 @code{(mapcar* 'f foo bar)}. Note that this loop has no body | |
2101 @var{forms} at all, performing all its work as side effects of | |
2102 the rest of the loop. | |
2103 | |
2104 @example | |
2105 (do ((x foo (cdr x)) | |
2106 (y bar (cdr y)) | |
2107 (z nil (cons (f (car x) (car y)) z))) | |
2108 ((or (null x) (null y)) | |
2109 (nreverse z))) | |
2110 @end example | |
2111 @end defspec | |
2112 | |
2113 @defspec do* (spec@dots{}) (end-test [result@dots{}]) forms@dots{} | |
2114 This is to @code{do} what @code{let*} is to @code{let}. In | |
2115 particular, the initial values are bound as if by @code{let*} | |
2116 rather than @code{let}, and the steps are assigned as if by | |
2117 @code{setq} rather than @code{psetq}. | |
2118 | |
2119 Here is another way to write the above loop: | |
2120 | |
2121 @example | |
2122 (do* ((xp foo (cdr xp)) | |
2123 (yp bar (cdr yp)) | |
2124 (x (car xp) (car xp)) | |
2125 (y (car yp) (car yp)) | |
2126 z) | |
2127 ((or (null xp) (null yp)) | |
2128 (nreverse z)) | |
2129 (push (f x y) z)) | |
2130 @end example | |
2131 @end defspec | |
2132 | |
27511
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2133 @defspec dolist (var list [result]) forms@dots{} |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2134 This is a more specialized loop which iterates across the elements |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2135 of a list. @var{list} should evaluate to a list; the body @var{forms} |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2136 are executed with @var{var} bound to each element of the list in |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2137 turn. Finally, the @var{result} form (or @code{nil}) is evaluated |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2138 with @var{var} bound to @code{nil} to produce the result returned by |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2139 the loop. Unlike with Emacs's built in @code{dolist}, the loop is |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2140 surrounded by an implicit @code{nil} block. |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2141 @end defspec |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2142 |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2143 @defspec dotimes (var count [result]) forms@dots{} |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2144 This is a more specialized loop which iterates a specified number |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2145 of times. The body is executed with @var{var} bound to the integers |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2146 from zero (inclusive) to @var{count} (exclusive), in turn. Then |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2147 the @code{result} form is evaluated with @var{var} bound to the total |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2148 number of iterations that were done (i.e., @code{(max 0 @var{count})}) |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2149 to get the return value for the loop form. Unlike with Emacs's built in |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2150 @code{dolist}, the loop is surrounded by an implicit @code{nil} block. |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2151 @end defspec |
ead47a92d9d0
Replace dotimes, dolist, with comment.
Dave Love <fx@gnu.org>
parents:
27487
diff
changeset
|
2152 |
25829 | 2153 @defspec do-symbols (var [obarray [result]]) forms@dots{} |
2154 This loop iterates over all interned symbols. If @var{obarray} | |
2155 is specified and is not @code{nil}, it loops over all symbols in | |
2156 that obarray. For each symbol, the body @var{forms} are evaluated | |
2157 with @var{var} bound to that symbol. The symbols are visited in | |
2158 an unspecified order. Afterward the @var{result} form, if any, | |
2159 is evaluated (with @var{var} bound to @code{nil}) to get the return | |
2160 value. The loop is surrounded by an implicit @code{nil} block. | |
2161 @end defspec | |
2162 | |
2163 @defspec do-all-symbols (var [result]) forms@dots{} | |
2164 This is identical to @code{do-symbols} except that the @var{obarray} | |
2165 argument is omitted; it always iterates over the default obarray. | |
2166 @end defspec | |
2167 | |
2168 @xref{Mapping over Sequences}, for some more functions for | |
2169 iterating over vectors or lists. | |
2170 | |
2171 @node Loop Facility, Multiple Values, Iteration, Control Structure | |
2172 @section Loop Facility | |
2173 | |
2174 @noindent | |
2175 A common complaint with Lisp's traditional looping constructs is | |
2176 that they are either too simple and limited, such as Common Lisp's | |
2177 @code{dotimes} or Emacs Lisp's @code{while}, or too unreadable and | |
2178 obscure, like Common Lisp's @code{do} loop. | |
2179 | |
2180 To remedy this, recent versions of Common Lisp have added a new | |
2181 construct called the ``Loop Facility'' or ``@code{loop} macro,'' | |
2182 with an easy-to-use but very powerful and expressive syntax. | |
2183 | |
2184 @menu | |
2185 * Loop Basics:: `loop' macro, basic clause structure | |
2186 * Loop Examples:: Working examples of `loop' macro | |
2187 * For Clauses:: Clauses introduced by `for' or `as' | |
2188 * Iteration Clauses:: `repeat', `while', `thereis', etc. | |
2189 * Accumulation Clauses:: `collect', `sum', `maximize', etc. | |
2190 * Other Clauses:: `with', `if', `initially', `finally' | |
2191 @end menu | |
2192 | |
2193 @node Loop Basics, Loop Examples, Loop Facility, Loop Facility | |
2194 @subsection Loop Basics | |
2195 | |
2196 @noindent | |
2197 The @code{loop} macro essentially creates a mini-language within | |
2198 Lisp that is specially tailored for describing loops. While this | |
2199 language is a little strange-looking by the standards of regular Lisp, | |
2200 it turns out to be very easy to learn and well-suited to its purpose. | |
2201 | |
2202 Since @code{loop} is a macro, all parsing of the loop language | |
2203 takes place at byte-compile time; compiled @code{loop}s are just | |
2204 as efficient as the equivalent @code{while} loops written longhand. | |
2205 | |
2206 @defspec loop clauses@dots{} | |
2207 A loop construct consists of a series of @var{clause}s, each | |
2208 introduced by a symbol like @code{for} or @code{do}. Clauses | |
2209 are simply strung together in the argument list of @code{loop}, | |
2210 with minimal extra parentheses. The various types of clauses | |
2211 specify initializations, such as the binding of temporary | |
2212 variables, actions to be taken in the loop, stepping actions, | |
2213 and final cleanup. | |
2214 | |
2215 Common Lisp specifies a certain general order of clauses in a | |
2216 loop: | |
2217 | |
2218 @example | |
2219 (loop @var{name-clause} | |
2220 @var{var-clauses}@dots{} | |
2221 @var{action-clauses}@dots{}) | |
2222 @end example | |
2223 | |
2224 The @var{name-clause} optionally gives a name to the implicit | |
2225 block that surrounds the loop. By default, the implicit block | |
2226 is named @code{nil}. The @var{var-clauses} specify what | |
2227 variables should be bound during the loop, and how they should | |
2228 be modified or iterated throughout the course of the loop. The | |
2229 @var{action-clauses} are things to be done during the loop, such | |
2230 as computing, collecting, and returning values. | |
2231 | |
2232 The Emacs version of the @code{loop} macro is less restrictive about | |
2233 the order of clauses, but things will behave most predictably if | |
2234 you put the variable-binding clauses @code{with}, @code{for}, and | |
2235 @code{repeat} before the action clauses. As in Common Lisp, | |
2236 @code{initially} and @code{finally} clauses can go anywhere. | |
2237 | |
2238 Loops generally return @code{nil} by default, but you can cause | |
2239 them to return a value by using an accumulation clause like | |
2240 @code{collect}, an end-test clause like @code{always}, or an | |
2241 explicit @code{return} clause to jump out of the implicit block. | |
2242 (Because the loop body is enclosed in an implicit block, you can | |
2243 also use regular Lisp @code{return} or @code{return-from} to | |
2244 break out of the loop.) | |
2245 @end defspec | |
2246 | |
2247 The following sections give some examples of the Loop Macro in | |
2248 action, and describe the particular loop clauses in great detail. | |
2249 Consult the second edition of Steele's @dfn{Common Lisp, the Language}, | |
2250 for additional discussion and examples of the @code{loop} macro. | |
2251 | |
2252 @node Loop Examples, For Clauses, Loop Basics, Loop Facility | |
2253 @subsection Loop Examples | |
2254 | |
2255 @noindent | |
2256 Before listing the full set of clauses that are allowed, let's | |
2257 look at a few example loops just to get a feel for the @code{loop} | |
2258 language. | |
2259 | |
2260 @example | |
2261 (loop for buf in (buffer-list) | |
2262 collect (buffer-file-name buf)) | |
2263 @end example | |
2264 | |
2265 @noindent | |
2266 This loop iterates over all Emacs buffers, using the list | |
2267 returned by @code{buffer-list}. For each buffer @code{buf}, | |
2268 it calls @code{buffer-file-name} and collects the results into | |
2269 a list, which is then returned from the @code{loop} construct. | |
2270 The result is a list of the file names of all the buffers in | |
2271 Emacs' memory. The words @code{for}, @code{in}, and @code{collect} | |
2272 are reserved words in the @code{loop} language. | |
2273 | |
2274 @example | |
2275 (loop repeat 20 do (insert "Yowsa\n")) | |
2276 @end example | |
2277 | |
2278 @noindent | |
2279 This loop inserts the phrase ``Yowsa'' twenty times in the | |
2280 current buffer. | |
2281 | |
2282 @example | |
2283 (loop until (eobp) do (munch-line) (forward-line 1)) | |
2284 @end example | |
2285 | |
2286 @noindent | |
2287 This loop calls @code{munch-line} on every line until the end | |
2288 of the buffer. If point is already at the end of the buffer, | |
2289 the loop exits immediately. | |
2290 | |
2291 @example | |
2292 (loop do (munch-line) until (eobp) do (forward-line 1)) | |
2293 @end example | |
2294 | |
2295 @noindent | |
2296 This loop is similar to the above one, except that @code{munch-line} | |
2297 is always called at least once. | |
2298 | |
2299 @example | |
2300 (loop for x from 1 to 100 | |
2301 for y = (* x x) | |
2302 until (>= y 729) | |
2303 finally return (list x (= y 729))) | |
2304 @end example | |
2305 | |
2306 @noindent | |
2307 This more complicated loop searches for a number @code{x} whose | |
2308 square is 729. For safety's sake it only examines @code{x} | |
2309 values up to 100; dropping the phrase @samp{to 100} would | |
2310 cause the loop to count upwards with no limit. The second | |
2311 @code{for} clause defines @code{y} to be the square of @code{x} | |
2312 within the loop; the expression after the @code{=} sign is | |
2313 reevaluated each time through the loop. The @code{until} | |
2314 clause gives a condition for terminating the loop, and the | |
2315 @code{finally} clause says what to do when the loop finishes. | |
2316 (This particular example was written less concisely than it | |
2317 could have been, just for the sake of illustration.) | |
2318 | |
2319 Note that even though this loop contains three clauses (two | |
2320 @code{for}s and an @code{until}) that would have been enough to | |
2321 define loops all by themselves, it still creates a single loop | |
2322 rather than some sort of triple-nested loop. You must explicitly | |
2323 nest your @code{loop} constructs if you want nested loops. | |
2324 | |
2325 @node For Clauses, Iteration Clauses, Loop Examples, Loop Facility | |
2326 @subsection For Clauses | |
2327 | |
2328 @noindent | |
2329 Most loops are governed by one or more @code{for} clauses. | |
2330 A @code{for} clause simultaneously describes variables to be | |
2331 bound, how those variables are to be stepped during the loop, | |
2332 and usually an end condition based on those variables. | |
2333 | |
2334 The word @code{as} is a synonym for the word @code{for}. This | |
2335 word is followed by a variable name, then a word like @code{from} | |
2336 or @code{across} that describes the kind of iteration desired. | |
2337 In Common Lisp, the phrase @code{being the} sometimes precedes | |
2338 the type of iteration; in this package both @code{being} and | |
2339 @code{the} are optional. The word @code{each} is a synonym | |
2340 for @code{the}, and the word that follows it may be singular | |
2341 or plural: @samp{for x being the elements of y} or | |
2342 @samp{for x being each element of y}. Which form you use | |
2343 is purely a matter of style. | |
2344 | |
2345 The variable is bound around the loop as if by @code{let}: | |
2346 | |
2347 @example | |
2348 (setq i 'happy) | |
2349 (loop for i from 1 to 10 do (do-something-with i)) | |
2350 i | |
2351 @result{} happy | |
2352 @end example | |
2353 | |
2354 @table @code | |
2355 @item for @var{var} from @var{expr1} to @var{expr2} by @var{expr3} | |
2356 This type of @code{for} clause creates a counting loop. Each of | |
2357 the three sub-terms is optional, though there must be at least one | |
2358 term so that the clause is marked as a counting clause. | |
2359 | |
2360 The three expressions are the starting value, the ending value, and | |
2361 the step value, respectively, of the variable. The loop counts | |
2362 upwards by default (@var{expr3} must be positive), from @var{expr1} | |
2363 to @var{expr2} inclusively. If you omit the @code{from} term, the | |
2364 loop counts from zero; if you omit the @code{to} term, the loop | |
2365 counts forever without stopping (unless stopped by some other | |
2366 loop clause, of course); if you omit the @code{by} term, the loop | |
2367 counts in steps of one. | |
2368 | |
2369 You can replace the word @code{from} with @code{upfrom} or | |
2370 @code{downfrom} to indicate the direction of the loop. Likewise, | |
2371 you can replace @code{to} with @code{upto} or @code{downto}. | |
2372 For example, @samp{for x from 5 downto 1} executes five times | |
2373 with @code{x} taking on the integers from 5 down to 1 in turn. | |
2374 Also, you can replace @code{to} with @code{below} or @code{above}, | |
2375 which are like @code{upto} and @code{downto} respectively except | |
2376 that they are exclusive rather than inclusive limits: | |
2377 | |
2378 @example | |
2379 (loop for x to 10 collect x) | |
2380 @result{} (0 1 2 3 4 5 6 7 8 9 10) | |
2381 (loop for x below 10 collect x) | |
2382 @result{} (0 1 2 3 4 5 6 7 8 9) | |
2383 @end example | |
2384 | |
2385 The @code{by} value is always positive, even for downward-counting | |
2386 loops. Some sort of @code{from} value is required for downward | |
60927
bae786986f2e
* calc.texi, cl.texi, gnus.texi, idlwave.texi, reftex.texi: Replace
Werner LEMBERG <wl@gnu.org>
parents:
55833
diff
changeset
|
2387 loops; @samp{for x downto 5} is not a valid loop clause all by |
25829 | 2388 itself. |
2389 | |
2390 @item for @var{var} in @var{list} by @var{function} | |
2391 This clause iterates @var{var} over all the elements of @var{list}, | |
2392 in turn. If you specify the @code{by} term, then @var{function} | |
2393 is used to traverse the list instead of @code{cdr}; it must be a | |
2394 function taking one argument. For example: | |
2395 | |
2396 @example | |
2397 (loop for x in '(1 2 3 4 5 6) collect (* x x)) | |
2398 @result{} (1 4 9 16 25 36) | |
2399 (loop for x in '(1 2 3 4 5 6) by 'cddr collect (* x x)) | |
2400 @result{} (1 9 25) | |
2401 @end example | |
2402 | |
2403 @item for @var{var} on @var{list} by @var{function} | |
2404 This clause iterates @var{var} over all the cons cells of @var{list}. | |
2405 | |
2406 @example | |
2407 (loop for x on '(1 2 3 4) collect x) | |
2408 @result{} ((1 2 3 4) (2 3 4) (3 4) (4)) | |
2409 @end example | |
2410 | |
2411 With @code{by}, there is no real reason that the @code{on} expression | |
2412 must be a list. For example: | |
2413 | |
2414 @example | |
2415 (loop for x on first-animal by 'next-animal collect x) | |
2416 @end example | |
2417 | |
2418 @noindent | |
2419 where @code{(next-animal x)} takes an ``animal'' @var{x} and returns | |
2420 the next in the (assumed) sequence of animals, or @code{nil} if | |
2421 @var{x} was the last animal in the sequence. | |
2422 | |
2423 @item for @var{var} in-ref @var{list} by @var{function} | |
2424 This is like a regular @code{in} clause, but @var{var} becomes | |
2425 a @code{setf}-able ``reference'' onto the elements of the list | |
2426 rather than just a temporary variable. For example, | |
2427 | |
2428 @example | |
2429 (loop for x in-ref my-list do (incf x)) | |
2430 @end example | |
2431 | |
2432 @noindent | |
2433 increments every element of @code{my-list} in place. This clause | |
2434 is an extension to standard Common Lisp. | |
2435 | |
2436 @item for @var{var} across @var{array} | |
2437 This clause iterates @var{var} over all the elements of @var{array}, | |
2438 which may be a vector or a string. | |
2439 | |
2440 @example | |
2441 (loop for x across "aeiou" | |
2442 do (use-vowel (char-to-string x))) | |
2443 @end example | |
2444 | |
2445 @item for @var{var} across-ref @var{array} | |
2446 This clause iterates over an array, with @var{var} a @code{setf}-able | |
2447 reference onto the elements; see @code{in-ref} above. | |
2448 | |
2449 @item for @var{var} being the elements of @var{sequence} | |
2450 This clause iterates over the elements of @var{sequence}, which may | |
2451 be a list, vector, or string. Since the type must be determined | |
2452 at run-time, this is somewhat less efficient than @code{in} or | |
2453 @code{across}. The clause may be followed by the additional term | |
2454 @samp{using (index @var{var2})} to cause @var{var2} to be bound to | |
2455 the successive indices (starting at 0) of the elements. | |
2456 | |
2457 This clause type is taken from older versions of the @code{loop} macro, | |
2458 and is not present in modern Common Lisp. The @samp{using (sequence ...)} | |
2459 term of the older macros is not supported. | |
2460 | |
2461 @item for @var{var} being the elements of-ref @var{sequence} | |
2462 This clause iterates over a sequence, with @var{var} a @code{setf}-able | |
2463 reference onto the elements; see @code{in-ref} above. | |
2464 | |
2465 @item for @var{var} being the symbols [of @var{obarray}] | |
2466 This clause iterates over symbols, either over all interned symbols | |
2467 or over all symbols in @var{obarray}. The loop is executed with | |
2468 @var{var} bound to each symbol in turn. The symbols are visited in | |
2469 an unspecified order. | |
2470 | |
2471 As an example, | |
2472 | |
2473 @example | |
2474 (loop for sym being the symbols | |
2475 when (fboundp sym) | |
2476 when (string-match "^map" (symbol-name sym)) | |
2477 collect sym) | |
2478 @end example | |
2479 | |
2480 @noindent | |
2481 returns a list of all the functions whose names begin with @samp{map}. | |
2482 | |
2483 The Common Lisp words @code{external-symbols} and @code{present-symbols} | |
2484 are also recognized but are equivalent to @code{symbols} in Emacs Lisp. | |
2485 | |
2486 Due to a minor implementation restriction, it will not work to have | |
2487 more than one @code{for} clause iterating over symbols, hash tables, | |
2488 keymaps, overlays, or intervals in a given @code{loop}. Fortunately, | |
60927
bae786986f2e
* calc.texi, cl.texi, gnus.texi, idlwave.texi, reftex.texi: Replace
Werner LEMBERG <wl@gnu.org>
parents:
55833
diff
changeset
|
2489 it would rarely if ever be useful to do so. It @emph{is} valid to mix |
25829 | 2490 one of these types of clauses with other clauses like @code{for ... to} |
2491 or @code{while}. | |
2492 | |
2493 @item for @var{var} being the hash-keys of @var{hash-table} | |
2494 This clause iterates over the entries in @var{hash-table}. For each | |
2495 hash table entry, @var{var} is bound to the entry's key. If you write | |
2496 @samp{the hash-values} instead, @var{var} is bound to the values | |
2497 of the entries. The clause may be followed by the additional | |
2498 term @samp{using (hash-values @var{var2})} (where @code{hash-values} | |
2499 is the opposite word of the word following @code{the}) to cause | |
2500 @var{var} and @var{var2} to be bound to the two parts of each | |
2501 hash table entry. | |
2502 | |
2503 @item for @var{var} being the key-codes of @var{keymap} | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
2504 This clause iterates over the entries in @var{keymap}. |
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
2505 The iteration does not enter nested keymaps or inherited (parent) keymaps. |
25829 | 2506 You can use @samp{the key-bindings} to access the commands bound to |
2507 the keys rather than the key codes, and you can add a @code{using} | |
2508 clause to access both the codes and the bindings together. | |
2509 | |
2510 @item for @var{var} being the key-seqs of @var{keymap} | |
2511 This clause iterates over all key sequences defined by @var{keymap} | |
2512 and its nested keymaps, where @var{var} takes on values which are | |
27225
ee242fddb1ab
Remove various old stuff and references thereto.
Dave Love <fx@gnu.org>
parents:
25829
diff
changeset
|
2513 vectors. The strings or vectors |
25829 | 2514 are reused for each iteration, so you must copy them if you wish to keep |
2515 them permanently. You can add a @samp{using (key-bindings ...)} | |
2516 clause to get the command bindings as well. | |
2517 | |
2518 @item for @var{var} being the overlays [of @var{buffer}] @dots{} | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
2519 This clause iterates over the ``overlays'' of a buffer |
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
2520 (the clause @code{extents} is synonymous |
27225
ee242fddb1ab
Remove various old stuff and references thereto.
Dave Love <fx@gnu.org>
parents:
25829
diff
changeset
|
2521 with @code{overlays}). If the @code{of} term is omitted, the current |
ee242fddb1ab
Remove various old stuff and references thereto.
Dave Love <fx@gnu.org>
parents:
25829
diff
changeset
|
2522 buffer is used. |
25829 | 2523 This clause also accepts optional @samp{from @var{pos}} and |
2524 @samp{to @var{pos}} terms, limiting the clause to overlays which | |
2525 overlap the specified region. | |
2526 | |
2527 @item for @var{var} being the intervals [of @var{buffer}] @dots{} | |
2528 This clause iterates over all intervals of a buffer with constant | |
2529 text properties. The variable @var{var} will be bound to conses | |
2530 of start and end positions, where one start position is always equal | |
2531 to the previous end position. The clause allows @code{of}, | |
2532 @code{from}, @code{to}, and @code{property} terms, where the latter | |
2533 term restricts the search to just the specified property. The | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
2534 @code{of} term may specify either a buffer or a string. |
25829 | 2535 |
2536 @item for @var{var} being the frames | |
2537 This clause iterates over all frames, i.e., X window system windows | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
2538 open on Emacs files. The |
25829 | 2539 clause @code{screens} is a synonym for @code{frames}. The frames |
2540 are visited in @code{next-frame} order starting from | |
2541 @code{selected-frame}. | |
2542 | |
2543 @item for @var{var} being the windows [of @var{frame}] | |
2544 This clause iterates over the windows (in the Emacs sense) of | |
27225
ee242fddb1ab
Remove various old stuff and references thereto.
Dave Love <fx@gnu.org>
parents:
25829
diff
changeset
|
2545 the current frame, or of the specified @var{frame}. |
25829 | 2546 |
2547 @item for @var{var} being the buffers | |
2548 This clause iterates over all buffers in Emacs. It is equivalent | |
2549 to @samp{for @var{var} in (buffer-list)}. | |
2550 | |
2551 @item for @var{var} = @var{expr1} then @var{expr2} | |
2552 This clause does a general iteration. The first time through | |
2553 the loop, @var{var} will be bound to @var{expr1}. On the second | |
2554 and successive iterations it will be set by evaluating @var{expr2} | |
2555 (which may refer to the old value of @var{var}). For example, | |
2556 these two loops are effectively the same: | |
2557 | |
2558 @example | |
2559 (loop for x on my-list by 'cddr do ...) | |
2560 (loop for x = my-list then (cddr x) while x do ...) | |
2561 @end example | |
2562 | |
2563 Note that this type of @code{for} clause does not imply any sort | |
2564 of terminating condition; the above example combines it with a | |
2565 @code{while} clause to tell when to end the loop. | |
2566 | |
2567 If you omit the @code{then} term, @var{expr1} is used both for | |
2568 the initial setting and for successive settings: | |
2569 | |
2570 @example | |
2571 (loop for x = (random) when (> x 0) return x) | |
2572 @end example | |
2573 | |
2574 @noindent | |
2575 This loop keeps taking random numbers from the @code{(random)} | |
2576 function until it gets a positive one, which it then returns. | |
2577 @end table | |
2578 | |
2579 If you include several @code{for} clauses in a row, they are | |
2580 treated sequentially (as if by @code{let*} and @code{setq}). | |
2581 You can instead use the word @code{and} to link the clauses, | |
2582 in which case they are processed in parallel (as if by @code{let} | |
2583 and @code{psetq}). | |
2584 | |
2585 @example | |
2586 (loop for x below 5 for y = nil then x collect (list x y)) | |
2587 @result{} ((0 nil) (1 1) (2 2) (3 3) (4 4)) | |
2588 (loop for x below 5 and y = nil then x collect (list x y)) | |
2589 @result{} ((0 nil) (1 0) (2 1) (3 2) (4 3)) | |
2590 @end example | |
2591 | |
2592 @noindent | |
2593 In the first loop, @code{y} is set based on the value of @code{x} | |
2594 that was just set by the previous clause; in the second loop, | |
2595 @code{x} and @code{y} are set simultaneously so @code{y} is set | |
2596 based on the value of @code{x} left over from the previous time | |
2597 through the loop. | |
2598 | |
2599 Another feature of the @code{loop} macro is @dfn{destructuring}, | |
2600 similar in concept to the destructuring provided by @code{defmacro}. | |
2601 The @var{var} part of any @code{for} clause can be given as a list | |
2602 of variables instead of a single variable. The values produced | |
2603 during loop execution must be lists; the values in the lists are | |
2604 stored in the corresponding variables. | |
2605 | |
2606 @example | |
2607 (loop for (x y) in '((2 3) (4 5) (6 7)) collect (+ x y)) | |
2608 @result{} (5 9 13) | |
2609 @end example | |
2610 | |
2611 In loop destructuring, if there are more values than variables | |
2612 the trailing values are ignored, and if there are more variables | |
2613 than values the trailing variables get the value @code{nil}. | |
2614 If @code{nil} is used as a variable name, the corresponding | |
2615 values are ignored. Destructuring may be nested, and dotted | |
2616 lists of variables like @code{(x . y)} are allowed. | |
2617 | |
2618 @node Iteration Clauses, Accumulation Clauses, For Clauses, Loop Facility | |
2619 @subsection Iteration Clauses | |
2620 | |
2621 @noindent | |
2622 Aside from @code{for} clauses, there are several other loop clauses | |
2623 that control the way the loop operates. They might be used by | |
2624 themselves, or in conjunction with one or more @code{for} clauses. | |
2625 | |
2626 @table @code | |
2627 @item repeat @var{integer} | |
2628 This clause simply counts up to the specified number using an | |
2629 internal temporary variable. The loops | |
2630 | |
2631 @example | |
2632 (loop repeat n do ...) | |
2633 (loop for temp to n do ...) | |
2634 @end example | |
2635 | |
2636 @noindent | |
2637 are identical except that the second one forces you to choose | |
2638 a name for a variable you aren't actually going to use. | |
2639 | |
2640 @item while @var{condition} | |
2641 This clause stops the loop when the specified condition (any Lisp | |
2642 expression) becomes @code{nil}. For example, the following two | |
2643 loops are equivalent, except for the implicit @code{nil} block | |
2644 that surrounds the second one: | |
2645 | |
2646 @example | |
2647 (while @var{cond} @var{forms}@dots{}) | |
2648 (loop while @var{cond} do @var{forms}@dots{}) | |
2649 @end example | |
2650 | |
2651 @item until @var{condition} | |
2652 This clause stops the loop when the specified condition is true, | |
2653 i.e., non-@code{nil}. | |
2654 | |
2655 @item always @var{condition} | |
2656 This clause stops the loop when the specified condition is @code{nil}. | |
2657 Unlike @code{while}, it stops the loop using @code{return nil} so that | |
2658 the @code{finally} clauses are not executed. If all the conditions | |
2659 were non-@code{nil}, the loop returns @code{t}: | |
2660 | |
2661 @example | |
2662 (if (loop for size in size-list always (> size 10)) | |
2663 (some-big-sizes) | |
2664 (no-big-sizes)) | |
2665 @end example | |
2666 | |
2667 @item never @var{condition} | |
2668 This clause is like @code{always}, except that the loop returns | |
2669 @code{t} if any conditions were false, or @code{nil} otherwise. | |
2670 | |
2671 @item thereis @var{condition} | |
2672 This clause stops the loop when the specified form is non-@code{nil}; | |
2673 in this case, it returns that non-@code{nil} value. If all the | |
2674 values were @code{nil}, the loop returns @code{nil}. | |
2675 @end table | |
2676 | |
2677 @node Accumulation Clauses, Other Clauses, Iteration Clauses, Loop Facility | |
2678 @subsection Accumulation Clauses | |
2679 | |
2680 @noindent | |
2681 These clauses cause the loop to accumulate information about the | |
2682 specified Lisp @var{form}. The accumulated result is returned | |
2683 from the loop unless overridden, say, by a @code{return} clause. | |
2684 | |
2685 @table @code | |
2686 @item collect @var{form} | |
2687 This clause collects the values of @var{form} into a list. Several | |
2688 examples of @code{collect} appear elsewhere in this manual. | |
2689 | |
2690 The word @code{collecting} is a synonym for @code{collect}, and | |
2691 likewise for the other accumulation clauses. | |
2692 | |
2693 @item append @var{form} | |
2694 This clause collects lists of values into a result list using | |
2695 @code{append}. | |
2696 | |
2697 @item nconc @var{form} | |
2698 This clause collects lists of values into a result list by | |
2699 destructively modifying the lists rather than copying them. | |
2700 | |
2701 @item concat @var{form} | |
2702 This clause concatenates the values of the specified @var{form} | |
2703 into a string. (It and the following clause are extensions to | |
2704 standard Common Lisp.) | |
2705 | |
2706 @item vconcat @var{form} | |
2707 This clause concatenates the values of the specified @var{form} | |
2708 into a vector. | |
2709 | |
2710 @item count @var{form} | |
2711 This clause counts the number of times the specified @var{form} | |
2712 evaluates to a non-@code{nil} value. | |
2713 | |
2714 @item sum @var{form} | |
2715 This clause accumulates the sum of the values of the specified | |
2716 @var{form}, which must evaluate to a number. | |
2717 | |
2718 @item maximize @var{form} | |
2719 This clause accumulates the maximum value of the specified @var{form}, | |
2720 which must evaluate to a number. The return value is undefined if | |
2721 @code{maximize} is executed zero times. | |
2722 | |
2723 @item minimize @var{form} | |
2724 This clause accumulates the minimum value of the specified @var{form}. | |
2725 @end table | |
2726 | |
2727 Accumulation clauses can be followed by @samp{into @var{var}} to | |
2728 cause the data to be collected into variable @var{var} (which is | |
2729 automatically @code{let}-bound during the loop) rather than an | |
2730 unnamed temporary variable. Also, @code{into} accumulations do | |
2731 not automatically imply a return value. The loop must use some | |
2732 explicit mechanism, such as @code{finally return}, to return | |
2733 the accumulated result. | |
2734 | |
60927
bae786986f2e
* calc.texi, cl.texi, gnus.texi, idlwave.texi, reftex.texi: Replace
Werner LEMBERG <wl@gnu.org>
parents:
55833
diff
changeset
|
2735 It is valid for several accumulation clauses of the same type to |
25829 | 2736 accumulate into the same place. From Steele: |
2737 | |
2738 @example | |
2739 (loop for name in '(fred sue alice joe june) | |
2740 for kids in '((bob ken) () () (kris sunshine) ()) | |
2741 collect name | |
2742 append kids) | |
2743 @result{} (fred bob ken sue alice joe kris sunshine june) | |
2744 @end example | |
2745 | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
2746 @node Other Clauses, , Accumulation Clauses, Loop Facility |
25829 | 2747 @subsection Other Clauses |
2748 | |
2749 @noindent | |
2750 This section describes the remaining loop clauses. | |
2751 | |
2752 @table @code | |
2753 @item with @var{var} = @var{value} | |
2754 This clause binds a variable to a value around the loop, but | |
2755 otherwise leaves the variable alone during the loop. The following | |
2756 loops are basically equivalent: | |
2757 | |
2758 @example | |
2759 (loop with x = 17 do ...) | |
2760 (let ((x 17)) (loop do ...)) | |
2761 (loop for x = 17 then x do ...) | |
2762 @end example | |
2763 | |
2764 Naturally, the variable @var{var} might be used for some purpose | |
2765 in the rest of the loop. For example: | |
2766 | |
2767 @example | |
2768 (loop for x in my-list with res = nil do (push x res) | |
2769 finally return res) | |
2770 @end example | |
2771 | |
2772 This loop inserts the elements of @code{my-list} at the front of | |
2773 a new list being accumulated in @code{res}, then returns the | |
2774 list @code{res} at the end of the loop. The effect is similar | |
2775 to that of a @code{collect} clause, but the list gets reversed | |
2776 by virtue of the fact that elements are being pushed onto the | |
2777 front of @code{res} rather than the end. | |
2778 | |
2779 If you omit the @code{=} term, the variable is initialized to | |
2780 @code{nil}. (Thus the @samp{= nil} in the above example is | |
2781 unnecessary.) | |
2782 | |
2783 Bindings made by @code{with} are sequential by default, as if | |
2784 by @code{let*}. Just like @code{for} clauses, @code{with} clauses | |
2785 can be linked with @code{and} to cause the bindings to be made by | |
2786 @code{let} instead. | |
2787 | |
2788 @item if @var{condition} @var{clause} | |
2789 This clause executes the following loop clause only if the specified | |
2790 condition is true. The following @var{clause} should be an accumulation, | |
2791 @code{do}, @code{return}, @code{if}, or @code{unless} clause. | |
2792 Several clauses may be linked by separating them with @code{and}. | |
2793 These clauses may be followed by @code{else} and a clause or clauses | |
2794 to execute if the condition was false. The whole construct may | |
2795 optionally be followed by the word @code{end} (which may be used to | |
2796 disambiguate an @code{else} or @code{and} in a nested @code{if}). | |
2797 | |
2798 The actual non-@code{nil} value of the condition form is available | |
2799 by the name @code{it} in the ``then'' part. For example: | |
2800 | |
2801 @example | |
2802 (setq funny-numbers '(6 13 -1)) | |
2803 @result{} (6 13 -1) | |
2804 (loop for x below 10 | |
2805 if (oddp x) | |
2806 collect x into odds | |
2807 and if (memq x funny-numbers) return (cdr it) end | |
2808 else | |
2809 collect x into evens | |
2810 finally return (vector odds evens)) | |
2811 @result{} [(1 3 5 7 9) (0 2 4 6 8)] | |
2812 (setq funny-numbers '(6 7 13 -1)) | |
2813 @result{} (6 7 13 -1) | |
2814 (loop <@r{same thing again}>) | |
2815 @result{} (13 -1) | |
2816 @end example | |
2817 | |
2818 Note the use of @code{and} to put two clauses into the ``then'' | |
2819 part, one of which is itself an @code{if} clause. Note also that | |
2820 @code{end}, while normally optional, was necessary here to make | |
2821 it clear that the @code{else} refers to the outermost @code{if} | |
2822 clause. In the first case, the loop returns a vector of lists | |
2823 of the odd and even values of @var{x}. In the second case, the | |
2824 odd number 7 is one of the @code{funny-numbers} so the loop | |
2825 returns early; the actual returned value is based on the result | |
2826 of the @code{memq} call. | |
2827 | |
2828 @item when @var{condition} @var{clause} | |
2829 This clause is just a synonym for @code{if}. | |
2830 | |
2831 @item unless @var{condition} @var{clause} | |
2832 The @code{unless} clause is just like @code{if} except that the | |
2833 sense of the condition is reversed. | |
2834 | |
2835 @item named @var{name} | |
2836 This clause gives a name other than @code{nil} to the implicit | |
2837 block surrounding the loop. The @var{name} is the symbol to be | |
2838 used as the block name. | |
2839 | |
2840 @item initially [do] @var{forms}... | |
2841 This keyword introduces one or more Lisp forms which will be | |
2842 executed before the loop itself begins (but after any variables | |
2843 requested by @code{for} or @code{with} have been bound to their | |
2844 initial values). @code{initially} clauses can appear anywhere; | |
2845 if there are several, they are executed in the order they appear | |
2846 in the loop. The keyword @code{do} is optional. | |
2847 | |
2848 @item finally [do] @var{forms}... | |
2849 This introduces Lisp forms which will be executed after the loop | |
2850 finishes (say, on request of a @code{for} or @code{while}). | |
2851 @code{initially} and @code{finally} clauses may appear anywhere | |
2852 in the loop construct, but they are executed (in the specified | |
2853 order) at the beginning or end, respectively, of the loop. | |
2854 | |
2855 @item finally return @var{form} | |
2856 This says that @var{form} should be executed after the loop | |
2857 is done to obtain a return value. (Without this, or some other | |
2858 clause like @code{collect} or @code{return}, the loop will simply | |
2859 return @code{nil}.) Variables bound by @code{for}, @code{with}, | |
2860 or @code{into} will still contain their final values when @var{form} | |
2861 is executed. | |
2862 | |
2863 @item do @var{forms}... | |
2864 The word @code{do} may be followed by any number of Lisp expressions | |
2865 which are executed as an implicit @code{progn} in the body of the | |
2866 loop. Many of the examples in this section illustrate the use of | |
2867 @code{do}. | |
2868 | |
2869 @item return @var{form} | |
2870 This clause causes the loop to return immediately. The following | |
2871 Lisp form is evaluated to give the return value of the @code{loop} | |
2872 form. The @code{finally} clauses, if any, are not executed. | |
2873 Of course, @code{return} is generally used inside an @code{if} or | |
2874 @code{unless}, as its use in a top-level loop clause would mean | |
2875 the loop would never get to ``loop'' more than once. | |
2876 | |
2877 The clause @samp{return @var{form}} is equivalent to | |
2878 @samp{do (return @var{form})} (or @code{return-from} if the loop | |
2879 was named). The @code{return} clause is implemented a bit more | |
2880 efficiently, though. | |
2881 @end table | |
2882 | |
2883 While there is no high-level way to add user extensions to @code{loop} | |
2884 (comparable to @code{defsetf} for @code{setf}, say), this package | |
2885 does offer two properties called @code{cl-loop-handler} and | |
2886 @code{cl-loop-for-handler} which are functions to be called when | |
2887 a given symbol is encountered as a top-level loop clause or | |
2888 @code{for} clause, respectively. Consult the source code in | |
2889 file @file{cl-macs.el} for details. | |
2890 | |
2891 This package's @code{loop} macro is compatible with that of Common | |
2892 Lisp, except that a few features are not implemented: @code{loop-finish} | |
2893 and data-type specifiers. Naturally, the @code{for} clauses which | |
2894 iterate over keymaps, overlays, intervals, frames, windows, and | |
2895 buffers are Emacs-specific extensions. | |
2896 | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
2897 @node Multiple Values, , Loop Facility, Control Structure |
25829 | 2898 @section Multiple Values |
2899 | |
2900 @noindent | |
2901 Common Lisp functions can return zero or more results. Emacs Lisp | |
2902 functions, by contrast, always return exactly one result. This | |
2903 package makes no attempt to emulate Common Lisp multiple return | |
2904 values; Emacs versions of Common Lisp functions that return more | |
2905 than one value either return just the first value (as in | |
2906 @code{compiler-macroexpand}) or return a list of values (as in | |
2907 @code{get-setf-method}). This package @emph{does} define placeholders | |
2908 for the Common Lisp functions that work with multiple values, but | |
2909 in Emacs Lisp these functions simply operate on lists instead. | |
2910 The @code{values} form, for example, is a synonym for @code{list} | |
2911 in Emacs. | |
2912 | |
2913 @defspec multiple-value-bind (var@dots{}) values-form forms@dots{} | |
2914 This form evaluates @var{values-form}, which must return a list of | |
2915 values. It then binds the @var{var}s to these respective values, | |
2916 as if by @code{let}, and then executes the body @var{forms}. | |
2917 If there are more @var{var}s than values, the extra @var{var}s | |
2918 are bound to @code{nil}. If there are fewer @var{var}s than | |
2919 values, the excess values are ignored. | |
2920 @end defspec | |
2921 | |
2922 @defspec multiple-value-setq (var@dots{}) form | |
2923 This form evaluates @var{form}, which must return a list of values. | |
2924 It then sets the @var{var}s to these respective values, as if by | |
2925 @code{setq}. Extra @var{var}s or values are treated the same as | |
2926 in @code{multiple-value-bind}. | |
2927 @end defspec | |
2928 | |
2929 The older Quiroz package attempted a more faithful (but still | |
2930 imperfect) emulation of Common Lisp multiple values. The old | |
2931 method ``usually'' simulated true multiple values quite well, | |
2932 but under certain circumstances would leave spurious return | |
2933 values in memory where a later, unrelated @code{multiple-value-bind} | |
2934 form would see them. | |
2935 | |
2936 Since a perfect emulation is not feasible in Emacs Lisp, this | |
2937 package opts to keep it as simple and predictable as possible. | |
2938 | |
2939 @node Macros, Declarations, Control Structure, Top | |
2940 @chapter Macros | |
2941 | |
2942 @noindent | |
2943 This package implements the various Common Lisp features of | |
2944 @code{defmacro}, such as destructuring, @code{&environment}, | |
2945 and @code{&body}. Top-level @code{&whole} is not implemented | |
2946 for @code{defmacro} due to technical difficulties. | |
2947 @xref{Argument Lists}. | |
2948 | |
2949 Destructuring is made available to the user by way of the | |
2950 following macro: | |
2951 | |
2952 @defspec destructuring-bind arglist expr forms@dots{} | |
2953 This macro expands to code which executes @var{forms}, with | |
2954 the variables in @var{arglist} bound to the list of values | |
2955 returned by @var{expr}. The @var{arglist} can include all | |
2956 the features allowed for @code{defmacro} argument lists, | |
2957 including destructuring. (The @code{&environment} keyword | |
2958 is not allowed.) The macro expansion will signal an error | |
2959 if @var{expr} returns a list of the wrong number of arguments | |
2960 or with incorrect keyword arguments. | |
2961 @end defspec | |
2962 | |
2963 This package also includes the Common Lisp @code{define-compiler-macro} | |
2964 facility, which allows you to define compile-time expansions and | |
2965 optimizations for your functions. | |
2966 | |
2967 @defspec define-compiler-macro name arglist forms@dots{} | |
2968 This form is similar to @code{defmacro}, except that it only expands | |
2969 calls to @var{name} at compile-time; calls processed by the Lisp | |
2970 interpreter are not expanded, nor are they expanded by the | |
2971 @code{macroexpand} function. | |
2972 | |
2973 The argument list may begin with a @code{&whole} keyword and a | |
2974 variable. This variable is bound to the macro-call form itself, | |
2975 i.e., to a list of the form @samp{(@var{name} @var{args}@dots{})}. | |
2976 If the macro expander returns this form unchanged, then the | |
2977 compiler treats it as a normal function call. This allows | |
2978 compiler macros to work as optimizers for special cases of a | |
2979 function, leaving complicated cases alone. | |
2980 | |
2981 For example, here is a simplified version of a definition that | |
2982 appears as a standard part of this package: | |
2983 | |
2984 @example | |
2985 (define-compiler-macro member* (&whole form a list &rest keys) | |
2986 (if (and (null keys) | |
2987 (eq (car-safe a) 'quote) | |
2988 (not (floatp-safe (cadr a)))) | |
2989 (list 'memq a list) | |
2990 form)) | |
2991 @end example | |
2992 | |
2993 @noindent | |
2994 This definition causes @code{(member* @var{a} @var{list})} to change | |
2995 to a call to the faster @code{memq} in the common case where @var{a} | |
2996 is a non-floating-point constant; if @var{a} is anything else, or | |
2997 if there are any keyword arguments in the call, then the original | |
2998 @code{member*} call is left intact. (The actual compiler macro | |
2999 for @code{member*} optimizes a number of other cases, including | |
3000 common @code{:test} predicates.) | |
3001 @end defspec | |
3002 | |
3003 @defun compiler-macroexpand form | |
3004 This function is analogous to @code{macroexpand}, except that it | |
3005 expands compiler macros rather than regular macros. It returns | |
3006 @var{form} unchanged if it is not a call to a function for which | |
3007 a compiler macro has been defined, or if that compiler macro | |
3008 decided to punt by returning its @code{&whole} argument. Like | |
3009 @code{macroexpand}, it expands repeatedly until it reaches a form | |
3010 for which no further expansion is possible. | |
3011 @end defun | |
3012 | |
3013 @xref{Macro Bindings}, for descriptions of the @code{macrolet} | |
3014 and @code{symbol-macrolet} forms for making ``local'' macro | |
3015 definitions. | |
3016 | |
3017 @node Declarations, Symbols, Macros, Top | |
3018 @chapter Declarations | |
3019 | |
3020 @noindent | |
3021 Common Lisp includes a complex and powerful ``declaration'' | |
3022 mechanism that allows you to give the compiler special hints | |
3023 about the types of data that will be stored in particular variables, | |
3024 and about the ways those variables and functions will be used. This | |
3025 package defines versions of all the Common Lisp declaration forms: | |
3026 @code{declare}, @code{locally}, @code{proclaim}, @code{declaim}, | |
3027 and @code{the}. | |
3028 | |
3029 Most of the Common Lisp declarations are not currently useful in | |
3030 Emacs Lisp, as the byte-code system provides little opportunity | |
3031 to benefit from type information, and @code{special} declarations | |
3032 are redundant in a fully dynamically-scoped Lisp. A few | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
3033 declarations are meaningful when the optimizing byte |
25829 | 3034 compiler is being used, however. Under the earlier non-optimizing |
3035 compiler, these declarations will effectively be ignored. | |
3036 | |
3037 @defun proclaim decl-spec | |
3038 This function records a ``global'' declaration specified by | |
3039 @var{decl-spec}. Since @code{proclaim} is a function, @var{decl-spec} | |
3040 is evaluated and thus should normally be quoted. | |
3041 @end defun | |
3042 | |
3043 @defspec declaim decl-specs@dots{} | |
3044 This macro is like @code{proclaim}, except that it takes any number | |
3045 of @var{decl-spec} arguments, and the arguments are unevaluated and | |
3046 unquoted. The @code{declaim} macro also puts an @code{(eval-when | |
3047 (compile load eval) ...)} around the declarations so that they will | |
3048 be registered at compile-time as well as at run-time. (This is vital, | |
3049 since normally the declarations are meant to influence the way the | |
3050 compiler treats the rest of the file that contains the @code{declaim} | |
3051 form.) | |
3052 @end defspec | |
3053 | |
3054 @defspec declare decl-specs@dots{} | |
3055 This macro is used to make declarations within functions and other | |
3056 code. Common Lisp allows declarations in various locations, generally | |
3057 at the beginning of any of the many ``implicit @code{progn}s'' | |
3058 throughout Lisp syntax, such as function bodies, @code{let} bodies, | |
3059 etc. Currently the only declaration understood by @code{declare} | |
3060 is @code{special}. | |
3061 @end defspec | |
3062 | |
3063 @defspec locally declarations@dots{} forms@dots{} | |
3064 In this package, @code{locally} is no different from @code{progn}. | |
3065 @end defspec | |
3066 | |
3067 @defspec the type form | |
3068 Type information provided by @code{the} is ignored in this package; | |
3069 in other words, @code{(the @var{type} @var{form})} is equivalent | |
3070 to @var{form}. Future versions of the optimizing byte-compiler may | |
3071 make use of this information. | |
3072 | |
3073 For example, @code{mapcar} can map over both lists and arrays. It is | |
3074 hard for the compiler to expand @code{mapcar} into an in-line loop | |
3075 unless it knows whether the sequence will be a list or an array ahead | |
3076 of time. With @code{(mapcar 'car (the vector foo))}, a future | |
3077 compiler would have enough information to expand the loop in-line. | |
3078 For now, Emacs Lisp will treat the above code as exactly equivalent | |
3079 to @code{(mapcar 'car foo)}. | |
3080 @end defspec | |
3081 | |
3082 Each @var{decl-spec} in a @code{proclaim}, @code{declaim}, or | |
3083 @code{declare} should be a list beginning with a symbol that says | |
3084 what kind of declaration it is. This package currently understands | |
3085 @code{special}, @code{inline}, @code{notinline}, @code{optimize}, | |
3086 and @code{warn} declarations. (The @code{warn} declaration is an | |
3087 extension of standard Common Lisp.) Other Common Lisp declarations, | |
3088 such as @code{type} and @code{ftype}, are silently ignored. | |
3089 | |
3090 @table @code | |
3091 @item special | |
3092 Since all variables in Emacs Lisp are ``special'' (in the Common | |
3093 Lisp sense), @code{special} declarations are only advisory. They | |
3094 simply tell the optimizing byte compiler that the specified | |
3095 variables are intentionally being referred to without being | |
3096 bound in the body of the function. The compiler normally emits | |
3097 warnings for such references, since they could be typographical | |
3098 errors for references to local variables. | |
3099 | |
3100 The declaration @code{(declare (special @var{var1} @var{var2}))} is | |
3101 equivalent to @code{(defvar @var{var1}) (defvar @var{var2})} in the | |
3102 optimizing compiler, or to nothing at all in older compilers (which | |
3103 do not warn for non-local references). | |
3104 | |
3105 In top-level contexts, it is generally better to write | |
3106 @code{(defvar @var{var})} than @code{(declaim (special @var{var}))}, | |
3107 since @code{defvar} makes your intentions clearer. But the older | |
3108 byte compilers can not handle @code{defvar}s appearing inside of | |
3109 functions, while @code{(declare (special @var{var}))} takes care | |
3110 to work correctly with all compilers. | |
3111 | |
3112 @item inline | |
3113 The @code{inline} @var{decl-spec} lists one or more functions | |
3114 whose bodies should be expanded ``in-line'' into calling functions | |
3115 whenever the compiler is able to arrange for it. For example, | |
3116 the Common Lisp function @code{cadr} is declared @code{inline} | |
3117 by this package so that the form @code{(cadr @var{x})} will | |
3118 expand directly into @code{(car (cdr @var{x}))} when it is called | |
3119 in user functions, for a savings of one (relatively expensive) | |
3120 function call. | |
3121 | |
3122 The following declarations are all equivalent. Note that the | |
3123 @code{defsubst} form is a convenient way to define a function | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
3124 and declare it inline all at once. |
25829 | 3125 |
3126 @example | |
3127 (declaim (inline foo bar)) | |
3128 (eval-when (compile load eval) (proclaim '(inline foo bar))) | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
3129 (defsubst foo (...) ...) ; instead of defun |
25829 | 3130 @end example |
3131 | |
52704 | 3132 @strong{Please note:} this declaration remains in effect after the |
25829 | 3133 containing source file is done. It is correct to use it to |
3134 request that a function you have defined should be inlined, | |
3135 but it is impolite to use it to request inlining of an external | |
3136 function. | |
3137 | |
3138 In Common Lisp, it is possible to use @code{(declare (inline @dots{}))} | |
3139 before a particular call to a function to cause just that call to | |
3140 be inlined; the current byte compilers provide no way to implement | |
3141 this, so @code{(declare (inline @dots{}))} is currently ignored by | |
3142 this package. | |
3143 | |
3144 @item notinline | |
3145 The @code{notinline} declaration lists functions which should | |
3146 not be inlined after all; it cancels a previous @code{inline} | |
3147 declaration. | |
3148 | |
3149 @item optimize | |
3150 This declaration controls how much optimization is performed by | |
3151 the compiler. Naturally, it is ignored by the earlier non-optimizing | |
3152 compilers. | |
3153 | |
3154 The word @code{optimize} is followed by any number of lists like | |
3155 @code{(speed 3)} or @code{(safety 2)}. Common Lisp defines several | |
3156 optimization ``qualities''; this package ignores all but @code{speed} | |
3157 and @code{safety}. The value of a quality should be an integer from | |
3158 0 to 3, with 0 meaning ``unimportant'' and 3 meaning ``very important.'' | |
3159 The default level for both qualities is 1. | |
3160 | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
3161 In this package, with the optimizing compiler, the |
25829 | 3162 @code{speed} quality is tied to the @code{byte-compile-optimize} |
3163 flag, which is set to @code{nil} for @code{(speed 0)} and to | |
3164 @code{t} for higher settings; and the @code{safety} quality is | |
3165 tied to the @code{byte-compile-delete-errors} flag, which is | |
3166 set to @code{t} for @code{(safety 3)} and to @code{nil} for all | |
3167 lower settings. (The latter flag controls whether the compiler | |
3168 is allowed to optimize out code whose only side-effect could | |
3169 be to signal an error, e.g., rewriting @code{(progn foo bar)} to | |
3170 @code{bar} when it is not known whether @code{foo} will be bound | |
3171 at run-time.) | |
3172 | |
3173 Note that even compiling with @code{(safety 0)}, the Emacs | |
3174 byte-code system provides sufficient checking to prevent real | |
3175 harm from being done. For example, barring serious bugs in | |
3176 Emacs itself, Emacs will not crash with a segmentation fault | |
3177 just because of an error in a fully-optimized Lisp program. | |
3178 | |
3179 The @code{optimize} declaration is normally used in a top-level | |
3180 @code{proclaim} or @code{declaim} in a file; Common Lisp allows | |
3181 it to be used with @code{declare} to set the level of optimization | |
3182 locally for a given form, but this will not work correctly with the | |
3183 current version of the optimizing compiler. (The @code{declare} | |
3184 will set the new optimization level, but that level will not | |
3185 automatically be unset after the enclosing form is done.) | |
3186 | |
3187 @item warn | |
3188 This declaration controls what sorts of warnings are generated | |
3189 by the byte compiler. Again, only the optimizing compiler | |
3190 generates warnings. The word @code{warn} is followed by any | |
3191 number of ``warning qualities,'' similar in form to optimization | |
3192 qualities. The currently supported warning types are | |
3193 @code{redefine}, @code{callargs}, @code{unresolved}, and | |
3194 @code{free-vars}; in the current system, a value of 0 will | |
3195 disable these warnings and any higher value will enable them. | |
3196 See the documentation for the optimizing byte compiler for details. | |
3197 @end table | |
3198 | |
3199 @node Symbols, Numbers, Declarations, Top | |
3200 @chapter Symbols | |
3201 | |
3202 @noindent | |
3203 This package defines several symbol-related features that were | |
3204 missing from Emacs Lisp. | |
3205 | |
3206 @menu | |
3207 * Property Lists:: `get*', `remprop', `getf', `remf' | |
3208 * Creating Symbols:: `gensym', `gentemp' | |
3209 @end menu | |
3210 | |
3211 @node Property Lists, Creating Symbols, Symbols, Symbols | |
3212 @section Property Lists | |
3213 | |
3214 @noindent | |
3215 These functions augment the standard Emacs Lisp functions @code{get} | |
3216 and @code{put} for operating on properties attached to symbols. | |
3217 There are also functions for working with property lists as | |
3218 first-class data structures not attached to particular symbols. | |
3219 | |
3220 @defun get* symbol property &optional default | |
3221 This function is like @code{get}, except that if the property is | |
3222 not found, the @var{default} argument provides the return value. | |
3223 (The Emacs Lisp @code{get} function always uses @code{nil} as | |
3224 the default; this package's @code{get*} is equivalent to Common | |
3225 Lisp's @code{get}.) | |
3226 | |
3227 The @code{get*} function is @code{setf}-able; when used in this | |
3228 fashion, the @var{default} argument is allowed but ignored. | |
3229 @end defun | |
3230 | |
3231 @defun remprop symbol property | |
3232 This function removes the entry for @var{property} from the property | |
3233 list of @var{symbol}. It returns a true value if the property was | |
3234 indeed found and removed, or @code{nil} if there was no such property. | |
3235 (This function was probably omitted from Emacs originally because, | |
3236 since @code{get} did not allow a @var{default}, it was very difficult | |
3237 to distinguish between a missing property and a property whose value | |
3238 was @code{nil}; thus, setting a property to @code{nil} was close | |
3239 enough to @code{remprop} for most purposes.) | |
3240 @end defun | |
3241 | |
3242 @defun getf place property &optional default | |
3243 This function scans the list @var{place} as if it were a property | |
3244 list, i.e., a list of alternating property names and values. If | |
3245 an even-numbered element of @var{place} is found which is @code{eq} | |
3246 to @var{property}, the following odd-numbered element is returned. | |
3247 Otherwise, @var{default} is returned (or @code{nil} if no default | |
3248 is given). | |
3249 | |
3250 In particular, | |
3251 | |
3252 @example | |
3253 (get sym prop) @equiv{} (getf (symbol-plist sym) prop) | |
3254 @end example | |
3255 | |
60927
bae786986f2e
* calc.texi, cl.texi, gnus.texi, idlwave.texi, reftex.texi: Replace
Werner LEMBERG <wl@gnu.org>
parents:
55833
diff
changeset
|
3256 It is valid to use @code{getf} as a @code{setf} place, in which case |
bae786986f2e
* calc.texi, cl.texi, gnus.texi, idlwave.texi, reftex.texi: Replace
Werner LEMBERG <wl@gnu.org>
parents:
55833
diff
changeset
|
3257 its @var{place} argument must itself be a valid @code{setf} place. |
25829 | 3258 The @var{default} argument, if any, is ignored in this context. |
3259 The effect is to change (via @code{setcar}) the value cell in the | |
3260 list that corresponds to @var{property}, or to cons a new property-value | |
3261 pair onto the list if the property is not yet present. | |
3262 | |
3263 @example | |
3264 (put sym prop val) @equiv{} (setf (getf (symbol-plist sym) prop) val) | |
3265 @end example | |
3266 | |
3267 The @code{get} and @code{get*} functions are also @code{setf}-able. | |
3268 The fact that @code{default} is ignored can sometimes be useful: | |
3269 | |
3270 @example | |
3271 (incf (get* 'foo 'usage-count 0)) | |
3272 @end example | |
3273 | |
3274 Here, symbol @code{foo}'s @code{usage-count} property is incremented | |
3275 if it exists, or set to 1 (an incremented 0) otherwise. | |
3276 | |
3277 When not used as a @code{setf} form, @code{getf} is just a regular | |
3278 function and its @var{place} argument can actually be any Lisp | |
3279 expression. | |
3280 @end defun | |
3281 | |
3282 @defspec remf place property | |
3283 This macro removes the property-value pair for @var{property} from | |
3284 the property list stored at @var{place}, which is any @code{setf}-able | |
3285 place expression. It returns true if the property was found. Note | |
3286 that if @var{property} happens to be first on the list, this will | |
3287 effectively do a @code{(setf @var{place} (cddr @var{place}))}, | |
3288 whereas if it occurs later, this simply uses @code{setcdr} to splice | |
3289 out the property and value cells. | |
3290 @end defspec | |
3291 | |
3292 @iftex | |
3293 @secno=2 | |
3294 @end iftex | |
3295 | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
3296 @node Creating Symbols, , Property Lists, Symbols |
25829 | 3297 @section Creating Symbols |
3298 | |
3299 @noindent | |
3300 These functions create unique symbols, typically for use as | |
3301 temporary variables. | |
3302 | |
3303 @defun gensym &optional x | |
3304 This function creates a new, uninterned symbol (using @code{make-symbol}) | |
3305 with a unique name. (The name of an uninterned symbol is relevant | |
3306 only if the symbol is printed.) By default, the name is generated | |
3307 from an increasing sequence of numbers, @samp{G1000}, @samp{G1001}, | |
3308 @samp{G1002}, etc. If the optional argument @var{x} is a string, that | |
3309 string is used as a prefix instead of @samp{G}. Uninterned symbols | |
3310 are used in macro expansions for temporary variables, to ensure that | |
3311 their names will not conflict with ``real'' variables in the user's | |
3312 code. | |
3313 @end defun | |
3314 | |
3315 @defvar *gensym-counter* | |
3316 This variable holds the counter used to generate @code{gensym} names. | |
3317 It is incremented after each use by @code{gensym}. In Common Lisp | |
3318 this is initialized with 0, but this package initializes it with a | |
3319 random (time-dependent) value to avoid trouble when two files that | |
3320 each used @code{gensym} in their compilation are loaded together. | |
3321 (Uninterned symbols become interned when the compiler writes them | |
3322 out to a file and the Emacs loader loads them, so their names have to | |
3323 be treated a bit more carefully than in Common Lisp where uninterned | |
3324 symbols remain uninterned after loading.) | |
3325 @end defvar | |
3326 | |
3327 @defun gentemp &optional x | |
3328 This function is like @code{gensym}, except that it produces a new | |
3329 @emph{interned} symbol. If the symbol that is generated already | |
3330 exists, the function keeps incrementing the counter and trying | |
3331 again until a new symbol is generated. | |
3332 @end defun | |
3333 | |
3334 The Quiroz @file{cl.el} package also defined a @code{defkeyword} | |
3335 form for creating self-quoting keyword symbols. This package | |
3336 automatically creates all keywords that are called for by | |
3337 @code{&key} argument specifiers, and discourages the use of | |
3338 keywords as data unrelated to keyword arguments, so the | |
3339 @code{defkeyword} form has been discontinued. | |
3340 | |
3341 @iftex | |
3342 @chapno=11 | |
3343 @end iftex | |
3344 | |
3345 @node Numbers, Sequences, Symbols, Top | |
3346 @chapter Numbers | |
3347 | |
3348 @noindent | |
3349 This section defines a few simple Common Lisp operations on numbers | |
3350 which were left out of Emacs Lisp. | |
3351 | |
3352 @menu | |
3353 * Predicates on Numbers:: `plusp', `oddp', `floatp-safe', etc. | |
28039
c3a446101beb
Remove references to rassoc, delete, expt.
Dave Love <fx@gnu.org>
parents:
27511
diff
changeset
|
3354 * Numerical Functions:: `abs', `floor*', etc. |
25829 | 3355 * Random Numbers:: `random*', `make-random-state' |
42136
5b63c25571a8
Remove most-positive-fixnum, most-negative-fixnum.
Dave Love <fx@gnu.org>
parents:
40590
diff
changeset
|
3356 * Implementation Parameters:: `most-positive-float' |
25829 | 3357 @end menu |
3358 | |
3359 @iftex | |
3360 @secno=1 | |
3361 @end iftex | |
3362 | |
3363 @node Predicates on Numbers, Numerical Functions, Numbers, Numbers | |
3364 @section Predicates on Numbers | |
3365 | |
3366 @noindent | |
3367 These functions return @code{t} if the specified condition is | |
3368 true of the numerical argument, or @code{nil} otherwise. | |
3369 | |
3370 @defun plusp number | |
3371 This predicate tests whether @var{number} is positive. It is an | |
3372 error if the argument is not a number. | |
3373 @end defun | |
3374 | |
3375 @defun minusp number | |
3376 This predicate tests whether @var{number} is negative. It is an | |
3377 error if the argument is not a number. | |
3378 @end defun | |
3379 | |
3380 @defun oddp integer | |
3381 This predicate tests whether @var{integer} is odd. It is an | |
3382 error if the argument is not an integer. | |
3383 @end defun | |
3384 | |
3385 @defun evenp integer | |
3386 This predicate tests whether @var{integer} is even. It is an | |
3387 error if the argument is not an integer. | |
3388 @end defun | |
3389 | |
3390 @defun floatp-safe object | |
3391 This predicate tests whether @var{object} is a floating-point | |
3392 number. On systems that support floating-point, this is equivalent | |
3393 to @code{floatp}. On other systems, this always returns @code{nil}. | |
3394 @end defun | |
3395 | |
3396 @iftex | |
3397 @secno=3 | |
3398 @end iftex | |
3399 | |
3400 @node Numerical Functions, Random Numbers, Predicates on Numbers, Numbers | |
3401 @section Numerical Functions | |
3402 | |
3403 @noindent | |
3404 These functions perform various arithmetic operations on numbers. | |
3405 | |
3406 @defun gcd &rest integers | |
3407 This function returns the Greatest Common Divisor of the arguments. | |
3408 For one argument, it returns the absolute value of that argument. | |
3409 For zero arguments, it returns zero. | |
3410 @end defun | |
3411 | |
3412 @defun lcm &rest integers | |
3413 This function returns the Least Common Multiple of the arguments. | |
3414 For one argument, it returns the absolute value of that argument. | |
3415 For zero arguments, it returns one. | |
3416 @end defun | |
3417 | |
3418 @defun isqrt integer | |
3419 This function computes the ``integer square root'' of its integer | |
3420 argument, i.e., the greatest integer less than or equal to the true | |
3421 square root of the argument. | |
3422 @end defun | |
3423 | |
3424 @defun floor* number &optional divisor | |
3425 This function implements the Common Lisp @code{floor} function. | |
3426 It is called @code{floor*} to avoid name conflicts with the | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
3427 simpler @code{floor} function built-in to Emacs. |
25829 | 3428 |
3429 With one argument, @code{floor*} returns a list of two numbers: | |
3430 The argument rounded down (toward minus infinity) to an integer, | |
3431 and the ``remainder'' which would have to be added back to the | |
3432 first return value to yield the argument again. If the argument | |
3433 is an integer @var{x}, the result is always the list @code{(@var{x} 0)}. | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
3434 If the argument is a floating-point number, the first |
25829 | 3435 result is a Lisp integer and the second is a Lisp float between |
3436 0 (inclusive) and 1 (exclusive). | |
3437 | |
3438 With two arguments, @code{floor*} divides @var{number} by | |
3439 @var{divisor}, and returns the floor of the quotient and the | |
3440 corresponding remainder as a list of two numbers. If | |
3441 @code{(floor* @var{x} @var{y})} returns @code{(@var{q} @var{r})}, | |
3442 then @code{@var{q}*@var{y} + @var{r} = @var{x}}, with @var{r} | |
3443 between 0 (inclusive) and @var{r} (exclusive). Also, note | |
3444 that @code{(floor* @var{x})} is exactly equivalent to | |
3445 @code{(floor* @var{x} 1)}. | |
3446 | |
3447 This function is entirely compatible with Common Lisp's @code{floor} | |
3448 function, except that it returns the two results in a list since | |
3449 Emacs Lisp does not support multiple-valued functions. | |
3450 @end defun | |
3451 | |
3452 @defun ceiling* number &optional divisor | |
3453 This function implements the Common Lisp @code{ceiling} function, | |
3454 which is analogous to @code{floor} except that it rounds the | |
3455 argument or quotient of the arguments up toward plus infinity. | |
3456 The remainder will be between 0 and minus @var{r}. | |
3457 @end defun | |
3458 | |
3459 @defun truncate* number &optional divisor | |
3460 This function implements the Common Lisp @code{truncate} function, | |
3461 which is analogous to @code{floor} except that it rounds the | |
3462 argument or quotient of the arguments toward zero. Thus it is | |
3463 equivalent to @code{floor*} if the argument or quotient is | |
3464 positive, or to @code{ceiling*} otherwise. The remainder has | |
3465 the same sign as @var{number}. | |
3466 @end defun | |
3467 | |
3468 @defun round* number &optional divisor | |
3469 This function implements the Common Lisp @code{round} function, | |
3470 which is analogous to @code{floor} except that it rounds the | |
3471 argument or quotient of the arguments to the nearest integer. | |
3472 In the case of a tie (the argument or quotient is exactly | |
3473 halfway between two integers), it rounds to the even integer. | |
3474 @end defun | |
3475 | |
3476 @defun mod* number divisor | |
3477 This function returns the same value as the second return value | |
3478 of @code{floor}. | |
3479 @end defun | |
3480 | |
3481 @defun rem* number divisor | |
3482 This function returns the same value as the second return value | |
3483 of @code{truncate}. | |
3484 @end defun | |
3485 | |
3486 These definitions are compatible with those in the Quiroz | |
3487 @file{cl.el} package, except that this package appends @samp{*} | |
3488 to certain function names to avoid conflicts with existing | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
3489 Emacs functions, and that the mechanism for returning |
25829 | 3490 multiple values is different. |
3491 | |
3492 @iftex | |
3493 @secno=8 | |
3494 @end iftex | |
3495 | |
3496 @node Random Numbers, Implementation Parameters, Numerical Functions, Numbers | |
3497 @section Random Numbers | |
3498 | |
3499 @noindent | |
3500 This package also provides an implementation of the Common Lisp | |
3501 random number generator. It uses its own additive-congruential | |
3502 algorithm, which is much more likely to give statistically clean | |
3503 random numbers than the simple generators supplied by many | |
3504 operating systems. | |
3505 | |
3506 @defun random* number &optional state | |
3507 This function returns a random nonnegative number less than | |
3508 @var{number}, and of the same type (either integer or floating-point). | |
3509 The @var{state} argument should be a @code{random-state} object | |
3510 which holds the state of the random number generator. The | |
3511 function modifies this state object as a side effect. If | |
3512 @var{state} is omitted, it defaults to the variable | |
3513 @code{*random-state*}, which contains a pre-initialized | |
3514 @code{random-state} object. | |
3515 @end defun | |
3516 | |
3517 @defvar *random-state* | |
3518 This variable contains the system ``default'' @code{random-state} | |
3519 object, used for calls to @code{random*} that do not specify an | |
3520 alternative state object. Since any number of programs in the | |
3521 Emacs process may be accessing @code{*random-state*} in interleaved | |
3522 fashion, the sequence generated from this variable will be | |
3523 irreproducible for all intents and purposes. | |
3524 @end defvar | |
3525 | |
3526 @defun make-random-state &optional state | |
3527 This function creates or copies a @code{random-state} object. | |
3528 If @var{state} is omitted or @code{nil}, it returns a new copy of | |
3529 @code{*random-state*}. This is a copy in the sense that future | |
3530 sequences of calls to @code{(random* @var{n})} and | |
3531 @code{(random* @var{n} @var{s})} (where @var{s} is the new | |
3532 random-state object) will return identical sequences of random | |
3533 numbers. | |
3534 | |
3535 If @var{state} is a @code{random-state} object, this function | |
3536 returns a copy of that object. If @var{state} is @code{t}, this | |
3537 function returns a new @code{random-state} object seeded from the | |
3538 date and time. As an extension to Common Lisp, @var{state} may also | |
3539 be an integer in which case the new object is seeded from that | |
3540 integer; each different integer seed will result in a completely | |
3541 different sequence of random numbers. | |
3542 | |
60927
bae786986f2e
* calc.texi, cl.texi, gnus.texi, idlwave.texi, reftex.texi: Replace
Werner LEMBERG <wl@gnu.org>
parents:
55833
diff
changeset
|
3543 It is valid to print a @code{random-state} object to a buffer or |
25829 | 3544 file and later read it back with @code{read}. If a program wishes |
3545 to use a sequence of pseudo-random numbers which can be reproduced | |
3546 later for debugging, it can call @code{(make-random-state t)} to | |
3547 get a new sequence, then print this sequence to a file. When the | |
3548 program is later rerun, it can read the original run's random-state | |
3549 from the file. | |
3550 @end defun | |
3551 | |
3552 @defun random-state-p object | |
3553 This predicate returns @code{t} if @var{object} is a | |
3554 @code{random-state} object, or @code{nil} otherwise. | |
3555 @end defun | |
3556 | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
3557 @node Implementation Parameters, , Random Numbers, Numbers |
25829 | 3558 @section Implementation Parameters |
3559 | |
3560 @noindent | |
3561 This package defines several useful constants having to with numbers. | |
3562 | |
3563 The following parameters have to do with floating-point numbers. | |
3564 This package determines their values by exercising the computer's | |
3565 floating-point arithmetic in various ways. Because this operation | |
3566 might be slow, the code for initializing them is kept in a separate | |
3567 function that must be called before the parameters can be used. | |
3568 | |
3569 @defun cl-float-limits | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
3570 This function makes sure that the Common Lisp floating-point parameters |
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
3571 like @code{most-positive-float} have been initialized. Until it is |
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
3572 called, these parameters will be @code{nil}. If this version of Emacs |
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
3573 does not support floats, the parameters will remain @code{nil}. If the |
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
3574 parameters have already been initialized, the function returns |
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
3575 immediately. |
25829 | 3576 |
3577 The algorithm makes assumptions that will be valid for most modern | |
3578 machines, but will fail if the machine's arithmetic is extremely | |
3579 unusual, e.g., decimal. | |
3580 @end defun | |
3581 | |
3582 Since true Common Lisp supports up to four different floating-point | |
3583 precisions, it has families of constants like | |
3584 @code{most-positive-single-float}, @code{most-positive-double-float}, | |
3585 @code{most-positive-long-float}, and so on. Emacs has only one | |
3586 floating-point precision, so this package omits the precision word | |
3587 from the constants' names. | |
3588 | |
3589 @defvar most-positive-float | |
3590 This constant equals the largest value a Lisp float can hold. | |
3591 For those systems whose arithmetic supports infinities, this is | |
3592 the largest @emph{finite} value. For IEEE machines, the value | |
3593 is approximately @code{1.79e+308}. | |
3594 @end defvar | |
3595 | |
3596 @defvar most-negative-float | |
3597 This constant equals the most-negative value a Lisp float can hold. | |
3598 (It is assumed to be equal to @code{(- most-positive-float)}.) | |
3599 @end defvar | |
3600 | |
3601 @defvar least-positive-float | |
3602 This constant equals the smallest Lisp float value greater than zero. | |
3603 For IEEE machines, it is about @code{4.94e-324} if denormals are | |
3604 supported or @code{2.22e-308} if not. | |
3605 @end defvar | |
3606 | |
3607 @defvar least-positive-normalized-float | |
3608 This constant equals the smallest @emph{normalized} Lisp float greater | |
3609 than zero, i.e., the smallest value for which IEEE denormalization | |
3610 will not result in a loss of precision. For IEEE machines, this | |
3611 value is about @code{2.22e-308}. For machines that do not support | |
3612 the concept of denormalization and gradual underflow, this constant | |
3613 will always equal @code{least-positive-float}. | |
3614 @end defvar | |
3615 | |
3616 @defvar least-negative-float | |
3617 This constant is the negative counterpart of @code{least-positive-float}. | |
3618 @end defvar | |
3619 | |
3620 @defvar least-negative-normalized-float | |
3621 This constant is the negative counterpart of | |
3622 @code{least-positive-normalized-float}. | |
3623 @end defvar | |
3624 | |
3625 @defvar float-epsilon | |
3626 This constant is the smallest positive Lisp float that can be added | |
3627 to 1.0 to produce a distinct value. Adding a smaller number to 1.0 | |
3628 will yield 1.0 again due to roundoff. For IEEE machines, epsilon | |
3629 is about @code{2.22e-16}. | |
3630 @end defvar | |
3631 | |
3632 @defvar float-negative-epsilon | |
3633 This is the smallest positive value that can be subtracted from | |
3634 1.0 to produce a distinct value. For IEEE machines, it is about | |
3635 @code{1.11e-16}. | |
3636 @end defvar | |
3637 | |
3638 @iftex | |
3639 @chapno=13 | |
3640 @end iftex | |
3641 | |
3642 @node Sequences, Lists, Numbers, Top | |
3643 @chapter Sequences | |
3644 | |
3645 @noindent | |
3646 Common Lisp defines a number of functions that operate on | |
3647 @dfn{sequences}, which are either lists, strings, or vectors. | |
3648 Emacs Lisp includes a few of these, notably @code{elt} and | |
3649 @code{length}; this package defines most of the rest. | |
3650 | |
3651 @menu | |
3652 * Sequence Basics:: Arguments shared by all sequence functions | |
3653 * Mapping over Sequences:: `mapcar*', `mapcan', `map', `every', etc. | |
3654 * Sequence Functions:: `subseq', `remove*', `substitute', etc. | |
3655 * Searching Sequences:: `find', `position', `count', `search', etc. | |
3656 * Sorting Sequences:: `sort*', `stable-sort', `merge' | |
3657 @end menu | |
3658 | |
3659 @node Sequence Basics, Mapping over Sequences, Sequences, Sequences | |
3660 @section Sequence Basics | |
3661 | |
3662 @noindent | |
3663 Many of the sequence functions take keyword arguments; @pxref{Argument | |
3664 Lists}. All keyword arguments are optional and, if specified, | |
3665 may appear in any order. | |
3666 | |
3667 The @code{:key} argument should be passed either @code{nil}, or a | |
3668 function of one argument. This key function is used as a filter | |
3669 through which the elements of the sequence are seen; for example, | |
3670 @code{(find x y :key 'car)} is similar to @code{(assoc* x y)}: | |
3671 It searches for an element of the list whose @code{car} equals | |
3672 @code{x}, rather than for an element which equals @code{x} itself. | |
3673 If @code{:key} is omitted or @code{nil}, the filter is effectively | |
3674 the identity function. | |
3675 | |
3676 The @code{:test} and @code{:test-not} arguments should be either | |
3677 @code{nil}, or functions of two arguments. The test function is | |
3678 used to compare two sequence elements, or to compare a search value | |
3679 with sequence elements. (The two values are passed to the test | |
3680 function in the same order as the original sequence function | |
3681 arguments from which they are derived, or, if they both come from | |
3682 the same sequence, in the same order as they appear in that sequence.) | |
3683 The @code{:test} argument specifies a function which must return | |
3684 true (non-@code{nil}) to indicate a match; instead, you may use | |
3685 @code{:test-not} to give a function which returns @emph{false} to | |
3686 indicate a match. The default test function is @code{:test 'eql}. | |
3687 | |
3688 Many functions which take @var{item} and @code{:test} or @code{:test-not} | |
3689 arguments also come in @code{-if} and @code{-if-not} varieties, | |
3690 where a @var{predicate} function is passed instead of @var{item}, | |
3691 and sequence elements match if the predicate returns true on them | |
3692 (or false in the case of @code{-if-not}). For example: | |
3693 | |
3694 @example | |
3695 (remove* 0 seq :test '=) @equiv{} (remove-if 'zerop seq) | |
3696 @end example | |
3697 | |
3698 @noindent | |
3699 to remove all zeros from sequence @code{seq}. | |
3700 | |
3701 Some operations can work on a subsequence of the argument sequence; | |
3702 these function take @code{:start} and @code{:end} arguments which | |
3703 default to zero and the length of the sequence, respectively. | |
3704 Only elements between @var{start} (inclusive) and @var{end} | |
3705 (exclusive) are affected by the operation. The @var{end} argument | |
3706 may be passed @code{nil} to signify the length of the sequence; | |
3707 otherwise, both @var{start} and @var{end} must be integers, with | |
3708 @code{0 <= @var{start} <= @var{end} <= (length @var{seq})}. | |
3709 If the function takes two sequence arguments, the limits are | |
3710 defined by keywords @code{:start1} and @code{:end1} for the first, | |
3711 and @code{:start2} and @code{:end2} for the second. | |
3712 | |
3713 A few functions accept a @code{:from-end} argument, which, if | |
3714 non-@code{nil}, causes the operation to go from right-to-left | |
3715 through the sequence instead of left-to-right, and a @code{:count} | |
3716 argument, which specifies an integer maximum number of elements | |
3717 to be removed or otherwise processed. | |
3718 | |
3719 The sequence functions make no guarantees about the order in | |
3720 which the @code{:test}, @code{:test-not}, and @code{:key} functions | |
3721 are called on various elements. Therefore, it is a bad idea to depend | |
3722 on side effects of these functions. For example, @code{:from-end} | |
3723 may cause the sequence to be scanned actually in reverse, or it may | |
3724 be scanned forwards but computing a result ``as if'' it were scanned | |
3725 backwards. (Some functions, like @code{mapcar*} and @code{every}, | |
3726 @emph{do} specify exactly the order in which the function is called | |
3727 so side effects are perfectly acceptable in those cases.) | |
3728 | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
3729 Strings may contain ``text properties'' as well |
25829 | 3730 as character data. Except as noted, it is undefined whether or |
3731 not text properties are preserved by sequence functions. For | |
3732 example, @code{(remove* ?A @var{str})} may or may not preserve | |
3733 the properties of the characters copied from @var{str} into the | |
3734 result. | |
3735 | |
3736 @node Mapping over Sequences, Sequence Functions, Sequence Basics, Sequences | |
3737 @section Mapping over Sequences | |
3738 | |
3739 @noindent | |
3740 These functions ``map'' the function you specify over the elements | |
3741 of lists or arrays. They are all variations on the theme of the | |
3742 built-in function @code{mapcar}. | |
3743 | |
3744 @defun mapcar* function seq &rest more-seqs | |
3745 This function calls @var{function} on successive parallel sets of | |
3746 elements from its argument sequences. Given a single @var{seq} | |
3747 argument it is equivalent to @code{mapcar}; given @var{n} sequences, | |
3748 it calls the function with the first elements of each of the sequences | |
3749 as the @var{n} arguments to yield the first element of the result | |
3750 list, then with the second elements, and so on. The mapping stops as | |
3751 soon as the shortest sequence runs out. The argument sequences may | |
3752 be any mixture of lists, strings, and vectors; the return sequence | |
3753 is always a list. | |
3754 | |
3755 Common Lisp's @code{mapcar} accepts multiple arguments but works | |
3756 only on lists; Emacs Lisp's @code{mapcar} accepts a single sequence | |
3757 argument. This package's @code{mapcar*} works as a compatible | |
3758 superset of both. | |
3759 @end defun | |
3760 | |
3761 @defun map result-type function seq &rest more-seqs | |
3762 This function maps @var{function} over the argument sequences, | |
3763 just like @code{mapcar*}, but it returns a sequence of type | |
3764 @var{result-type} rather than a list. @var{result-type} must | |
3765 be one of the following symbols: @code{vector}, @code{string}, | |
3766 @code{list} (in which case the effect is the same as for | |
3767 @code{mapcar*}), or @code{nil} (in which case the results are | |
3768 thrown away and @code{map} returns @code{nil}). | |
3769 @end defun | |
3770 | |
3771 @defun maplist function list &rest more-lists | |
3772 This function calls @var{function} on each of its argument lists, | |
3773 then on the @code{cdr}s of those lists, and so on, until the | |
3774 shortest list runs out. The results are returned in the form | |
3775 of a list. Thus, @code{maplist} is like @code{mapcar*} except | |
3776 that it passes in the list pointers themselves rather than the | |
3777 @code{car}s of the advancing pointers. | |
3778 @end defun | |
3779 | |
3780 @defun mapc function seq &rest more-seqs | |
36931 | 3781 This function is like @code{mapcar*}, except that the values returned |
3782 by @var{function} are ignored and thrown away rather than being | |
3783 collected into a list. The return value of @code{mapc} is @var{seq}, | |
3784 the first sequence. This function is more general than the Emacs | |
3785 primitive @code{mapc}. | |
25829 | 3786 @end defun |
3787 | |
3788 @defun mapl function list &rest more-lists | |
3789 This function is like @code{maplist}, except that it throws away | |
3790 the values returned by @var{function}. | |
3791 @end defun | |
3792 | |
3793 @defun mapcan function seq &rest more-seqs | |
3794 This function is like @code{mapcar*}, except that it concatenates | |
3795 the return values (which must be lists) using @code{nconc}, | |
3796 rather than simply collecting them into a list. | |
3797 @end defun | |
3798 | |
3799 @defun mapcon function list &rest more-lists | |
3800 This function is like @code{maplist}, except that it concatenates | |
3801 the return values using @code{nconc}. | |
3802 @end defun | |
3803 | |
3804 @defun some predicate seq &rest more-seqs | |
3805 This function calls @var{predicate} on each element of @var{seq} | |
3806 in turn; if @var{predicate} returns a non-@code{nil} value, | |
3807 @code{some} returns that value, otherwise it returns @code{nil}. | |
3808 Given several sequence arguments, it steps through the sequences | |
3809 in parallel until the shortest one runs out, just as in | |
3810 @code{mapcar*}. You can rely on the left-to-right order in which | |
3811 the elements are visited, and on the fact that mapping stops | |
3812 immediately as soon as @var{predicate} returns non-@code{nil}. | |
3813 @end defun | |
3814 | |
3815 @defun every predicate seq &rest more-seqs | |
3816 This function calls @var{predicate} on each element of the sequence(s) | |
3817 in turn; it returns @code{nil} as soon as @var{predicate} returns | |
3818 @code{nil} for any element, or @code{t} if the predicate was true | |
3819 for all elements. | |
3820 @end defun | |
3821 | |
3822 @defun notany predicate seq &rest more-seqs | |
3823 This function calls @var{predicate} on each element of the sequence(s) | |
3824 in turn; it returns @code{nil} as soon as @var{predicate} returns | |
3825 a non-@code{nil} value for any element, or @code{t} if the predicate | |
3826 was @code{nil} for all elements. | |
3827 @end defun | |
3828 | |
3829 @defun notevery predicate seq &rest more-seqs | |
3830 This function calls @var{predicate} on each element of the sequence(s) | |
3831 in turn; it returns a non-@code{nil} value as soon as @var{predicate} | |
3832 returns @code{nil} for any element, or @code{t} if the predicate was | |
3833 true for all elements. | |
3834 @end defun | |
3835 | |
3836 @defun reduce function seq @t{&key :from-end :start :end :initial-value :key} | |
3837 This function combines the elements of @var{seq} using an associative | |
3838 binary operation. Suppose @var{function} is @code{*} and @var{seq} is | |
3839 the list @code{(2 3 4 5)}. The first two elements of the list are | |
3840 combined with @code{(* 2 3) = 6}; this is combined with the next | |
3841 element, @code{(* 6 4) = 24}, and that is combined with the final | |
3842 element: @code{(* 24 5) = 120}. Note that the @code{*} function happens | |
3843 to be self-reducing, so that @code{(* 2 3 4 5)} has the same effect as | |
3844 an explicit call to @code{reduce}. | |
3845 | |
3846 If @code{:from-end} is true, the reduction is right-associative instead | |
3847 of left-associative: | |
3848 | |
3849 @example | |
3850 (reduce '- '(1 2 3 4)) | |
3851 @equiv{} (- (- (- 1 2) 3) 4) @result{} -8 | |
3852 (reduce '- '(1 2 3 4) :from-end t) | |
3853 @equiv{} (- 1 (- 2 (- 3 4))) @result{} -2 | |
3854 @end example | |
3855 | |
3856 If @code{:key} is specified, it is a function of one argument which | |
3857 is called on each of the sequence elements in turn. | |
3858 | |
3859 If @code{:initial-value} is specified, it is effectively added to the | |
3860 front (or rear in the case of @code{:from-end}) of the sequence. | |
3861 The @code{:key} function is @emph{not} applied to the initial value. | |
3862 | |
3863 If the sequence, including the initial value, has exactly one element | |
3864 then that element is returned without ever calling @var{function}. | |
3865 If the sequence is empty (and there is no initial value), then | |
3866 @var{function} is called with no arguments to obtain the return value. | |
3867 @end defun | |
3868 | |
3869 All of these mapping operations can be expressed conveniently in | |
3870 terms of the @code{loop} macro. In compiled code, @code{loop} will | |
3871 be faster since it generates the loop as in-line code with no | |
3872 function calls. | |
3873 | |
3874 @node Sequence Functions, Searching Sequences, Mapping over Sequences, Sequences | |
3875 @section Sequence Functions | |
3876 | |
3877 @noindent | |
3878 This section describes a number of Common Lisp functions for | |
3879 operating on sequences. | |
3880 | |
3881 @defun subseq sequence start &optional end | |
3882 This function returns a given subsequence of the argument | |
3883 @var{sequence}, which may be a list, string, or vector. | |
3884 The indices @var{start} and @var{end} must be in range, and | |
3885 @var{start} must be no greater than @var{end}. If @var{end} | |
3886 is omitted, it defaults to the length of the sequence. The | |
3887 return value is always a copy; it does not share structure | |
3888 with @var{sequence}. | |
3889 | |
3890 As an extension to Common Lisp, @var{start} and/or @var{end} | |
3891 may be negative, in which case they represent a distance back | |
3892 from the end of the sequence. This is for compatibility with | |
3893 Emacs' @code{substring} function. Note that @code{subseq} is | |
3894 the @emph{only} sequence function that allows negative | |
3895 @var{start} and @var{end}. | |
3896 | |
3897 You can use @code{setf} on a @code{subseq} form to replace a | |
3898 specified range of elements with elements from another sequence. | |
3899 The replacement is done as if by @code{replace}, described below. | |
3900 @end defun | |
3901 | |
3902 @defun concatenate result-type &rest seqs | |
3903 This function concatenates the argument sequences together to | |
3904 form a result sequence of type @var{result-type}, one of the | |
3905 symbols @code{vector}, @code{string}, or @code{list}. The | |
3906 arguments are always copied, even in cases such as | |
3907 @code{(concatenate 'list '(1 2 3))} where the result is | |
3908 identical to an argument. | |
3909 @end defun | |
3910 | |
3911 @defun fill seq item @t{&key :start :end} | |
3912 This function fills the elements of the sequence (or the specified | |
3913 part of the sequence) with the value @var{item}. | |
3914 @end defun | |
3915 | |
3916 @defun replace seq1 seq2 @t{&key :start1 :end1 :start2 :end2} | |
3917 This function copies part of @var{seq2} into part of @var{seq1}. | |
3918 The sequence @var{seq1} is not stretched or resized; the amount | |
3919 of data copied is simply the shorter of the source and destination | |
3920 (sub)sequences. The function returns @var{seq1}. | |
3921 | |
3922 If @var{seq1} and @var{seq2} are @code{eq}, then the replacement | |
3923 will work correctly even if the regions indicated by the start | |
3924 and end arguments overlap. However, if @var{seq1} and @var{seq2} | |
3925 are lists which share storage but are not @code{eq}, and the | |
3926 start and end arguments specify overlapping regions, the effect | |
3927 is undefined. | |
3928 @end defun | |
3929 | |
3930 @defun remove* item seq @t{&key :test :test-not :key :count :start :end :from-end} | |
3931 This returns a copy of @var{seq} with all elements matching | |
3932 @var{item} removed. The result may share storage with or be | |
3933 @code{eq} to @var{seq} in some circumstances, but the original | |
3934 @var{seq} will not be modified. The @code{:test}, @code{:test-not}, | |
3935 and @code{:key} arguments define the matching test that is used; | |
3936 by default, elements @code{eql} to @var{item} are removed. The | |
3937 @code{:count} argument specifies the maximum number of matching | |
3938 elements that can be removed (only the leftmost @var{count} matches | |
3939 are removed). The @code{:start} and @code{:end} arguments specify | |
3940 a region in @var{seq} in which elements will be removed; elements | |
3941 outside that region are not matched or removed. The @code{:from-end} | |
3942 argument, if true, says that elements should be deleted from the | |
3943 end of the sequence rather than the beginning (this matters only | |
3944 if @var{count} was also specified). | |
3945 @end defun | |
3946 | |
3947 @defun delete* item seq @t{&key :test :test-not :key :count :start :end :from-end} | |
3948 This deletes all elements of @var{seq} which match @var{item}. | |
3949 It is a destructive operation. Since Emacs Lisp does not support | |
3950 stretchable strings or vectors, this is the same as @code{remove*} | |
3951 for those sequence types. On lists, @code{remove*} will copy the | |
3952 list if necessary to preserve the original list, whereas | |
3953 @code{delete*} will splice out parts of the argument list. | |
3954 Compare @code{append} and @code{nconc}, which are analogous | |
3955 non-destructive and destructive list operations in Emacs Lisp. | |
3956 @end defun | |
3957 | |
3958 @findex remove-if | |
3959 @findex remove-if-not | |
3960 @findex delete-if | |
3961 @findex delete-if-not | |
3962 The predicate-oriented functions @code{remove-if}, @code{remove-if-not}, | |
3963 @code{delete-if}, and @code{delete-if-not} are defined similarly. | |
3964 | |
3965 @defun remove-duplicates seq @t{&key :test :test-not :key :start :end :from-end} | |
3966 This function returns a copy of @var{seq} with duplicate elements | |
3967 removed. Specifically, if two elements from the sequence match | |
3968 according to the @code{:test}, @code{:test-not}, and @code{:key} | |
3969 arguments, only the rightmost one is retained. If @code{:from-end} | |
3970 is true, the leftmost one is retained instead. If @code{:start} or | |
3971 @code{:end} is specified, only elements within that subsequence are | |
3972 examined or removed. | |
3973 @end defun | |
3974 | |
3975 @defun delete-duplicates seq @t{&key :test :test-not :key :start :end :from-end} | |
3976 This function deletes duplicate elements from @var{seq}. It is | |
3977 a destructive version of @code{remove-duplicates}. | |
3978 @end defun | |
3979 | |
3980 @defun substitute new old seq @t{&key :test :test-not :key :count :start :end :from-end} | |
3981 This function returns a copy of @var{seq}, with all elements | |
3982 matching @var{old} replaced with @var{new}. The @code{:count}, | |
3983 @code{:start}, @code{:end}, and @code{:from-end} arguments may be | |
3984 used to limit the number of substitutions made. | |
3985 @end defun | |
3986 | |
3987 @defun nsubstitute new old seq @t{&key :test :test-not :key :count :start :end :from-end} | |
3988 This is a destructive version of @code{substitute}; it performs | |
3989 the substitution using @code{setcar} or @code{aset} rather than | |
3990 by returning a changed copy of the sequence. | |
3991 @end defun | |
3992 | |
3993 @findex substitute-if | |
3994 @findex substitute-if-not | |
3995 @findex nsubstitute-if | |
3996 @findex nsubstitute-if-not | |
3997 The @code{substitute-if}, @code{substitute-if-not}, @code{nsubstitute-if}, | |
3998 and @code{nsubstitute-if-not} functions are defined similarly. For | |
3999 these, a @var{predicate} is given in place of the @var{old} argument. | |
4000 | |
4001 @node Searching Sequences, Sorting Sequences, Sequence Functions, Sequences | |
4002 @section Searching Sequences | |
4003 | |
4004 @noindent | |
4005 These functions search for elements or subsequences in a sequence. | |
4006 (See also @code{member*} and @code{assoc*}; @pxref{Lists}.) | |
4007 | |
4008 @defun find item seq @t{&key :test :test-not :key :start :end :from-end} | |
4009 This function searches @var{seq} for an element matching @var{item}. | |
4010 If it finds a match, it returns the matching element. Otherwise, | |
4011 it returns @code{nil}. It returns the leftmost match, unless | |
4012 @code{:from-end} is true, in which case it returns the rightmost | |
4013 match. The @code{:start} and @code{:end} arguments may be used to | |
4014 limit the range of elements that are searched. | |
4015 @end defun | |
4016 | |
4017 @defun position item seq @t{&key :test :test-not :key :start :end :from-end} | |
4018 This function is like @code{find}, except that it returns the | |
4019 integer position in the sequence of the matching item rather than | |
4020 the item itself. The position is relative to the start of the | |
4021 sequence as a whole, even if @code{:start} is non-zero. The function | |
4022 returns @code{nil} if no matching element was found. | |
4023 @end defun | |
4024 | |
4025 @defun count item seq @t{&key :test :test-not :key :start :end} | |
4026 This function returns the number of elements of @var{seq} which | |
4027 match @var{item}. The result is always a nonnegative integer. | |
4028 @end defun | |
4029 | |
4030 @findex find-if | |
4031 @findex find-if-not | |
4032 @findex position-if | |
4033 @findex position-if-not | |
4034 @findex count-if | |
4035 @findex count-if-not | |
4036 The @code{find-if}, @code{find-if-not}, @code{position-if}, | |
4037 @code{position-if-not}, @code{count-if}, and @code{count-if-not} | |
4038 functions are defined similarly. | |
4039 | |
4040 @defun mismatch seq1 seq2 @t{&key :test :test-not :key :start1 :end1 :start2 :end2 :from-end} | |
4041 This function compares the specified parts of @var{seq1} and | |
4042 @var{seq2}. If they are the same length and the corresponding | |
4043 elements match (according to @code{:test}, @code{:test-not}, | |
4044 and @code{:key}), the function returns @code{nil}. If there is | |
4045 a mismatch, the function returns the index (relative to @var{seq1}) | |
4046 of the first mismatching element. This will be the leftmost pair of | |
4047 elements which do not match, or the position at which the shorter of | |
4048 the two otherwise-matching sequences runs out. | |
4049 | |
4050 If @code{:from-end} is true, then the elements are compared from right | |
4051 to left starting at @code{(1- @var{end1})} and @code{(1- @var{end2})}. | |
4052 If the sequences differ, then one plus the index of the rightmost | |
4053 difference (relative to @var{seq1}) is returned. | |
4054 | |
4055 An interesting example is @code{(mismatch str1 str2 :key 'upcase)}, | |
4056 which compares two strings case-insensitively. | |
4057 @end defun | |
4058 | |
4059 @defun search seq1 seq2 @t{&key :test :test-not :key :from-end :start1 :end1 :start2 :end2} | |
4060 This function searches @var{seq2} for a subsequence that matches | |
4061 @var{seq1} (or part of it specified by @code{:start1} and | |
4062 @code{:end1}.) Only matches which fall entirely within the region | |
4063 defined by @code{:start2} and @code{:end2} will be considered. | |
4064 The return value is the index of the leftmost element of the | |
4065 leftmost match, relative to the start of @var{seq2}, or @code{nil} | |
4066 if no matches were found. If @code{:from-end} is true, the | |
4067 function finds the @emph{rightmost} matching subsequence. | |
4068 @end defun | |
4069 | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
4070 @node Sorting Sequences, , Searching Sequences, Sequences |
25829 | 4071 @section Sorting Sequences |
4072 | |
4073 @defun sort* seq predicate @t{&key :key} | |
4074 This function sorts @var{seq} into increasing order as determined | |
4075 by using @var{predicate} to compare pairs of elements. @var{predicate} | |
4076 should return true (non-@code{nil}) if and only if its first argument | |
4077 is less than (not equal to) its second argument. For example, | |
4078 @code{<} and @code{string-lessp} are suitable predicate functions | |
4079 for sorting numbers and strings, respectively; @code{>} would sort | |
4080 numbers into decreasing rather than increasing order. | |
4081 | |
4082 This function differs from Emacs' built-in @code{sort} in that it | |
4083 can operate on any type of sequence, not just lists. Also, it | |
4084 accepts a @code{:key} argument which is used to preprocess data | |
4085 fed to the @var{predicate} function. For example, | |
4086 | |
4087 @example | |
4088 (setq data (sort data 'string-lessp :key 'downcase)) | |
4089 @end example | |
4090 | |
4091 @noindent | |
4092 sorts @var{data}, a sequence of strings, into increasing alphabetical | |
4093 order without regard to case. A @code{:key} function of @code{car} | |
4094 would be useful for sorting association lists. | |
4095 | |
4096 The @code{sort*} function is destructive; it sorts lists by actually | |
4097 rearranging the @code{cdr} pointers in suitable fashion. | |
4098 @end defun | |
4099 | |
4100 @defun stable-sort seq predicate @t{&key :key} | |
4101 This function sorts @var{seq} @dfn{stably}, meaning two elements | |
4102 which are equal in terms of @var{predicate} are guaranteed not to | |
4103 be rearranged out of their original order by the sort. | |
4104 | |
4105 In practice, @code{sort*} and @code{stable-sort} are equivalent | |
4106 in Emacs Lisp because the underlying @code{sort} function is | |
4107 stable by default. However, this package reserves the right to | |
4108 use non-stable methods for @code{sort*} in the future. | |
4109 @end defun | |
4110 | |
4111 @defun merge type seq1 seq2 predicate @t{&key :key} | |
4112 This function merges two sequences @var{seq1} and @var{seq2} by | |
4113 interleaving their elements. The result sequence, of type @var{type} | |
4114 (in the sense of @code{concatenate}), has length equal to the sum | |
4115 of the lengths of the two input sequences. The sequences may be | |
4116 modified destructively. Order of elements within @var{seq1} and | |
4117 @var{seq2} is preserved in the interleaving; elements of the two | |
4118 sequences are compared by @var{predicate} (in the sense of | |
4119 @code{sort}) and the lesser element goes first in the result. | |
4120 When elements are equal, those from @var{seq1} precede those from | |
4121 @var{seq2} in the result. Thus, if @var{seq1} and @var{seq2} are | |
4122 both sorted according to @var{predicate}, then the result will be | |
4123 a merged sequence which is (stably) sorted according to | |
4124 @var{predicate}. | |
4125 @end defun | |
4126 | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
4127 @node Lists, Structures, Sequences, Top |
25829 | 4128 @chapter Lists |
4129 | |
4130 @noindent | |
4131 The functions described here operate on lists. | |
4132 | |
4133 @menu | |
36931 | 4134 * List Functions:: `caddr', `first', `list*', etc. |
25829 | 4135 * Substitution of Expressions:: `subst', `sublis', etc. |
4136 * Lists as Sets:: `member*', `adjoin', `union', etc. | |
4137 * Association Lists:: `assoc*', `rassoc*', `acons', `pairlis' | |
4138 @end menu | |
4139 | |
4140 @node List Functions, Substitution of Expressions, Lists, Lists | |
4141 @section List Functions | |
4142 | |
4143 @noindent | |
4144 This section describes a number of simple operations on lists, | |
4145 i.e., chains of cons cells. | |
4146 | |
4147 @defun caddr x | |
4148 This function is equivalent to @code{(car (cdr (cdr @var{x})))}. | |
4149 Likewise, this package defines all 28 @code{c@var{xxx}r} functions | |
4150 where @var{xxx} is up to four @samp{a}s and/or @samp{d}s. | |
4151 All of these functions are @code{setf}-able, and calls to them | |
4152 are expanded inline by the byte-compiler for maximum efficiency. | |
4153 @end defun | |
4154 | |
4155 @defun first x | |
4156 This function is a synonym for @code{(car @var{x})}. Likewise, | |
4157 the functions @code{second}, @code{third}, @dots{}, through | |
4158 @code{tenth} return the given element of the list @var{x}. | |
4159 @end defun | |
4160 | |
4161 @defun rest x | |
4162 This function is a synonym for @code{(cdr @var{x})}. | |
4163 @end defun | |
4164 | |
4165 @defun endp x | |
4166 Common Lisp defines this function to act like @code{null}, but | |
4167 signaling an error if @code{x} is neither a @code{nil} nor a | |
4168 cons cell. This package simply defines @code{endp} as a synonym | |
4169 for @code{null}. | |
4170 @end defun | |
4171 | |
4172 @defun list-length x | |
4173 This function returns the length of list @var{x}, exactly like | |
4174 @code{(length @var{x})}, except that if @var{x} is a circular | |
4175 list (where the cdr-chain forms a loop rather than terminating | |
4176 with @code{nil}), this function returns @code{nil}. (The regular | |
4177 @code{length} function would get stuck if given a circular list.) | |
4178 @end defun | |
4179 | |
4180 @defun list* arg &rest others | |
4181 This function constructs a list of its arguments. The final | |
4182 argument becomes the @code{cdr} of the last cell constructed. | |
4183 Thus, @code{(list* @var{a} @var{b} @var{c})} is equivalent to | |
4184 @code{(cons @var{a} (cons @var{b} @var{c}))}, and | |
4185 @code{(list* @var{a} @var{b} nil)} is equivalent to | |
4186 @code{(list @var{a} @var{b})}. | |
4187 | |
4188 (Note that this function really is called @code{list*} in Common | |
4189 Lisp; it is not a name invented for this package like @code{member*} | |
4190 or @code{defun*}.) | |
4191 @end defun | |
4192 | |
4193 @defun ldiff list sublist | |
4194 If @var{sublist} is a sublist of @var{list}, i.e., is @code{eq} to | |
4195 one of the cons cells of @var{list}, then this function returns | |
4196 a copy of the part of @var{list} up to but not including | |
4197 @var{sublist}. For example, @code{(ldiff x (cddr x))} returns | |
4198 the first two elements of the list @code{x}. The result is a | |
4199 copy; the original @var{list} is not modified. If @var{sublist} | |
4200 is not a sublist of @var{list}, a copy of the entire @var{list} | |
4201 is returned. | |
4202 @end defun | |
4203 | |
4204 @defun copy-list list | |
4205 This function returns a copy of the list @var{list}. It copies | |
4206 dotted lists like @code{(1 2 . 3)} correctly. | |
4207 @end defun | |
4208 | |
4209 @defun copy-tree x &optional vecp | |
4210 This function returns a copy of the tree of cons cells @var{x}. | |
4211 Unlike @code{copy-sequence} (and its alias @code{copy-list}), | |
4212 which copies only along the @code{cdr} direction, this function | |
4213 copies (recursively) along both the @code{car} and the @code{cdr} | |
4214 directions. If @var{x} is not a cons cell, the function simply | |
4215 returns @var{x} unchanged. If the optional @var{vecp} argument | |
4216 is true, this function copies vectors (recursively) as well as | |
4217 cons cells. | |
4218 @end defun | |
4219 | |
4220 @defun tree-equal x y @t{&key :test :test-not :key} | |
4221 This function compares two trees of cons cells. If @var{x} and | |
4222 @var{y} are both cons cells, their @code{car}s and @code{cdr}s are | |
4223 compared recursively. If neither @var{x} nor @var{y} is a cons | |
4224 cell, they are compared by @code{eql}, or according to the | |
4225 specified test. The @code{:key} function, if specified, is | |
4226 applied to the elements of both trees. @xref{Sequences}. | |
4227 @end defun | |
4228 | |
4229 @iftex | |
4230 @secno=3 | |
4231 @end iftex | |
4232 | |
4233 @node Substitution of Expressions, Lists as Sets, List Functions, Lists | |
4234 @section Substitution of Expressions | |
4235 | |
4236 @noindent | |
4237 These functions substitute elements throughout a tree of cons | |
4238 cells. (@xref{Sequence Functions}, for the @code{substitute} | |
4239 function, which works on just the top-level elements of a list.) | |
4240 | |
4241 @defun subst new old tree @t{&key :test :test-not :key} | |
4242 This function substitutes occurrences of @var{old} with @var{new} | |
4243 in @var{tree}, a tree of cons cells. It returns a substituted | |
4244 tree, which will be a copy except that it may share storage with | |
4245 the argument @var{tree} in parts where no substitutions occurred. | |
4246 The original @var{tree} is not modified. This function recurses | |
4247 on, and compares against @var{old}, both @code{car}s and @code{cdr}s | |
4248 of the component cons cells. If @var{old} is itself a cons cell, | |
4249 then matching cells in the tree are substituted as usual without | |
4250 recursively substituting in that cell. Comparisons with @var{old} | |
4251 are done according to the specified test (@code{eql} by default). | |
4252 The @code{:key} function is applied to the elements of the tree | |
4253 but not to @var{old}. | |
4254 @end defun | |
4255 | |
4256 @defun nsubst new old tree @t{&key :test :test-not :key} | |
4257 This function is like @code{subst}, except that it works by | |
4258 destructive modification (by @code{setcar} or @code{setcdr}) | |
4259 rather than copying. | |
4260 @end defun | |
4261 | |
4262 @findex subst-if | |
4263 @findex subst-if-not | |
4264 @findex nsubst-if | |
4265 @findex nsubst-if-not | |
4266 The @code{subst-if}, @code{subst-if-not}, @code{nsubst-if}, and | |
4267 @code{nsubst-if-not} functions are defined similarly. | |
4268 | |
4269 @defun sublis alist tree @t{&key :test :test-not :key} | |
4270 This function is like @code{subst}, except that it takes an | |
4271 association list @var{alist} of @var{old}-@var{new} pairs. | |
4272 Each element of the tree (after applying the @code{:key} | |
4273 function, if any), is compared with the @code{car}s of | |
4274 @var{alist}; if it matches, it is replaced by the corresponding | |
4275 @code{cdr}. | |
4276 @end defun | |
4277 | |
4278 @defun nsublis alist tree @t{&key :test :test-not :key} | |
4279 This is a destructive version of @code{sublis}. | |
4280 @end defun | |
4281 | |
4282 @node Lists as Sets, Association Lists, Substitution of Expressions, Lists | |
4283 @section Lists as Sets | |
4284 | |
4285 @noindent | |
4286 These functions perform operations on lists which represent sets | |
4287 of elements. | |
4288 | |
4289 @defun member* item list @t{&key :test :test-not :key} | |
4290 This function searches @var{list} for an element matching @var{item}. | |
4291 If a match is found, it returns the cons cell whose @code{car} was | |
4292 the matching element. Otherwise, it returns @code{nil}. Elements | |
4293 are compared by @code{eql} by default; you can use the @code{:test}, | |
4294 @code{:test-not}, and @code{:key} arguments to modify this behavior. | |
4295 @xref{Sequences}. | |
4296 | |
4297 Note that this function's name is suffixed by @samp{*} to avoid | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
4298 the incompatible @code{member} function defined in Emacs. |
25829 | 4299 (That function uses @code{equal} for comparisons; it is equivalent |
4300 to @code{(member* @var{item} @var{list} :test 'equal)}.) | |
4301 @end defun | |
4302 | |
4303 @findex member-if | |
4304 @findex member-if-not | |
4305 The @code{member-if} and @code{member-if-not} functions | |
4306 analogously search for elements which satisfy a given predicate. | |
4307 | |
4308 @defun tailp sublist list | |
4309 This function returns @code{t} if @var{sublist} is a sublist of | |
4310 @var{list}, i.e., if @var{sublist} is @code{eql} to @var{list} or to | |
4311 any of its @code{cdr}s. | |
4312 @end defun | |
4313 | |
4314 @defun adjoin item list @t{&key :test :test-not :key} | |
4315 This function conses @var{item} onto the front of @var{list}, | |
4316 like @code{(cons @var{item} @var{list})}, but only if @var{item} | |
4317 is not already present on the list (as determined by @code{member*}). | |
4318 If a @code{:key} argument is specified, it is applied to | |
4319 @var{item} as well as to the elements of @var{list} during | |
4320 the search, on the reasoning that @var{item} is ``about'' to | |
4321 become part of the list. | |
4322 @end defun | |
4323 | |
4324 @defun union list1 list2 @t{&key :test :test-not :key} | |
4325 This function combines two lists which represent sets of items, | |
4326 returning a list that represents the union of those two sets. | |
4327 The result list will contain all items which appear in @var{list1} | |
4328 or @var{list2}, and no others. If an item appears in both | |
4329 @var{list1} and @var{list2} it will be copied only once. If | |
4330 an item is duplicated in @var{list1} or @var{list2}, it is | |
4331 undefined whether or not that duplication will survive in the | |
4332 result list. The order of elements in the result list is also | |
4333 undefined. | |
4334 @end defun | |
4335 | |
4336 @defun nunion list1 list2 @t{&key :test :test-not :key} | |
4337 This is a destructive version of @code{union}; rather than copying, | |
4338 it tries to reuse the storage of the argument lists if possible. | |
4339 @end defun | |
4340 | |
4341 @defun intersection list1 list2 @t{&key :test :test-not :key} | |
4342 This function computes the intersection of the sets represented | |
4343 by @var{list1} and @var{list2}. It returns the list of items | |
4344 which appear in both @var{list1} and @var{list2}. | |
4345 @end defun | |
4346 | |
4347 @defun nintersection list1 list2 @t{&key :test :test-not :key} | |
4348 This is a destructive version of @code{intersection}. It | |
4349 tries to reuse storage of @var{list1} rather than copying. | |
4350 It does @emph{not} reuse the storage of @var{list2}. | |
4351 @end defun | |
4352 | |
4353 @defun set-difference list1 list2 @t{&key :test :test-not :key} | |
4354 This function computes the ``set difference'' of @var{list1} | |
4355 and @var{list2}, i.e., the set of elements that appear in | |
4356 @var{list1} but @emph{not} in @var{list2}. | |
4357 @end defun | |
4358 | |
4359 @defun nset-difference list1 list2 @t{&key :test :test-not :key} | |
4360 This is a destructive @code{set-difference}, which will try | |
4361 to reuse @var{list1} if possible. | |
4362 @end defun | |
4363 | |
4364 @defun set-exclusive-or list1 list2 @t{&key :test :test-not :key} | |
4365 This function computes the ``set exclusive or'' of @var{list1} | |
4366 and @var{list2}, i.e., the set of elements that appear in | |
4367 exactly one of @var{list1} and @var{list2}. | |
4368 @end defun | |
4369 | |
4370 @defun nset-exclusive-or list1 list2 @t{&key :test :test-not :key} | |
4371 This is a destructive @code{set-exclusive-or}, which will try | |
4372 to reuse @var{list1} and @var{list2} if possible. | |
4373 @end defun | |
4374 | |
4375 @defun subsetp list1 list2 @t{&key :test :test-not :key} | |
4376 This function checks whether @var{list1} represents a subset | |
4377 of @var{list2}, i.e., whether every element of @var{list1} | |
4378 also appears in @var{list2}. | |
4379 @end defun | |
4380 | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
4381 @node Association Lists, , Lists as Sets, Lists |
25829 | 4382 @section Association Lists |
4383 | |
4384 @noindent | |
4385 An @dfn{association list} is a list representing a mapping from | |
4386 one set of values to another; any list whose elements are cons | |
4387 cells is an association list. | |
4388 | |
4389 @defun assoc* item a-list @t{&key :test :test-not :key} | |
4390 This function searches the association list @var{a-list} for an | |
4391 element whose @code{car} matches (in the sense of @code{:test}, | |
4392 @code{:test-not}, and @code{:key}, or by comparison with @code{eql}) | |
4393 a given @var{item}. It returns the matching element, if any, | |
4394 otherwise @code{nil}. It ignores elements of @var{a-list} which | |
4395 are not cons cells. (This corresponds to the behavior of | |
4396 @code{assq} and @code{assoc} in Emacs Lisp; Common Lisp's | |
4397 @code{assoc} ignores @code{nil}s but considers any other non-cons | |
4398 elements of @var{a-list} to be an error.) | |
4399 @end defun | |
4400 | |
4401 @defun rassoc* item a-list @t{&key :test :test-not :key} | |
4402 This function searches for an element whose @code{cdr} matches | |
4403 @var{item}. If @var{a-list} represents a mapping, this applies | |
4404 the inverse of the mapping to @var{item}. | |
4405 @end defun | |
4406 | |
4407 @findex assoc-if | |
4408 @findex assoc-if-not | |
4409 @findex rassoc-if | |
4410 @findex rassoc-if-not | |
4411 The @code{assoc-if}, @code{assoc-if-not}, @code{rassoc-if}, | |
4412 and @code{rassoc-if-not} functions are defined similarly. | |
4413 | |
4414 Two simple functions for constructing association lists are: | |
4415 | |
4416 @defun acons key value alist | |
4417 This is equivalent to @code{(cons (cons @var{key} @var{value}) @var{alist})}. | |
4418 @end defun | |
4419 | |
4420 @defun pairlis keys values &optional alist | |
4421 This is equivalent to @code{(nconc (mapcar* 'cons @var{keys} @var{values}) | |
4422 @var{alist})}. | |
4423 @end defun | |
4424 | |
4425 @iftex | |
4426 @chapno=18 | |
4427 @end iftex | |
4428 | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
4429 @node Structures, Assertions, Lists, Top |
25829 | 4430 @chapter Structures |
4431 | |
4432 @noindent | |
4433 The Common Lisp @dfn{structure} mechanism provides a general way | |
4434 to define data types similar to C's @code{struct} types. A | |
4435 structure is a Lisp object containing some number of @dfn{slots}, | |
4436 each of which can hold any Lisp data object. Functions are | |
4437 provided for accessing and setting the slots, creating or copying | |
4438 structure objects, and recognizing objects of a particular structure | |
4439 type. | |
4440 | |
4441 In true Common Lisp, each structure type is a new type distinct | |
4442 from all existing Lisp types. Since the underlying Emacs Lisp | |
4443 system provides no way to create new distinct types, this package | |
4444 implements structures as vectors (or lists upon request) with a | |
4445 special ``tag'' symbol to identify them. | |
4446 | |
4447 @defspec defstruct name slots@dots{} | |
4448 The @code{defstruct} form defines a new structure type called | |
4449 @var{name}, with the specified @var{slots}. (The @var{slots} | |
4450 may begin with a string which documents the structure type.) | |
4451 In the simplest case, @var{name} and each of the @var{slots} | |
4452 are symbols. For example, | |
4453 | |
4454 @example | |
4455 (defstruct person name age sex) | |
4456 @end example | |
4457 | |
4458 @noindent | |
4459 defines a struct type called @code{person} which contains three | |
4460 slots. Given a @code{person} object @var{p}, you can access those | |
4461 slots by calling @code{(person-name @var{p})}, @code{(person-age @var{p})}, | |
4462 and @code{(person-sex @var{p})}. You can also change these slots by | |
4463 using @code{setf} on any of these place forms: | |
4464 | |
4465 @example | |
4466 (incf (person-age birthday-boy)) | |
4467 @end example | |
4468 | |
4469 You can create a new @code{person} by calling @code{make-person}, | |
4470 which takes keyword arguments @code{:name}, @code{:age}, and | |
4471 @code{:sex} to specify the initial values of these slots in the | |
4472 new object. (Omitting any of these arguments leaves the corresponding | |
4473 slot ``undefined,'' according to the Common Lisp standard; in Emacs | |
4474 Lisp, such uninitialized slots are filled with @code{nil}.) | |
4475 | |
4476 Given a @code{person}, @code{(copy-person @var{p})} makes a new | |
4477 object of the same type whose slots are @code{eq} to those of @var{p}. | |
4478 | |
4479 Given any Lisp object @var{x}, @code{(person-p @var{x})} returns | |
4480 true if @var{x} looks like a @code{person}, false otherwise. (Again, | |
4481 in Common Lisp this predicate would be exact; in Emacs Lisp the | |
4482 best it can do is verify that @var{x} is a vector of the correct | |
4483 length which starts with the correct tag symbol.) | |
4484 | |
4485 Accessors like @code{person-name} normally check their arguments | |
4486 (effectively using @code{person-p}) and signal an error if the | |
4487 argument is the wrong type. This check is affected by | |
4488 @code{(optimize (safety @dots{}))} declarations. Safety level 1, | |
4489 the default, uses a somewhat optimized check that will detect all | |
4490 incorrect arguments, but may use an uninformative error message | |
4491 (e.g., ``expected a vector'' instead of ``expected a @code{person}''). | |
4492 Safety level 0 omits all checks except as provided by the underlying | |
4493 @code{aref} call; safety levels 2 and 3 do rigorous checking that will | |
4494 always print a descriptive error message for incorrect inputs. | |
4495 @xref{Declarations}. | |
4496 | |
4497 @example | |
4498 (setq dave (make-person :name "Dave" :sex 'male)) | |
4499 @result{} [cl-struct-person "Dave" nil male] | |
4500 (setq other (copy-person dave)) | |
4501 @result{} [cl-struct-person "Dave" nil male] | |
4502 (eq dave other) | |
4503 @result{} nil | |
4504 (eq (person-name dave) (person-name other)) | |
4505 @result{} t | |
4506 (person-p dave) | |
4507 @result{} t | |
4508 (person-p [1 2 3 4]) | |
4509 @result{} nil | |
4510 (person-p "Bogus") | |
4511 @result{} nil | |
4512 (person-p '[cl-struct-person counterfeit person object]) | |
4513 @result{} t | |
4514 @end example | |
4515 | |
4516 In general, @var{name} is either a name symbol or a list of a name | |
4517 symbol followed by any number of @dfn{struct options}; each @var{slot} | |
4518 is either a slot symbol or a list of the form @samp{(@var{slot-name} | |
4519 @var{default-value} @var{slot-options}@dots{})}. The @var{default-value} | |
4520 is a Lisp form which is evaluated any time an instance of the | |
4521 structure type is created without specifying that slot's value. | |
4522 | |
4523 Common Lisp defines several slot options, but the only one | |
4524 implemented in this package is @code{:read-only}. A non-@code{nil} | |
4525 value for this option means the slot should not be @code{setf}-able; | |
4526 the slot's value is determined when the object is created and does | |
4527 not change afterward. | |
4528 | |
4529 @example | |
4530 (defstruct person | |
4531 (name nil :read-only t) | |
4532 age | |
4533 (sex 'unknown)) | |
4534 @end example | |
4535 | |
4536 Any slot options other than @code{:read-only} are ignored. | |
4537 | |
4538 For obscure historical reasons, structure options take a different | |
4539 form than slot options. A structure option is either a keyword | |
4540 symbol, or a list beginning with a keyword symbol possibly followed | |
4541 by arguments. (By contrast, slot options are key-value pairs not | |
4542 enclosed in lists.) | |
4543 | |
4544 @example | |
4545 (defstruct (person (:constructor create-person) | |
4546 (:type list) | |
4547 :named) | |
4548 name age sex) | |
4549 @end example | |
4550 | |
4551 The following structure options are recognized. | |
4552 | |
4553 @table @code | |
4554 @iftex | |
4555 @itemmax=0 in | |
4556 @advance@leftskip-.5@tableindent | |
4557 @end iftex | |
4558 @item :conc-name | |
4559 The argument is a symbol whose print name is used as the prefix for | |
4560 the names of slot accessor functions. The default is the name of | |
4561 the struct type followed by a hyphen. The option @code{(:conc-name p-)} | |
4562 would change this prefix to @code{p-}. Specifying @code{nil} as an | |
4563 argument means no prefix, so that the slot names themselves are used | |
4564 to name the accessor functions. | |
4565 | |
4566 @item :constructor | |
4567 In the simple case, this option takes one argument which is an | |
4568 alternate name to use for the constructor function. The default | |
4569 is @code{make-@var{name}}, e.g., @code{make-person}. The above | |
4570 example changes this to @code{create-person}. Specifying @code{nil} | |
4571 as an argument means that no standard constructor should be | |
4572 generated at all. | |
4573 | |
4574 In the full form of this option, the constructor name is followed | |
4575 by an arbitrary argument list. @xref{Program Structure}, for a | |
4576 description of the format of Common Lisp argument lists. All | |
4577 options, such as @code{&rest} and @code{&key}, are supported. | |
4578 The argument names should match the slot names; each slot is | |
4579 initialized from the corresponding argument. Slots whose names | |
4580 do not appear in the argument list are initialized based on the | |
4581 @var{default-value} in their slot descriptor. Also, @code{&optional} | |
4582 and @code{&key} arguments which don't specify defaults take their | |
60927
bae786986f2e
* calc.texi, cl.texi, gnus.texi, idlwave.texi, reftex.texi: Replace
Werner LEMBERG <wl@gnu.org>
parents:
55833
diff
changeset
|
4583 defaults from the slot descriptor. It is valid to include arguments |
25829 | 4584 which don't correspond to slot names; these are useful if they are |
4585 referred to in the defaults for optional, keyword, or @code{&aux} | |
4586 arguments which @emph{do} correspond to slots. | |
4587 | |
4588 You can specify any number of full-format @code{:constructor} | |
4589 options on a structure. The default constructor is still generated | |
4590 as well unless you disable it with a simple-format @code{:constructor} | |
4591 option. | |
4592 | |
4593 @example | |
4594 (defstruct | |
4595 (person | |
4596 (:constructor nil) ; no default constructor | |
4597 (:constructor new-person (name sex &optional (age 0))) | |
4598 (:constructor new-hound (&key (name "Rover") | |
4599 (dog-years 0) | |
4600 &aux (age (* 7 dog-years)) | |
4601 (sex 'canine)))) | |
4602 name age sex) | |
4603 @end example | |
4604 | |
4605 The first constructor here takes its arguments positionally rather | |
4606 than by keyword. (In official Common Lisp terminology, constructors | |
4607 that work By Order of Arguments instead of by keyword are called | |
4608 ``BOA constructors.'' No, I'm not making this up.) For example, | |
4609 @code{(new-person "Jane" 'female)} generates a person whose slots | |
4610 are @code{"Jane"}, 0, and @code{female}, respectively. | |
4611 | |
4612 The second constructor takes two keyword arguments, @code{:name}, | |
4613 which initializes the @code{name} slot and defaults to @code{"Rover"}, | |
4614 and @code{:dog-years}, which does not itself correspond to a slot | |
4615 but which is used to initialize the @code{age} slot. The @code{sex} | |
4616 slot is forced to the symbol @code{canine} with no syntax for | |
4617 overriding it. | |
4618 | |
4619 @item :copier | |
4620 The argument is an alternate name for the copier function for | |
4621 this type. The default is @code{copy-@var{name}}. @code{nil} | |
4622 means not to generate a copier function. (In this implementation, | |
4623 all copier functions are simply synonyms for @code{copy-sequence}.) | |
4624 | |
4625 @item :predicate | |
4626 The argument is an alternate name for the predicate which recognizes | |
4627 objects of this type. The default is @code{@var{name}-p}. @code{nil} | |
4628 means not to generate a predicate function. (If the @code{:type} | |
4629 option is used without the @code{:named} option, no predicate is | |
4630 ever generated.) | |
4631 | |
4632 In true Common Lisp, @code{typep} is always able to recognize a | |
4633 structure object even if @code{:predicate} was used. In this | |
4634 package, @code{typep} simply looks for a function called | |
4635 @code{@var{typename}-p}, so it will work for structure types | |
4636 only if they used the default predicate name. | |
4637 | |
4638 @item :include | |
4639 This option implements a very limited form of C++-style inheritance. | |
4640 The argument is the name of another structure type previously | |
4641 created with @code{defstruct}. The effect is to cause the new | |
4642 structure type to inherit all of the included structure's slots | |
4643 (plus, of course, any new slots described by this struct's slot | |
4644 descriptors). The new structure is considered a ``specialization'' | |
4645 of the included one. In fact, the predicate and slot accessors | |
4646 for the included type will also accept objects of the new type. | |
4647 | |
4648 If there are extra arguments to the @code{:include} option after | |
4649 the included-structure name, these options are treated as replacement | |
4650 slot descriptors for slots in the included structure, possibly with | |
4651 modified default values. Borrowing an example from Steele: | |
4652 | |
4653 @example | |
4654 (defstruct person name (age 0) sex) | |
4655 @result{} person | |
4656 (defstruct (astronaut (:include person (age 45))) | |
4657 helmet-size | |
4658 (favorite-beverage 'tang)) | |
4659 @result{} astronaut | |
4660 | |
4661 (setq joe (make-person :name "Joe")) | |
4662 @result{} [cl-struct-person "Joe" 0 nil] | |
4663 (setq buzz (make-astronaut :name "Buzz")) | |
4664 @result{} [cl-struct-astronaut "Buzz" 45 nil nil tang] | |
4665 | |
4666 (list (person-p joe) (person-p buzz)) | |
4667 @result{} (t t) | |
4668 (list (astronaut-p joe) (astronaut-p buzz)) | |
4669 @result{} (nil t) | |
4670 | |
4671 (person-name buzz) | |
4672 @result{} "Buzz" | |
4673 (astronaut-name joe) | |
4674 @result{} error: "astronaut-name accessing a non-astronaut" | |
4675 @end example | |
4676 | |
4677 Thus, if @code{astronaut} is a specialization of @code{person}, | |
4678 then every @code{astronaut} is also a @code{person} (but not the | |
4679 other way around). Every @code{astronaut} includes all the slots | |
4680 of a @code{person}, plus extra slots that are specific to | |
4681 astronauts. Operations that work on people (like @code{person-name}) | |
4682 work on astronauts just like other people. | |
4683 | |
4684 @item :print-function | |
4685 In full Common Lisp, this option allows you to specify a function | |
4686 which is called to print an instance of the structure type. The | |
4687 Emacs Lisp system offers no hooks into the Lisp printer which would | |
4688 allow for such a feature, so this package simply ignores | |
4689 @code{:print-function}. | |
4690 | |
4691 @item :type | |
4692 The argument should be one of the symbols @code{vector} or @code{list}. | |
4693 This tells which underlying Lisp data type should be used to implement | |
4694 the new structure type. Vectors are used by default, but | |
4695 @code{(:type list)} will cause structure objects to be stored as | |
4696 lists instead. | |
4697 | |
4698 The vector representation for structure objects has the advantage | |
4699 that all structure slots can be accessed quickly, although creating | |
4700 vectors is a bit slower in Emacs Lisp. Lists are easier to create, | |
4701 but take a relatively long time accessing the later slots. | |
4702 | |
4703 @item :named | |
4704 This option, which takes no arguments, causes a characteristic ``tag'' | |
4705 symbol to be stored at the front of the structure object. Using | |
4706 @code{:type} without also using @code{:named} will result in a | |
4707 structure type stored as plain vectors or lists with no identifying | |
4708 features. | |
4709 | |
4710 The default, if you don't specify @code{:type} explicitly, is to | |
4711 use named vectors. Therefore, @code{:named} is only useful in | |
4712 conjunction with @code{:type}. | |
4713 | |
4714 @example | |
4715 (defstruct (person1) name age sex) | |
4716 (defstruct (person2 (:type list) :named) name age sex) | |
4717 (defstruct (person3 (:type list)) name age sex) | |
4718 | |
4719 (setq p1 (make-person1)) | |
4720 @result{} [cl-struct-person1 nil nil nil] | |
4721 (setq p2 (make-person2)) | |
4722 @result{} (person2 nil nil nil) | |
4723 (setq p3 (make-person3)) | |
4724 @result{} (nil nil nil) | |
4725 | |
4726 (person1-p p1) | |
4727 @result{} t | |
4728 (person2-p p2) | |
4729 @result{} t | |
4730 (person3-p p3) | |
4731 @result{} error: function person3-p undefined | |
4732 @end example | |
4733 | |
4734 Since unnamed structures don't have tags, @code{defstruct} is not | |
4735 able to make a useful predicate for recognizing them. Also, | |
4736 accessors like @code{person3-name} will be generated but they | |
4737 will not be able to do any type checking. The @code{person3-name} | |
4738 function, for example, will simply be a synonym for @code{car} in | |
4739 this case. By contrast, @code{person2-name} is able to verify | |
4740 that its argument is indeed a @code{person2} object before | |
4741 proceeding. | |
4742 | |
4743 @item :initial-offset | |
4744 The argument must be a nonnegative integer. It specifies a | |
4745 number of slots to be left ``empty'' at the front of the | |
4746 structure. If the structure is named, the tag appears at the | |
4747 specified position in the list or vector; otherwise, the first | |
4748 slot appears at that position. Earlier positions are filled | |
4749 with @code{nil} by the constructors and ignored otherwise. If | |
4750 the type @code{:include}s another type, then @code{:initial-offset} | |
4751 specifies a number of slots to be skipped between the last slot | |
4752 of the included type and the first new slot. | |
4753 @end table | |
4754 @end defspec | |
4755 | |
4756 Except as noted, the @code{defstruct} facility of this package is | |
4757 entirely compatible with that of Common Lisp. | |
4758 | |
4759 @iftex | |
4760 @chapno=23 | |
4761 @end iftex | |
4762 | |
4763 @node Assertions, Efficiency Concerns, Structures, Top | |
4764 @chapter Assertions and Errors | |
4765 | |
4766 @noindent | |
4767 This section describes two macros that test @dfn{assertions}, i.e., | |
4768 conditions which must be true if the program is operating correctly. | |
4769 Assertions never add to the behavior of a Lisp program; they simply | |
4770 make ``sanity checks'' to make sure everything is as it should be. | |
4771 | |
4772 If the optimization property @code{speed} has been set to 3, and | |
4773 @code{safety} is less than 3, then the byte-compiler will optimize | |
4774 away the following assertions. Because assertions might be optimized | |
4775 away, it is a bad idea for them to include side-effects. | |
4776 | |
4777 @defspec assert test-form [show-args string args@dots{}] | |
4778 This form verifies that @var{test-form} is true (i.e., evaluates to | |
4779 a non-@code{nil} value). If so, it returns @code{nil}. If the test | |
4780 is not satisfied, @code{assert} signals an error. | |
4781 | |
4782 A default error message will be supplied which includes @var{test-form}. | |
4783 You can specify a different error message by including a @var{string} | |
4784 argument plus optional extra arguments. Those arguments are simply | |
4785 passed to @code{error} to signal the error. | |
4786 | |
4787 If the optional second argument @var{show-args} is @code{t} instead | |
4788 of @code{nil}, then the error message (with or without @var{string}) | |
4789 will also include all non-constant arguments of the top-level | |
4790 @var{form}. For example: | |
4791 | |
4792 @example | |
4793 (assert (> x 10) t "x is too small: %d") | |
4794 @end example | |
4795 | |
4796 This usage of @var{show-args} is an extension to Common Lisp. In | |
4797 true Common Lisp, the second argument gives a list of @var{places} | |
4798 which can be @code{setf}'d by the user before continuing from the | |
4799 error. Since Emacs Lisp does not support continuable errors, it | |
4800 makes no sense to specify @var{places}. | |
4801 @end defspec | |
4802 | |
4803 @defspec check-type form type [string] | |
4804 This form verifies that @var{form} evaluates to a value of type | |
4805 @var{type}. If so, it returns @code{nil}. If not, @code{check-type} | |
4806 signals a @code{wrong-type-argument} error. The default error message | |
4807 lists the erroneous value along with @var{type} and @var{form} | |
4808 themselves. If @var{string} is specified, it is included in the | |
4809 error message in place of @var{type}. For example: | |
4810 | |
4811 @example | |
4812 (check-type x (integer 1 *) "a positive integer") | |
4813 @end example | |
4814 | |
4815 @xref{Type Predicates}, for a description of the type specifiers | |
4816 that may be used for @var{type}. | |
4817 | |
4818 Note that in Common Lisp, the first argument to @code{check-type} | |
4819 must be a @var{place} suitable for use by @code{setf}, because | |
4820 @code{check-type} signals a continuable error that allows the | |
4821 user to modify @var{place}. | |
4822 @end defspec | |
4823 | |
4824 The following error-related macro is also defined: | |
4825 | |
4826 @defspec ignore-errors forms@dots{} | |
4827 This executes @var{forms} exactly like a @code{progn}, except that | |
4828 errors are ignored during the @var{forms}. More precisely, if | |
4829 an error is signaled then @code{ignore-errors} immediately | |
4830 aborts execution of the @var{forms} and returns @code{nil}. | |
4831 If the @var{forms} complete successfully, @code{ignore-errors} | |
4832 returns the result of the last @var{form}. | |
4833 @end defspec | |
4834 | |
4835 @node Efficiency Concerns, Common Lisp Compatibility, Assertions, Top | |
4836 @appendix Efficiency Concerns | |
4837 | |
4838 @appendixsec Macros | |
4839 | |
4840 @noindent | |
4841 Many of the advanced features of this package, such as @code{defun*}, | |
4842 @code{loop}, and @code{setf}, are implemented as Lisp macros. In | |
4843 byte-compiled code, these complex notations will be expanded into | |
4844 equivalent Lisp code which is simple and efficient. For example, | |
4845 the forms | |
4846 | |
4847 @example | |
4848 (incf i n) | |
4849 (push x (car p)) | |
4850 @end example | |
4851 | |
4852 @noindent | |
4853 are expanded at compile-time to the Lisp forms | |
4854 | |
4855 @example | |
4856 (setq i (+ i n)) | |
4857 (setcar p (cons x (car p))) | |
4858 @end example | |
4859 | |
4860 @noindent | |
4861 which are the most efficient ways of doing these respective operations | |
4862 in Lisp. Thus, there is no performance penalty for using the more | |
4863 readable @code{incf} and @code{push} forms in your compiled code. | |
4864 | |
4865 @emph{Interpreted} code, on the other hand, must expand these macros | |
4866 every time they are executed. For this reason it is strongly | |
4867 recommended that code making heavy use of macros be compiled. | |
4868 (The features labeled ``Special Form'' instead of ``Function'' in | |
4869 this manual are macros.) A loop using @code{incf} a hundred times | |
4870 will execute considerably faster if compiled, and will also | |
4871 garbage-collect less because the macro expansion will not have | |
4872 to be generated, used, and thrown away a hundred times. | |
4873 | |
4874 You can find out how a macro expands by using the | |
4875 @code{cl-prettyexpand} function. | |
4876 | |
4877 @defun cl-prettyexpand form &optional full | |
4878 This function takes a single Lisp form as an argument and inserts | |
4879 a nicely formatted copy of it in the current buffer (which must be | |
4880 in Lisp mode so that indentation works properly). It also expands | |
4881 all Lisp macros which appear in the form. The easiest way to use | |
4882 this function is to go to the @code{*scratch*} buffer and type, say, | |
4883 | |
4884 @example | |
4885 (cl-prettyexpand '(loop for x below 10 collect x)) | |
4886 @end example | |
4887 | |
4888 @noindent | |
4889 and type @kbd{C-x C-e} immediately after the closing parenthesis; | |
4890 the expansion | |
4891 | |
4892 @example | |
4893 (block nil | |
4894 (let* ((x 0) | |
4895 (G1004 nil)) | |
4896 (while (< x 10) | |
4897 (setq G1004 (cons x G1004)) | |
4898 (setq x (+ x 1))) | |
4899 (nreverse G1004))) | |
4900 @end example | |
4901 | |
4902 @noindent | |
4903 will be inserted into the buffer. (The @code{block} macro is | |
4904 expanded differently in the interpreter and compiler, so | |
4905 @code{cl-prettyexpand} just leaves it alone. The temporary | |
4906 variable @code{G1004} was created by @code{gensym}.) | |
4907 | |
4908 If the optional argument @var{full} is true, then @emph{all} | |
4909 macros are expanded, including @code{block}, @code{eval-when}, | |
4910 and compiler macros. Expansion is done as if @var{form} were | |
4911 a top-level form in a file being compiled. For example, | |
4912 | |
4913 @example | |
4914 (cl-prettyexpand '(pushnew 'x list)) | |
4915 @print{} (setq list (adjoin 'x list)) | |
4916 (cl-prettyexpand '(pushnew 'x list) t) | |
4917 @print{} (setq list (if (memq 'x list) list (cons 'x list))) | |
4918 (cl-prettyexpand '(caddr (member* 'a list)) t) | |
4919 @print{} (car (cdr (cdr (memq 'a list)))) | |
4920 @end example | |
4921 | |
4922 Note that @code{adjoin}, @code{caddr}, and @code{member*} all | |
4923 have built-in compiler macros to optimize them in common cases. | |
4924 @end defun | |
4925 | |
4926 @ifinfo | |
4927 @example | |
4928 | |
4929 @end example | |
4930 @end ifinfo | |
4931 @appendixsec Error Checking | |
4932 | |
4933 @noindent | |
4934 Common Lisp compliance has in general not been sacrificed for the | |
4935 sake of efficiency. A few exceptions have been made for cases | |
4936 where substantial gains were possible at the expense of marginal | |
33295
d66d9f108b83
Remove obsolete warnings about use of memq for keyword args.
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
32315
diff
changeset
|
4937 incompatibility. |
25829 | 4938 |
4939 The Common Lisp standard (as embodied in Steele's book) uses the | |
4940 phrase ``it is an error if'' to indicate a situation which is not | |
4941 supposed to arise in complying programs; implementations are strongly | |
4942 encouraged but not required to signal an error in these situations. | |
4943 This package sometimes omits such error checking in the interest of | |
4944 compactness and efficiency. For example, @code{do} variable | |
4945 specifiers are supposed to be lists of one, two, or three forms; | |
4946 extra forms are ignored by this package rather than signaling a | |
4947 syntax error. The @code{endp} function is simply a synonym for | |
4948 @code{null} in this package. Functions taking keyword arguments | |
4949 will accept an odd number of arguments, treating the trailing | |
4950 keyword as if it were followed by the value @code{nil}. | |
4951 | |
4952 Argument lists (as processed by @code{defun*} and friends) | |
4953 @emph{are} checked rigorously except for the minor point just | |
4954 mentioned; in particular, keyword arguments are checked for | |
4955 validity, and @code{&allow-other-keys} and @code{:allow-other-keys} | |
4956 are fully implemented. Keyword validity checking is slightly | |
4957 time consuming (though not too bad in byte-compiled code); | |
4958 you can use @code{&allow-other-keys} to omit this check. Functions | |
4959 defined in this package such as @code{find} and @code{member*} | |
4960 do check their keyword arguments for validity. | |
4961 | |
4962 @ifinfo | |
4963 @example | |
4964 | |
4965 @end example | |
4966 @end ifinfo | |
4967 @appendixsec Optimizing Compiler | |
4968 | |
4969 @noindent | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
4970 Use of the optimizing Emacs compiler is highly recommended; many of the Common |
27225
ee242fddb1ab
Remove various old stuff and references thereto.
Dave Love <fx@gnu.org>
parents:
25829
diff
changeset
|
4971 Lisp macros emit |
25829 | 4972 code which can be improved by optimization. In particular, |
4973 @code{block}s (whether explicit or implicit in constructs like | |
4974 @code{defun*} and @code{loop}) carry a fair run-time penalty; the | |
4975 optimizing compiler removes @code{block}s which are not actually | |
4976 referenced by @code{return} or @code{return-from} inside the block. | |
4977 | |
4978 @node Common Lisp Compatibility, Old CL Compatibility, Efficiency Concerns, Top | |
4979 @appendix Common Lisp Compatibility | |
4980 | |
4981 @noindent | |
4982 Following is a list of all known incompatibilities between this | |
4983 package and Common Lisp as documented in Steele (2nd edition). | |
4984 | |
4985 Certain function names, such as @code{member}, @code{assoc}, and | |
4986 @code{floor}, were already taken by (incompatible) Emacs Lisp | |
4987 functions; this package appends @samp{*} to the names of its | |
4988 Common Lisp versions of these functions. | |
4989 | |
4990 The word @code{defun*} is required instead of @code{defun} in order | |
4991 to use extended Common Lisp argument lists in a function. Likewise, | |
4992 @code{defmacro*} and @code{function*} are versions of those forms | |
4993 which understand full-featured argument lists. The @code{&whole} | |
4994 keyword does not work in @code{defmacro} argument lists (except | |
4995 inside recursive argument lists). | |
4996 | |
4997 The @code{eql} and @code{equal} predicates do not distinguish | |
4998 between IEEE floating-point plus and minus zero. The @code{equalp} | |
4999 predicate has several differences with Common Lisp; @pxref{Predicates}. | |
5000 | |
5001 The @code{setf} mechanism is entirely compatible, except that | |
5002 setf-methods return a list of five values rather than five | |
5003 values directly. Also, the new ``@code{setf} function'' concept | |
5004 (typified by @code{(defun (setf foo) @dots{})}) is not implemented. | |
5005 | |
5006 The @code{do-all-symbols} form is the same as @code{do-symbols} | |
5007 with no @var{obarray} argument. In Common Lisp, this form would | |
5008 iterate over all symbols in all packages. Since Emacs obarrays | |
5009 are not a first-class package mechanism, there is no way for | |
5010 @code{do-all-symbols} to locate any but the default obarray. | |
5011 | |
5012 The @code{loop} macro is complete except that @code{loop-finish} | |
5013 and type specifiers are unimplemented. | |
5014 | |
5015 The multiple-value return facility treats lists as multiple | |
5016 values, since Emacs Lisp cannot support multiple return values | |
5017 directly. The macros will be compatible with Common Lisp if | |
5018 @code{values} or @code{values-list} is always used to return to | |
5019 a @code{multiple-value-bind} or other multiple-value receiver; | |
5020 if @code{values} is used without @code{multiple-value-@dots{}} | |
5021 or vice-versa the effect will be different from Common Lisp. | |
5022 | |
5023 Many Common Lisp declarations are ignored, and others match | |
5024 the Common Lisp standard in concept but not in detail. For | |
5025 example, local @code{special} declarations, which are purely | |
5026 advisory in Emacs Lisp, do not rigorously obey the scoping rules | |
5027 set down in Steele's book. | |
5028 | |
5029 The variable @code{*gensym-counter*} starts out with a pseudo-random | |
5030 value rather than with zero. This is to cope with the fact that | |
5031 generated symbols become interned when they are written to and | |
5032 loaded back from a file. | |
5033 | |
5034 The @code{defstruct} facility is compatible, except that structures | |
5035 are of type @code{:type vector :named} by default rather than some | |
5036 special, distinct type. Also, the @code{:type} slot option is ignored. | |
5037 | |
5038 The second argument of @code{check-type} is treated differently. | |
5039 | |
5040 @node Old CL Compatibility, Porting Common Lisp, Common Lisp Compatibility, Top | |
5041 @appendix Old CL Compatibility | |
5042 | |
5043 @noindent | |
5044 Following is a list of all known incompatibilities between this package | |
5045 and the older Quiroz @file{cl.el} package. | |
5046 | |
5047 This package's emulation of multiple return values in functions is | |
5048 incompatible with that of the older package. That package attempted | |
5049 to come as close as possible to true Common Lisp multiple return | |
5050 values; unfortunately, it could not be 100% reliable and so was prone | |
5051 to occasional surprises if used freely. This package uses a simpler | |
5052 method, namely replacing multiple values with lists of values, which | |
5053 is more predictable though more noticeably different from Common Lisp. | |
5054 | |
5055 The @code{defkeyword} form and @code{keywordp} function are not | |
5056 implemented in this package. | |
5057 | |
5058 The @code{member}, @code{floor}, @code{ceiling}, @code{truncate}, | |
5059 @code{round}, @code{mod}, and @code{rem} functions are suffixed | |
5060 by @samp{*} in this package to avoid collision with existing | |
27225
ee242fddb1ab
Remove various old stuff and references thereto.
Dave Love <fx@gnu.org>
parents:
25829
diff
changeset
|
5061 functions in Emacs. The older package simply |
25829 | 5062 redefined these functions, overwriting the built-in meanings and |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
5063 causing serious portability problems. (Some more |
25829 | 5064 recent versions of the Quiroz package changed the names to |
5065 @code{cl-member}, etc.; this package defines the latter names as | |
5066 aliases for @code{member*}, etc.) | |
5067 | |
5068 Certain functions in the old package which were buggy or inconsistent | |
5069 with the Common Lisp standard are incompatible with the conforming | |
5070 versions in this package. For example, @code{eql} and @code{member} | |
5071 were synonyms for @code{eq} and @code{memq} in that package, @code{setf} | |
5072 failed to preserve correct order of evaluation of its arguments, etc. | |
5073 | |
5074 Finally, unlike the older package, this package is careful to | |
5075 prefix all of its internal names with @code{cl-}. Except for a | |
5076 few functions which are explicitly defined as additional features | |
5077 (such as @code{floatp-safe} and @code{letf}), this package does not | |
5078 export any non-@samp{cl-} symbols which are not also part of Common | |
5079 Lisp. | |
5080 | |
5081 @ifinfo | |
5082 @example | |
5083 | |
5084 @end example | |
5085 @end ifinfo | |
5086 @appendixsec The @code{cl-compat} package | |
5087 | |
5088 @noindent | |
5089 The @dfn{CL} package includes emulations of some features of the | |
5090 old @file{cl.el}, in the form of a compatibility package | |
5091 @code{cl-compat}. To use it, put @code{(require 'cl-compat)} in | |
5092 your program. | |
5093 | |
5094 The old package defined a number of internal routines without | |
5095 @code{cl-} prefixes or other annotations. Call to these routines | |
5096 may have crept into existing Lisp code. @code{cl-compat} | |
5097 provides emulations of the following internal routines: | |
5098 @code{pair-with-newsyms}, @code{zip-lists}, @code{unzip-lists}, | |
5099 @code{reassemble-arglists}, @code{duplicate-symbols-p}, | |
5100 @code{safe-idiv}. | |
5101 | |
5102 Some @code{setf} forms translated into calls to internal | |
5103 functions that user code might call directly. The functions | |
5104 @code{setnth}, @code{setnthcdr}, and @code{setelt} fall in | |
5105 this category; they are defined by @code{cl-compat}, but the | |
5106 best fix is to change to use @code{setf} properly. | |
5107 | |
5108 The @code{cl-compat} file defines the keyword functions | |
5109 @code{keywordp}, @code{keyword-of}, and @code{defkeyword}, | |
5110 which are not defined by the new @dfn{CL} package because the | |
5111 use of keywords as data is discouraged. | |
5112 | |
5113 The @code{build-klist} mechanism for parsing keyword arguments | |
5114 is emulated by @code{cl-compat}; the @code{with-keyword-args} | |
5115 macro is not, however, and in any case it's best to change to | |
5116 use the more natural keyword argument processing offered by | |
5117 @code{defun*}. | |
5118 | |
5119 Multiple return values are treated differently by the two | |
5120 Common Lisp packages. The old package's method was more | |
5121 compatible with true Common Lisp, though it used heuristics | |
5122 that caused it to report spurious multiple return values in | |
5123 certain cases. The @code{cl-compat} package defines a set | |
5124 of multiple-value macros that are compatible with the old | |
5125 CL package; again, they are heuristic in nature, but they | |
5126 are guaranteed to work in any case where the old package's | |
5127 macros worked. To avoid name collision with the ``official'' | |
5128 multiple-value facilities, the ones in @code{cl-compat} have | |
5129 capitalized names: @code{Values}, @code{Values-list}, | |
5130 @code{Multiple-value-bind}, etc. | |
5131 | |
5132 The functions @code{cl-floor}, @code{cl-ceiling}, @code{cl-truncate}, | |
5133 and @code{cl-round} are defined by @code{cl-compat} to use the | |
5134 old-style multiple-value mechanism, just as they did in the old | |
5135 package. The newer @code{floor*} and friends return their two | |
5136 results in a list rather than as multiple values. Note that | |
5137 older versions of the old package used the unadorned names | |
5138 @code{floor}, @code{ceiling}, etc.; @code{cl-compat} cannot use | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
5139 these names because they conflict with Emacs built-ins. |
25829 | 5140 |
5141 @node Porting Common Lisp, Function Index, Old CL Compatibility, Top | |
5142 @appendix Porting Common Lisp | |
5143 | |
5144 @noindent | |
5145 This package is meant to be used as an extension to Emacs Lisp, | |
5146 not as an Emacs implementation of true Common Lisp. Some of the | |
5147 remaining differences between Emacs Lisp and Common Lisp make it | |
5148 difficult to port large Common Lisp applications to Emacs. For | |
5149 one, some of the features in this package are not fully compliant | |
5150 with ANSI or Steele; @pxref{Common Lisp Compatibility}. But there | |
5151 are also quite a few features that this package does not provide | |
61442
0129c2b09b4a
(Porting Common Lisp): Fix typo.
Thien-Thi Nguyen <ttn@gnuvola.org>
parents:
60927
diff
changeset
|
5152 at all. Here are some major omissions that you will want to watch out |
25829 | 5153 for when bringing Common Lisp code into Emacs. |
5154 | |
5155 @itemize @bullet | |
5156 @item | |
5157 Case-insensitivity. Symbols in Common Lisp are case-insensitive | |
5158 by default. Some programs refer to a function or variable as | |
5159 @code{foo} in one place and @code{Foo} or @code{FOO} in another. | |
5160 Emacs Lisp will treat these as three distinct symbols. | |
5161 | |
5162 Some Common Lisp code is written entirely in upper case. While Emacs | |
5163 is happy to let the program's own functions and variables use | |
5164 this convention, calls to Lisp builtins like @code{if} and | |
5165 @code{defun} will have to be changed to lower case. | |
5166 | |
5167 @item | |
5168 Lexical scoping. In Common Lisp, function arguments and @code{let} | |
5169 bindings apply only to references physically within their bodies | |
5170 (or within macro expansions in their bodies). Emacs Lisp, by | |
5171 contrast, uses @dfn{dynamic scoping} wherein a binding to a | |
5172 variable is visible even inside functions called from the body. | |
5173 | |
5174 Variables in Common Lisp can be made dynamically scoped by | |
5175 declaring them @code{special} or using @code{defvar}. In Emacs | |
5176 Lisp it is as if all variables were declared @code{special}. | |
5177 | |
5178 Often you can use code that was written for lexical scoping | |
5179 even in a dynamically scoped Lisp, but not always. Here is | |
5180 an example of a Common Lisp code fragment that would fail in | |
5181 Emacs Lisp: | |
5182 | |
5183 @example | |
5184 (defun map-odd-elements (func list) | |
5185 (loop for x in list | |
5186 for flag = t then (not flag) | |
5187 collect (if flag x (funcall func x)))) | |
5188 | |
5189 (defun add-odd-elements (list x) | |
28344
54fda0e8528a
Weed out redundant uses of `function'
Stefan Monnier <monnier@iro.umontreal.ca>
parents:
28039
diff
changeset
|
5190 (map-odd-elements (lambda (a) (+ a x))) list) |
25829 | 5191 @end example |
5192 | |
5193 @noindent | |
5194 In Common Lisp, the two functions' usages of @code{x} are completely | |
5195 independent. In Emacs Lisp, the binding to @code{x} made by | |
5196 @code{add-odd-elements} will have been hidden by the binding | |
5197 in @code{map-odd-elements} by the time the @code{(+ a x)} function | |
5198 is called. | |
5199 | |
5200 (This package avoids such problems in its own mapping functions | |
5201 by using names like @code{cl-x} instead of @code{x} internally; | |
5202 as long as you don't use the @code{cl-} prefix for your own | |
5203 variables no collision can occur.) | |
5204 | |
5205 @xref{Lexical Bindings}, for a description of the @code{lexical-let} | |
5206 form which establishes a Common Lisp-style lexical binding, and some | |
5207 examples of how it differs from Emacs' regular @code{let}. | |
5208 | |
5209 @item | |
5210 Reader macros. Common Lisp includes a second type of macro that | |
5211 works at the level of individual characters. For example, Common | |
5212 Lisp implements the quote notation by a reader macro called @code{'}, | |
5213 whereas Emacs Lisp's parser just treats quote as a special case. | |
5214 Some Lisp packages use reader macros to create special syntaxes | |
5215 for themselves, which the Emacs parser is incapable of reading. | |
5216 | |
5217 The lack of reader macros, incidentally, is the reason behind | |
5218 Emacs Lisp's unusual backquote syntax. Since backquotes are | |
5219 implemented as a Lisp package and not built-in to the Emacs | |
5220 parser, they are forced to use a regular macro named @code{`} | |
5221 which is used with the standard function/macro call notation. | |
5222 | |
5223 @item | |
5224 Other syntactic features. Common Lisp provides a number of | |
5225 notations beginning with @code{#} that the Emacs Lisp parser | |
5226 won't understand. For example, @samp{#| ... |#} is an | |
5227 alternate comment notation, and @samp{#+lucid (foo)} tells | |
5228 the parser to ignore the @code{(foo)} except in Lucid Common | |
5229 Lisp. | |
5230 | |
5231 @item | |
5232 Packages. In Common Lisp, symbols are divided into @dfn{packages}. | |
5233 Symbols that are Lisp built-ins are typically stored in one package; | |
5234 symbols that are vendor extensions are put in another, and each | |
5235 application program would have a package for its own symbols. | |
5236 Certain symbols are ``exported'' by a package and others are | |
5237 internal; certain packages ``use'' or import the exported symbols | |
5238 of other packages. To access symbols that would not normally be | |
5239 visible due to this importing and exporting, Common Lisp provides | |
5240 a syntax like @code{package:symbol} or @code{package::symbol}. | |
5241 | |
5242 Emacs Lisp has a single namespace for all interned symbols, and | |
5243 then uses a naming convention of putting a prefix like @code{cl-} | |
5244 in front of the name. Some Emacs packages adopt the Common Lisp-like | |
5245 convention of using @code{cl:} or @code{cl::} as the prefix. | |
5246 However, the Emacs parser does not understand colons and just | |
5247 treats them as part of the symbol name. Thus, while @code{mapcar} | |
5248 and @code{lisp:mapcar} may refer to the same symbol in Common | |
5249 Lisp, they are totally distinct in Emacs Lisp. Common Lisp | |
5250 programs which refer to a symbol by the full name sometimes | |
5251 and the short name other times will not port cleanly to Emacs. | |
5252 | |
5253 Emacs Lisp does have a concept of ``obarrays,'' which are | |
5254 package-like collections of symbols, but this feature is not | |
5255 strong enough to be used as a true package mechanism. | |
5256 | |
5257 @item | |
5258 The @code{format} function is quite different between Common | |
5259 Lisp and Emacs Lisp. It takes an additional ``destination'' | |
5260 argument before the format string. A destination of @code{nil} | |
5261 means to format to a string as in Emacs Lisp; a destination | |
5262 of @code{t} means to write to the terminal (similar to | |
5263 @code{message} in Emacs). Also, format control strings are | |
5264 utterly different; @code{~} is used instead of @code{%} to | |
5265 introduce format codes, and the set of available codes is | |
5266 much richer. There are no notations like @code{\n} for | |
5267 string literals; instead, @code{format} is used with the | |
5268 ``newline'' format code, @code{~%}. More advanced formatting | |
5269 codes provide such features as paragraph filling, case | |
5270 conversion, and even loops and conditionals. | |
5271 | |
5272 While it would have been possible to implement most of Common | |
5273 Lisp @code{format} in this package (under the name @code{format*}, | |
5274 of course), it was not deemed worthwhile. It would have required | |
5275 a huge amount of code to implement even a decent subset of | |
5276 @code{format*}, yet the functionality it would provide over | |
5277 Emacs Lisp's @code{format} would rarely be useful. | |
5278 | |
5279 @item | |
5280 Vector constants use square brackets in Emacs Lisp, but | |
5281 @code{#(a b c)} notation in Common Lisp. To further complicate | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
5282 matters, Emacs has its own @code{#(} notation for |
25829 | 5283 something entirely different---strings with properties. |
5284 | |
5285 @item | |
5286 Characters are distinct from integers in Common Lisp. The | |
5287 notation for character constants is also different: @code{#\A} | |
5288 instead of @code{?A}. Also, @code{string=} and @code{string-equal} | |
5289 are synonyms in Emacs Lisp whereas the latter is case-insensitive | |
5290 in Common Lisp. | |
5291 | |
5292 @item | |
5293 Data types. Some Common Lisp data types do not exist in Emacs | |
5294 Lisp. Rational numbers and complex numbers are not present, | |
5295 nor are large integers (all integers are ``fixnums''). All | |
5296 arrays are one-dimensional. There are no readtables or pathnames; | |
5297 streams are a set of existing data types rather than a new data | |
5298 type of their own. Hash tables, random-states, structures, and | |
5299 packages (obarrays) are built from Lisp vectors or lists rather | |
5300 than being distinct types. | |
5301 | |
5302 @item | |
5303 The Common Lisp Object System (CLOS) is not implemented, | |
5304 nor is the Common Lisp Condition System. However, the EIEIO package | |
5305 from @uref{ftp://ftp.ultranet.com/pub/zappo} does implement some | |
5306 CLOS functionality. | |
5307 | |
5308 @item | |
5309 Common Lisp features that are completely redundant with Emacs | |
5310 Lisp features of a different name generally have not been | |
5311 implemented. For example, Common Lisp writes @code{defconstant} | |
5312 where Emacs Lisp uses @code{defconst}. Similarly, @code{make-list} | |
5313 takes its arguments in different ways in the two Lisps but does | |
5314 exactly the same thing, so this package has not bothered to | |
5315 implement a Common Lisp-style @code{make-list}. | |
5316 | |
5317 @item | |
5318 A few more notable Common Lisp features not included in this | |
5319 package: @code{compiler-let}, @code{tagbody}, @code{prog}, | |
5320 @code{ldb/dpb}, @code{parse-integer}, @code{cerror}. | |
5321 | |
5322 @item | |
5323 Recursion. While recursion works in Emacs Lisp just like it | |
5324 does in Common Lisp, various details of the Emacs Lisp system | |
5325 and compiler make recursion much less efficient than it is in | |
5326 most Lisps. Some schools of thought prefer to use recursion | |
5327 in Lisp over other techniques; they would sum a list of | |
5328 numbers using something like | |
5329 | |
5330 @example | |
5331 (defun sum-list (list) | |
5332 (if list | |
5333 (+ (car list) (sum-list (cdr list))) | |
5334 0)) | |
5335 @end example | |
5336 | |
5337 @noindent | |
5338 where a more iteratively-minded programmer might write one of | |
5339 these forms: | |
5340 | |
5341 @example | |
5342 (let ((total 0)) (dolist (x my-list) (incf total x)) total) | |
5343 (loop for x in my-list sum x) | |
5344 @end example | |
5345 | |
5346 While this would be mainly a stylistic choice in most Common Lisps, | |
5347 in Emacs Lisp you should be aware that the iterative forms are | |
5348 much faster than recursion. Also, Lisp programmers will want to | |
5349 note that the current Emacs Lisp compiler does not optimize tail | |
5350 recursion. | |
5351 @end itemize | |
5352 | |
5353 @node Function Index, Variable Index, Porting Common Lisp, Top | |
5354 @unnumbered Function Index | |
5355 | |
5356 @printindex fn | |
5357 | |
31572
384603523f41
Remove obsolescences, especially hash tables and refs to Emacs 19.
Dave Love <fx@gnu.org>
parents:
30009
diff
changeset
|
5358 @node Variable Index, , Function Index, Top |
25829 | 5359 @unnumbered Variable Index |
5360 | |
5361 @printindex vr | |
5362 | |
29713 | 5363 @setchapternewpage odd |
25829 | 5364 @contents |
5365 @bye | |
52401 | 5366 |
5367 @ignore | |
5368 arch-tag: b61e7200-3bfa-4a70-a9d3-095e152696f8 | |
5369 @end ignore |