Commit | Line | Data |
---|---|---|
2da09c3f MV |
1 | @c -*-texinfo-*- |
2 | @c This is part of the GNU Guile Reference Manual. | |
620c8965 | 3 | @c Copyright (C) 1996, 1997, 2000, 2001, 2002, 2003, 2004, 2006, 2007, 2008, 2009 |
2da09c3f MV |
4 | @c Free Software Foundation, Inc. |
5 | @c See the file guile.texi for copying conditions. | |
6 | ||
a0e07ba4 NJ |
7 | @page |
8 | @node SRFI Support | |
3229f68b | 9 | @section SRFI Support Modules |
8742c48b | 10 | @cindex SRFI |
a0e07ba4 NJ |
11 | |
12 | SRFI is an acronym for Scheme Request For Implementation. The SRFI | |
13 | documents define a lot of syntactic and procedure extensions to standard | |
14 | Scheme as defined in R5RS. | |
15 | ||
16 | Guile has support for a number of SRFIs. This chapter gives an overview | |
17 | over the available SRFIs and some usage hints. For complete | |
18 | documentation, design rationales and further examples, we advise you to | |
19 | get the relevant SRFI documents from the SRFI home page | |
20 | @url{http://srfi.schemers.org}. | |
21 | ||
22 | @menu | |
23 | * About SRFI Usage:: What to know about Guile's SRFI support. | |
24 | * SRFI-0:: cond-expand | |
25 | * SRFI-1:: List library. | |
26 | * SRFI-2:: and-let*. | |
27 | * SRFI-4:: Homogeneous numeric vector datatypes. | |
28 | * SRFI-6:: Basic String Ports. | |
29 | * SRFI-8:: receive. | |
30 | * SRFI-9:: define-record-type. | |
31 | * SRFI-10:: Hash-Comma Reader Extension. | |
c010924a | 32 | * SRFI-11:: let-values and let*-values. |
a0e07ba4 NJ |
33 | * SRFI-13:: String library. |
34 | * SRFI-14:: Character-set library. | |
35 | * SRFI-16:: case-lambda | |
36 | * SRFI-17:: Generalized set! | |
e68f492a | 37 | * SRFI-18:: Multithreading support |
bfc9c8e0 | 38 | * SRFI-19:: Time/Date library. |
1de8c1ae | 39 | * SRFI-26:: Specializing parameters |
620c8965 | 40 | * SRFI-30:: Nested multi-line block comments |
8638c417 | 41 | * SRFI-31:: A special form `rec' for recursive evaluation |
f50ca8da LC |
42 | * SRFI-34:: Exception handling. |
43 | * SRFI-35:: Conditions. | |
d4c38221 | 44 | * SRFI-37:: args-fold program argument processor |
eeadfda1 | 45 | * SRFI-39:: Parameter objects |
4ea9becb | 46 | * SRFI-55:: Requiring Features. |
8503beb8 | 47 | * SRFI-60:: Integers as bits. |
43ed3b69 | 48 | * SRFI-61:: A more general `cond' clause |
1317062f | 49 | * SRFI-69:: Basic hash tables. |
189681f5 | 50 | * SRFI-88:: Keyword objects. |
922d417b | 51 | * SRFI-98:: Accessing environment variables. |
a0e07ba4 NJ |
52 | @end menu |
53 | ||
54 | ||
55 | @node About SRFI Usage | |
3229f68b | 56 | @subsection About SRFI Usage |
a0e07ba4 NJ |
57 | |
58 | @c FIXME::martin: Review me! | |
59 | ||
60 | SRFI support in Guile is currently implemented partly in the core | |
61 | library, and partly as add-on modules. That means that some SRFIs are | |
62 | automatically available when the interpreter is started, whereas the | |
63 | other SRFIs require you to use the appropriate support module | |
12991fed | 64 | explicitly. |
a0e07ba4 NJ |
65 | |
66 | There are several reasons for this inconsistency. First, the feature | |
67 | checking syntactic form @code{cond-expand} (@pxref{SRFI-0}) must be | |
68 | available immediately, because it must be there when the user wants to | |
69 | check for the Scheme implementation, that is, before she can know that | |
70 | it is safe to use @code{use-modules} to load SRFI support modules. The | |
71 | second reason is that some features defined in SRFIs had been | |
72 | implemented in Guile before the developers started to add SRFI | |
73 | implementations as modules (for example SRFI-6 (@pxref{SRFI-6})). In | |
74 | the future, it is possible that SRFIs in the core library might be | |
75 | factored out into separate modules, requiring explicit module loading | |
76 | when they are needed. So you should be prepared to have to use | |
77 | @code{use-modules} someday in the future to access SRFI-6 bindings. If | |
78 | you want, you can do that already. We have included the module | |
79 | @code{(srfi srfi-6)} in the distribution, which currently does nothing, | |
80 | but ensures that you can write future-safe code. | |
81 | ||
82 | Generally, support for a specific SRFI is made available by using | |
83 | modules named @code{(srfi srfi-@var{number})}, where @var{number} is the | |
84 | number of the SRFI needed. Another possibility is to use the command | |
85 | line option @code{--use-srfi}, which will load the necessary modules | |
86 | automatically (@pxref{Invoking Guile}). | |
87 | ||
88 | ||
89 | @node SRFI-0 | |
3229f68b | 90 | @subsection SRFI-0 - cond-expand |
8742c48b | 91 | @cindex SRFI-0 |
a0e07ba4 | 92 | |
5eef0f61 KR |
93 | This SRFI lets a portable Scheme program test for the presence of |
94 | certain features, and adapt itself by using different blocks of code, | |
95 | or fail if the necessary features are not available. There's no | |
96 | module to load, this is in the Guile core. | |
a0e07ba4 | 97 | |
5eef0f61 KR |
98 | A program designed only for Guile will generally not need this |
99 | mechanism, such a program can of course directly use the various | |
100 | documented parts of Guile. | |
a0e07ba4 | 101 | |
5eef0f61 KR |
102 | @deffn syntax cond-expand (feature body@dots{}) @dots{} |
103 | Expand to the @var{body} of the first clause whose @var{feature} | |
104 | specification is satisfied. It is an error if no @var{feature} is | |
a0e07ba4 NJ |
105 | satisfied. |
106 | ||
5eef0f61 KR |
107 | Features are symbols such as @code{srfi-1}, and a feature |
108 | specification can use @code{and}, @code{or} and @code{not} forms to | |
109 | test combinations. The last clause can be an @code{else}, to be used | |
110 | if no other passes. | |
a0e07ba4 | 111 | |
5eef0f61 KR |
112 | For example, define a private version of @code{alist-cons} if SRFI-1 |
113 | is not available. | |
a0e07ba4 | 114 | |
5eef0f61 KR |
115 | @example |
116 | (cond-expand (srfi-1 | |
117 | ) | |
118 | (else | |
119 | (define (alist-cons key val alist) | |
120 | (cons (cons key val) alist)))) | |
121 | @end example | |
a0e07ba4 | 122 | |
5eef0f61 KR |
123 | Or demand a certain set of SRFIs (list operations, string ports, |
124 | @code{receive} and string operations), failing if they're not | |
125 | available. | |
a0e07ba4 | 126 | |
5eef0f61 KR |
127 | @example |
128 | (cond-expand ((and srfi-1 srfi-6 srfi-8 srfi-13) | |
129 | )) | |
130 | @end example | |
131 | @end deffn | |
a0e07ba4 | 132 | |
f38d22c5 KR |
133 | @noindent |
134 | The Guile core has the following features, | |
135 | ||
136 | @example | |
137 | guile | |
60c8ad9e | 138 | guile-2 ;; starting from Guile 2.x |
f38d22c5 KR |
139 | r5rs |
140 | srfi-0 | |
141 | srfi-4 | |
142 | srfi-6 | |
143 | srfi-13 | |
144 | srfi-14 | |
145 | @end example | |
146 | ||
147 | Other SRFI feature symbols are defined once their code has been loaded | |
148 | with @code{use-modules}, since only then are their bindings available. | |
a0e07ba4 | 149 | |
5eef0f61 KR |
150 | The @samp{--use-srfi} command line option (@pxref{Invoking Guile}) is |
151 | a good way to load SRFIs to satisfy @code{cond-expand} when running a | |
152 | portable program. | |
a0e07ba4 | 153 | |
5eef0f61 KR |
154 | Testing the @code{guile} feature allows a program to adapt itself to |
155 | the Guile module system, but still run on other Scheme systems. For | |
156 | example the following demands SRFI-8 (@code{receive}), but also knows | |
157 | how to load it with the Guile mechanism. | |
a0e07ba4 NJ |
158 | |
159 | @example | |
5eef0f61 KR |
160 | (cond-expand (srfi-8 |
161 | ) | |
162 | (guile | |
163 | (use-modules (srfi srfi-8)))) | |
a0e07ba4 NJ |
164 | @end example |
165 | ||
60c8ad9e LC |
166 | @cindex @code{guile-2} SRFI-0 feature |
167 | @cindex portability between 2.0 and older versions | |
168 | Likewise, testing the @code{guile-2} feature allows code to be portable | |
169 | between Guile 2.0 and previous versions of Guile. For instance, it | |
170 | makes it possible to write code that accounts for Guile 2.0's compiler, | |
171 | yet be correctly interpreted on 1.8 and earlier versions: | |
172 | ||
173 | @example | |
174 | (cond-expand (guile-2 (eval-when (compile) | |
175 | ;; This must be evaluated at compile time. | |
176 | (fluid-set! current-reader my-reader))) | |
177 | (guile | |
178 | ;; Earlier versions of Guile do not have a | |
179 | ;; separate compilation phase. | |
180 | (fluid-set! current-reader my-reader))) | |
181 | @end example | |
182 | ||
5eef0f61 KR |
183 | It should be noted that @code{cond-expand} is separate from the |
184 | @code{*features*} mechanism (@pxref{Feature Tracking}), feature | |
185 | symbols in one are unrelated to those in the other. | |
a0e07ba4 NJ |
186 | |
187 | ||
188 | @node SRFI-1 | |
3229f68b | 189 | @subsection SRFI-1 - List library |
8742c48b | 190 | @cindex SRFI-1 |
7c2e18cd | 191 | @cindex list |
a0e07ba4 NJ |
192 | |
193 | @c FIXME::martin: Review me! | |
194 | ||
195 | The list library defined in SRFI-1 contains a lot of useful list | |
196 | processing procedures for construction, examining, destructuring and | |
197 | manipulating lists and pairs. | |
198 | ||
199 | Since SRFI-1 also defines some procedures which are already contained | |
200 | in R5RS and thus are supported by the Guile core library, some list | |
201 | and pair procedures which appear in the SRFI-1 document may not appear | |
202 | in this section. So when looking for a particular list/pair | |
203 | processing procedure, you should also have a look at the sections | |
204 | @ref{Lists} and @ref{Pairs}. | |
205 | ||
206 | @menu | |
207 | * SRFI-1 Constructors:: Constructing new lists. | |
208 | * SRFI-1 Predicates:: Testing list for specific properties. | |
209 | * SRFI-1 Selectors:: Selecting elements from lists. | |
210 | * SRFI-1 Length Append etc:: Length calculation and list appending. | |
211 | * SRFI-1 Fold and Map:: Higher-order list processing. | |
212 | * SRFI-1 Filtering and Partitioning:: Filter lists based on predicates. | |
85a9b4ed | 213 | * SRFI-1 Searching:: Search for elements. |
a0e07ba4 NJ |
214 | * SRFI-1 Deleting:: Delete elements from lists. |
215 | * SRFI-1 Association Lists:: Handle association lists. | |
216 | * SRFI-1 Set Operations:: Use lists for representing sets. | |
217 | @end menu | |
218 | ||
219 | @node SRFI-1 Constructors | |
3229f68b | 220 | @subsubsection Constructors |
7c2e18cd | 221 | @cindex list constructor |
a0e07ba4 NJ |
222 | |
223 | @c FIXME::martin: Review me! | |
224 | ||
225 | New lists can be constructed by calling one of the following | |
226 | procedures. | |
227 | ||
8f85c0c6 | 228 | @deffn {Scheme Procedure} xcons d a |
a0e07ba4 NJ |
229 | Like @code{cons}, but with interchanged arguments. Useful mostly when |
230 | passed to higher-order procedures. | |
231 | @end deffn | |
232 | ||
8f85c0c6 | 233 | @deffn {Scheme Procedure} list-tabulate n init-proc |
a0e07ba4 NJ |
234 | Return an @var{n}-element list, where each list element is produced by |
235 | applying the procedure @var{init-proc} to the corresponding list | |
236 | index. The order in which @var{init-proc} is applied to the indices | |
237 | is not specified. | |
238 | @end deffn | |
239 | ||
57066448 KR |
240 | @deffn {Scheme Procedure} list-copy lst |
241 | Return a new list containing the elements of the list @var{lst}. | |
242 | ||
243 | This function differs from the core @code{list-copy} (@pxref{List | |
244 | Constructors}) in accepting improper lists too. And if @var{lst} is | |
245 | not a pair at all then it's treated as the final tail of an improper | |
246 | list and simply returned. | |
247 | @end deffn | |
248 | ||
8f85c0c6 | 249 | @deffn {Scheme Procedure} circular-list elt1 elt2 @dots{} |
a0e07ba4 NJ |
250 | Return a circular list containing the given arguments @var{elt1} |
251 | @var{elt2} @dots{}. | |
252 | @end deffn | |
253 | ||
8f85c0c6 | 254 | @deffn {Scheme Procedure} iota count [start step] |
256853db KR |
255 | Return a list containing @var{count} numbers, starting from |
256 | @var{start} and adding @var{step} each time. The default @var{start} | |
257 | is 0, the default @var{step} is 1. For example, | |
a0e07ba4 | 258 | |
256853db KR |
259 | @example |
260 | (iota 6) @result{} (0 1 2 3 4 5) | |
261 | (iota 4 2.5 -2) @result{} (2.5 0.5 -1.5 -3.5) | |
262 | @end example | |
a0e07ba4 | 263 | |
256853db KR |
264 | This function takes its name from the corresponding primitive in the |
265 | APL language. | |
a0e07ba4 NJ |
266 | @end deffn |
267 | ||
268 | ||
269 | @node SRFI-1 Predicates | |
3229f68b | 270 | @subsubsection Predicates |
7c2e18cd | 271 | @cindex list predicate |
a0e07ba4 NJ |
272 | |
273 | @c FIXME::martin: Review me! | |
274 | ||
275 | The procedures in this section test specific properties of lists. | |
276 | ||
8f85c0c6 | 277 | @deffn {Scheme Procedure} proper-list? obj |
f18f87aa KR |
278 | Return @code{#t} if @var{obj} is a proper list, or @code{#f} |
279 | otherwise. This is the same as the core @code{list?} (@pxref{List | |
280 | Predicates}). | |
281 | ||
282 | A proper list is a list which ends with the empty list @code{()} in | |
283 | the usual way. The empty list @code{()} itself is a proper list too. | |
284 | ||
285 | @example | |
286 | (proper-list? '(1 2 3)) @result{} #t | |
287 | (proper-list? '()) @result{} #t | |
288 | @end example | |
a0e07ba4 NJ |
289 | @end deffn |
290 | ||
8f85c0c6 | 291 | @deffn {Scheme Procedure} circular-list? obj |
f18f87aa KR |
292 | Return @code{#t} if @var{obj} is a circular list, or @code{#f} |
293 | otherwise. | |
294 | ||
295 | A circular list is a list where at some point the @code{cdr} refers | |
296 | back to a previous pair in the list (either the start or some later | |
297 | point), so that following the @code{cdr}s takes you around in a | |
298 | circle, with no end. | |
299 | ||
300 | @example | |
301 | (define x (list 1 2 3 4)) | |
302 | (set-cdr! (last-pair x) (cddr x)) | |
303 | x @result{} (1 2 3 4 3 4 3 4 ...) | |
304 | (circular-list? x) @result{} #t | |
305 | @end example | |
a0e07ba4 NJ |
306 | @end deffn |
307 | ||
8f85c0c6 | 308 | @deffn {Scheme Procedure} dotted-list? obj |
f18f87aa KR |
309 | Return @code{#t} if @var{obj} is a dotted list, or @code{#f} |
310 | otherwise. | |
311 | ||
312 | A dotted list is a list where the @code{cdr} of the last pair is not | |
313 | the empty list @code{()}. Any non-pair @var{obj} is also considered a | |
314 | dotted list, with length zero. | |
315 | ||
316 | @example | |
317 | (dotted-list? '(1 2 . 3)) @result{} #t | |
318 | (dotted-list? 99) @result{} #t | |
319 | @end example | |
a0e07ba4 NJ |
320 | @end deffn |
321 | ||
f18f87aa KR |
322 | It will be noted that any Scheme object passes exactly one of the |
323 | above three tests @code{proper-list?}, @code{circular-list?} and | |
324 | @code{dotted-list?}. Non-lists are @code{dotted-list?}, finite lists | |
325 | are either @code{proper-list?} or @code{dotted-list?}, and infinite | |
326 | lists are @code{circular-list?}. | |
327 | ||
328 | @sp 1 | |
8f85c0c6 | 329 | @deffn {Scheme Procedure} null-list? lst |
a0e07ba4 NJ |
330 | Return @code{#t} if @var{lst} is the empty list @code{()}, @code{#f} |
331 | otherwise. If something else than a proper or circular list is passed | |
85a9b4ed | 332 | as @var{lst}, an error is signalled. This procedure is recommended |
a0e07ba4 NJ |
333 | for checking for the end of a list in contexts where dotted lists are |
334 | not allowed. | |
335 | @end deffn | |
336 | ||
8f85c0c6 | 337 | @deffn {Scheme Procedure} not-pair? obj |
a0e07ba4 NJ |
338 | Return @code{#t} is @var{obj} is not a pair, @code{#f} otherwise. |
339 | This is shorthand notation @code{(not (pair? @var{obj}))} and is | |
340 | supposed to be used for end-of-list checking in contexts where dotted | |
341 | lists are allowed. | |
342 | @end deffn | |
343 | ||
8f85c0c6 | 344 | @deffn {Scheme Procedure} list= elt= list1 @dots{} |
a0e07ba4 NJ |
345 | Return @code{#t} if all argument lists are equal, @code{#f} otherwise. |
346 | List equality is determined by testing whether all lists have the same | |
347 | length and the corresponding elements are equal in the sense of the | |
348 | equality predicate @var{elt=}. If no or only one list is given, | |
349 | @code{#t} is returned. | |
350 | @end deffn | |
351 | ||
352 | ||
353 | @node SRFI-1 Selectors | |
3229f68b | 354 | @subsubsection Selectors |
7c2e18cd | 355 | @cindex list selector |
a0e07ba4 NJ |
356 | |
357 | @c FIXME::martin: Review me! | |
358 | ||
8f85c0c6 NJ |
359 | @deffn {Scheme Procedure} first pair |
360 | @deffnx {Scheme Procedure} second pair | |
361 | @deffnx {Scheme Procedure} third pair | |
362 | @deffnx {Scheme Procedure} fourth pair | |
363 | @deffnx {Scheme Procedure} fifth pair | |
364 | @deffnx {Scheme Procedure} sixth pair | |
365 | @deffnx {Scheme Procedure} seventh pair | |
366 | @deffnx {Scheme Procedure} eighth pair | |
367 | @deffnx {Scheme Procedure} ninth pair | |
368 | @deffnx {Scheme Procedure} tenth pair | |
a0e07ba4 NJ |
369 | These are synonyms for @code{car}, @code{cadr}, @code{caddr}, @dots{}. |
370 | @end deffn | |
371 | ||
8f85c0c6 | 372 | @deffn {Scheme Procedure} car+cdr pair |
a0e07ba4 NJ |
373 | Return two values, the @sc{car} and the @sc{cdr} of @var{pair}. |
374 | @end deffn | |
375 | ||
8f85c0c6 NJ |
376 | @deffn {Scheme Procedure} take lst i |
377 | @deffnx {Scheme Procedure} take! lst i | |
a0e07ba4 NJ |
378 | Return a list containing the first @var{i} elements of @var{lst}. |
379 | ||
380 | @code{take!} may modify the structure of the argument list @var{lst} | |
381 | in order to produce the result. | |
382 | @end deffn | |
383 | ||
8f85c0c6 | 384 | @deffn {Scheme Procedure} drop lst i |
a0e07ba4 NJ |
385 | Return a list containing all but the first @var{i} elements of |
386 | @var{lst}. | |
387 | @end deffn | |
388 | ||
8f85c0c6 | 389 | @deffn {Scheme Procedure} take-right lst i |
a0e07ba4 | 390 | Return the a list containing the @var{i} last elements of @var{lst}. |
64bf8517 | 391 | The return shares a common tail with @var{lst}. |
a0e07ba4 NJ |
392 | @end deffn |
393 | ||
8f85c0c6 NJ |
394 | @deffn {Scheme Procedure} drop-right lst i |
395 | @deffnx {Scheme Procedure} drop-right! lst i | |
a0e07ba4 NJ |
396 | Return the a list containing all but the @var{i} last elements of |
397 | @var{lst}. | |
398 | ||
64bf8517 KR |
399 | @code{drop-right} always returns a new list, even when @var{i} is |
400 | zero. @code{drop-right!} may modify the structure of the argument | |
401 | list @var{lst} in order to produce the result. | |
a0e07ba4 NJ |
402 | @end deffn |
403 | ||
8f85c0c6 NJ |
404 | @deffn {Scheme Procedure} split-at lst i |
405 | @deffnx {Scheme Procedure} split-at! lst i | |
a0e07ba4 NJ |
406 | Return two values, a list containing the first @var{i} elements of the |
407 | list @var{lst} and a list containing the remaining elements. | |
408 | ||
409 | @code{split-at!} may modify the structure of the argument list | |
410 | @var{lst} in order to produce the result. | |
411 | @end deffn | |
412 | ||
8f85c0c6 | 413 | @deffn {Scheme Procedure} last lst |
a0e07ba4 NJ |
414 | Return the last element of the non-empty, finite list @var{lst}. |
415 | @end deffn | |
416 | ||
417 | ||
418 | @node SRFI-1 Length Append etc | |
3229f68b | 419 | @subsubsection Length, Append, Concatenate, etc. |
a0e07ba4 NJ |
420 | |
421 | @c FIXME::martin: Review me! | |
422 | ||
8f85c0c6 | 423 | @deffn {Scheme Procedure} length+ lst |
a0e07ba4 NJ |
424 | Return the length of the argument list @var{lst}. When @var{lst} is a |
425 | circular list, @code{#f} is returned. | |
426 | @end deffn | |
427 | ||
8f85c0c6 NJ |
428 | @deffn {Scheme Procedure} concatenate list-of-lists |
429 | @deffnx {Scheme Procedure} concatenate! list-of-lists | |
a0e07ba4 NJ |
430 | Construct a list by appending all lists in @var{list-of-lists}. |
431 | ||
432 | @code{concatenate!} may modify the structure of the given lists in | |
433 | order to produce the result. | |
a3e856f2 KR |
434 | |
435 | @code{concatenate} is the same as @code{(apply append | |
436 | @var{list-of-lists})}. It exists because some Scheme implementations | |
437 | have a limit on the number of arguments a function takes, which the | |
438 | @code{apply} might exceed. In Guile there is no such limit. | |
a0e07ba4 NJ |
439 | @end deffn |
440 | ||
8f85c0c6 NJ |
441 | @deffn {Scheme Procedure} append-reverse rev-head tail |
442 | @deffnx {Scheme Procedure} append-reverse! rev-head tail | |
23f2b9a3 KR |
443 | Reverse @var{rev-head}, append @var{tail} to it, and return the |
444 | result. This is equivalent to @code{(append (reverse @var{rev-head}) | |
445 | @var{tail})}, but its implementation is more efficient. | |
446 | ||
447 | @example | |
448 | (append-reverse '(1 2 3) '(4 5 6)) @result{} (3 2 1 4 5 6) | |
449 | @end example | |
a0e07ba4 NJ |
450 | |
451 | @code{append-reverse!} may modify @var{rev-head} in order to produce | |
452 | the result. | |
453 | @end deffn | |
454 | ||
8f85c0c6 | 455 | @deffn {Scheme Procedure} zip lst1 lst2 @dots{} |
a0e07ba4 NJ |
456 | Return a list as long as the shortest of the argument lists, where |
457 | each element is a list. The first list contains the first elements of | |
458 | the argument lists, the second list contains the second elements, and | |
459 | so on. | |
460 | @end deffn | |
461 | ||
8f85c0c6 NJ |
462 | @deffn {Scheme Procedure} unzip1 lst |
463 | @deffnx {Scheme Procedure} unzip2 lst | |
464 | @deffnx {Scheme Procedure} unzip3 lst | |
465 | @deffnx {Scheme Procedure} unzip4 lst | |
466 | @deffnx {Scheme Procedure} unzip5 lst | |
a0e07ba4 NJ |
467 | @code{unzip1} takes a list of lists, and returns a list containing the |
468 | first elements of each list, @code{unzip2} returns two lists, the | |
469 | first containing the first elements of each lists and the second | |
470 | containing the second elements of each lists, and so on. | |
471 | @end deffn | |
472 | ||
e508c863 KR |
473 | @deffn {Scheme Procedure} count pred lst1 @dots{} lstN |
474 | Return a count of the number of times @var{pred} returns true when | |
475 | called on elements from the given lists. | |
476 | ||
477 | @var{pred} is called with @var{N} parameters @code{(@var{pred} | |
478 | @var{elem1} @dots{} @var{elemN})}, each element being from the | |
479 | corresponding @var{lst1} @dots{} @var{lstN}. The first call is with | |
480 | the first element of each list, the second with the second element | |
481 | from each, and so on. | |
482 | ||
483 | Counting stops when the end of the shortest list is reached. At least | |
484 | one list must be non-circular. | |
485 | @end deffn | |
486 | ||
a0e07ba4 NJ |
487 | |
488 | @node SRFI-1 Fold and Map | |
3229f68b | 489 | @subsubsection Fold, Unfold & Map |
7c2e18cd KR |
490 | @cindex list fold |
491 | @cindex list map | |
a0e07ba4 NJ |
492 | |
493 | @c FIXME::martin: Review me! | |
494 | ||
1e181a08 KR |
495 | @deffn {Scheme Procedure} fold proc init lst1 @dots{} lstN |
496 | @deffnx {Scheme Procedure} fold-right proc init lst1 @dots{} lstN | |
497 | Apply @var{proc} to the elements of @var{lst1} @dots{} @var{lstN} to | |
498 | build a result, and return that result. | |
a0e07ba4 | 499 | |
1e181a08 KR |
500 | Each @var{proc} call is @code{(@var{proc} @var{elem1} @dots{} |
501 | @var{elemN} @var{previous})}, where @var{elem1} is from @var{lst1}, | |
502 | through @var{elemN} from @var{lstN}. @var{previous} is the return | |
503 | from the previous call to @var{proc}, or the given @var{init} for the | |
504 | first call. If any list is empty, just @var{init} is returned. | |
a0e07ba4 | 505 | |
1e181a08 KR |
506 | @code{fold} works through the list elements from first to last. The |
507 | following shows a list reversal and the calls it makes, | |
a0e07ba4 | 508 | |
1e181a08 KR |
509 | @example |
510 | (fold cons '() '(1 2 3)) | |
a0e07ba4 | 511 | |
1e181a08 KR |
512 | (cons 1 '()) |
513 | (cons 2 '(1)) | |
514 | (cons 3 '(2 1) | |
515 | @result{} (3 2 1) | |
516 | @end example | |
a0e07ba4 | 517 | |
1e181a08 KR |
518 | @code{fold-right} works through the list elements from last to first, |
519 | ie.@: from the right. So for example the following finds the longest | |
520 | string, and the last among equal longest, | |
521 | ||
522 | @example | |
523 | (fold-right (lambda (str prev) | |
524 | (if (> (string-length str) (string-length prev)) | |
525 | str | |
526 | prev)) | |
527 | "" | |
528 | '("x" "abc" "xyz" "jk")) | |
529 | @result{} "xyz" | |
530 | @end example | |
a0e07ba4 | 531 | |
1e181a08 KR |
532 | If @var{lst1} through @var{lstN} have different lengths, @code{fold} |
533 | stops when the end of the shortest is reached; @code{fold-right} | |
534 | commences at the last element of the shortest. Ie.@: elements past | |
535 | the length of the shortest are ignored in the other @var{lst}s. At | |
536 | least one @var{lst} must be non-circular. | |
537 | ||
538 | @code{fold} should be preferred over @code{fold-right} if the order of | |
539 | processing doesn't matter, or can be arranged either way, since | |
540 | @code{fold} is a little more efficient. | |
541 | ||
542 | The way @code{fold} builds a result from iterating is quite general, | |
543 | it can do more than other iterations like say @code{map} or | |
544 | @code{filter}. The following for example removes adjacent duplicate | |
545 | elements from a list, | |
546 | ||
547 | @example | |
548 | (define (delete-adjacent-duplicates lst) | |
549 | (fold-right (lambda (elem ret) | |
550 | (if (equal? elem (first ret)) | |
551 | ret | |
552 | (cons elem ret))) | |
553 | (list (last lst)) | |
554 | lst)) | |
555 | (delete-adjacent-duplicates '(1 2 3 3 4 4 4 5)) | |
556 | @result{} (1 2 3 4 5) | |
557 | @end example | |
558 | ||
559 | Clearly the same sort of thing can be done with a @code{for-each} and | |
5f708db6 KR |
560 | a variable in which to build the result, but a self-contained |
561 | @var{proc} can be re-used in multiple contexts, where a | |
562 | @code{for-each} would have to be written out each time. | |
a0e07ba4 NJ |
563 | @end deffn |
564 | ||
1e181a08 KR |
565 | @deffn {Scheme Procedure} pair-fold proc init lst1 @dots{} lstN |
566 | @deffnx {Scheme Procedure} pair-fold-right proc init lst1 @dots{} lstN | |
567 | The same as @code{fold} and @code{fold-right}, but apply @var{proc} to | |
568 | the pairs of the lists instead of the list elements. | |
a0e07ba4 NJ |
569 | @end deffn |
570 | ||
5f708db6 KR |
571 | @deffn {Scheme Procedure} reduce proc default lst |
572 | @deffnx {Scheme Procedure} reduce-right proc default lst | |
573 | @code{reduce} is a variant of @code{fold}, where the first call to | |
574 | @var{proc} is on two elements from @var{lst}, rather than one element | |
575 | and a given initial value. | |
1e181a08 | 576 | |
5f708db6 KR |
577 | If @var{lst} is empty, @code{reduce} returns @var{default} (this is |
578 | the only use for @var{default}). If @var{lst} has just one element | |
579 | then that's the return value. Otherwise @var{proc} is called on the | |
580 | elements of @var{lst}. | |
1e181a08 | 581 | |
5f708db6 KR |
582 | Each @var{proc} call is @code{(@var{proc} @var{elem} @var{previous})}, |
583 | where @var{elem} is from @var{lst} (the second and subsequent elements | |
584 | of @var{lst}), and @var{previous} is the return from the previous call | |
585 | to @var{proc}. The first element of @var{lst} is the @var{previous} | |
586 | for the first call to @var{proc}. | |
1e181a08 | 587 | |
5f708db6 KR |
588 | For example, the following adds a list of numbers, the calls made to |
589 | @code{+} are shown. (Of course @code{+} accepts multiple arguments | |
590 | and can add a list directly, with @code{apply}.) | |
1e181a08 KR |
591 | |
592 | @example | |
5f708db6 KR |
593 | (reduce + 0 '(5 6 7)) @result{} 18 |
594 | ||
595 | (+ 6 5) @result{} 11 | |
596 | (+ 7 11) @result{} 18 | |
1e181a08 KR |
597 | @end example |
598 | ||
5f708db6 KR |
599 | @code{reduce} can be used instead of @code{fold} where the @var{init} |
600 | value is an ``identity'', meaning a value which under @var{proc} | |
601 | doesn't change the result, in this case 0 is an identity since | |
602 | @code{(+ 5 0)} is just 5. @code{reduce} avoids that unnecessary call. | |
1e181a08 KR |
603 | |
604 | @code{reduce-right} is a similar variation on @code{fold-right}, | |
5f708db6 KR |
605 | working from the end (ie.@: the right) of @var{lst}. The last element |
606 | of @var{lst} is the @var{previous} for the first call to @var{proc}, | |
607 | and the @var{elem} values go from the second last. | |
1e181a08 KR |
608 | |
609 | @code{reduce} should be preferred over @code{reduce-right} if the | |
610 | order of processing doesn't matter, or can be arranged either way, | |
611 | since @code{reduce} is a little more efficient. | |
a0e07ba4 NJ |
612 | @end deffn |
613 | ||
8f85c0c6 | 614 | @deffn {Scheme Procedure} unfold p f g seed [tail-gen] |
a0e07ba4 NJ |
615 | @code{unfold} is defined as follows: |
616 | ||
617 | @lisp | |
618 | (unfold p f g seed) = | |
619 | (if (p seed) (tail-gen seed) | |
620 | (cons (f seed) | |
621 | (unfold p f g (g seed)))) | |
622 | @end lisp | |
623 | ||
624 | @table @var | |
625 | @item p | |
626 | Determines when to stop unfolding. | |
627 | ||
628 | @item f | |
629 | Maps each seed value to the corresponding list element. | |
630 | ||
631 | @item g | |
632 | Maps each seed value to next seed valu. | |
633 | ||
634 | @item seed | |
635 | The state value for the unfold. | |
636 | ||
637 | @item tail-gen | |
638 | Creates the tail of the list; defaults to @code{(lambda (x) '())}. | |
639 | @end table | |
640 | ||
641 | @var{g} produces a series of seed values, which are mapped to list | |
642 | elements by @var{f}. These elements are put into a list in | |
643 | left-to-right order, and @var{p} tells when to stop unfolding. | |
644 | @end deffn | |
645 | ||
8f85c0c6 | 646 | @deffn {Scheme Procedure} unfold-right p f g seed [tail] |
a0e07ba4 NJ |
647 | Construct a list with the following loop. |
648 | ||
649 | @lisp | |
650 | (let lp ((seed seed) (lis tail)) | |
651 | (if (p seed) lis | |
652 | (lp (g seed) | |
653 | (cons (f seed) lis)))) | |
654 | @end lisp | |
655 | ||
656 | @table @var | |
657 | @item p | |
658 | Determines when to stop unfolding. | |
659 | ||
660 | @item f | |
661 | Maps each seed value to the corresponding list element. | |
662 | ||
663 | @item g | |
664 | Maps each seed value to next seed valu. | |
665 | ||
666 | @item seed | |
667 | The state value for the unfold. | |
668 | ||
669 | @item tail-gen | |
670 | Creates the tail of the list; defaults to @code{(lambda (x) '())}. | |
671 | @end table | |
672 | ||
673 | @end deffn | |
674 | ||
8f85c0c6 | 675 | @deffn {Scheme Procedure} map f lst1 lst2 @dots{} |
a0e07ba4 NJ |
676 | Map the procedure over the list(s) @var{lst1}, @var{lst2}, @dots{} and |
677 | return a list containing the results of the procedure applications. | |
678 | This procedure is extended with respect to R5RS, because the argument | |
679 | lists may have different lengths. The result list will have the same | |
680 | length as the shortest argument lists. The order in which @var{f} | |
681 | will be applied to the list element(s) is not specified. | |
682 | @end deffn | |
683 | ||
8f85c0c6 | 684 | @deffn {Scheme Procedure} for-each f lst1 lst2 @dots{} |
a0e07ba4 NJ |
685 | Apply the procedure @var{f} to each pair of corresponding elements of |
686 | the list(s) @var{lst1}, @var{lst2}, @dots{}. The return value is not | |
687 | specified. This procedure is extended with respect to R5RS, because | |
688 | the argument lists may have different lengths. The shortest argument | |
689 | list determines the number of times @var{f} is called. @var{f} will | |
85a9b4ed | 690 | be applied to the list elements in left-to-right order. |
a0e07ba4 NJ |
691 | |
692 | @end deffn | |
693 | ||
8f85c0c6 NJ |
694 | @deffn {Scheme Procedure} append-map f lst1 lst2 @dots{} |
695 | @deffnx {Scheme Procedure} append-map! f lst1 lst2 @dots{} | |
12991fed | 696 | Equivalent to |
a0e07ba4 NJ |
697 | |
698 | @lisp | |
12991fed | 699 | (apply append (map f clist1 clist2 ...)) |
a0e07ba4 NJ |
700 | @end lisp |
701 | ||
12991fed | 702 | and |
a0e07ba4 NJ |
703 | |
704 | @lisp | |
12991fed | 705 | (apply append! (map f clist1 clist2 ...)) |
a0e07ba4 NJ |
706 | @end lisp |
707 | ||
708 | Map @var{f} over the elements of the lists, just as in the @code{map} | |
709 | function. However, the results of the applications are appended | |
710 | together to make the final result. @code{append-map} uses | |
711 | @code{append} to append the results together; @code{append-map!} uses | |
712 | @code{append!}. | |
713 | ||
714 | The dynamic order in which the various applications of @var{f} are | |
715 | made is not specified. | |
716 | @end deffn | |
717 | ||
8f85c0c6 | 718 | @deffn {Scheme Procedure} map! f lst1 lst2 @dots{} |
a0e07ba4 NJ |
719 | Linear-update variant of @code{map} -- @code{map!} is allowed, but not |
720 | required, to alter the cons cells of @var{lst1} to construct the | |
721 | result list. | |
722 | ||
723 | The dynamic order in which the various applications of @var{f} are | |
724 | made is not specified. In the n-ary case, @var{lst2}, @var{lst3}, | |
725 | @dots{} must have at least as many elements as @var{lst1}. | |
726 | @end deffn | |
727 | ||
8f85c0c6 | 728 | @deffn {Scheme Procedure} pair-for-each f lst1 lst2 @dots{} |
a0e07ba4 NJ |
729 | Like @code{for-each}, but applies the procedure @var{f} to the pairs |
730 | from which the argument lists are constructed, instead of the list | |
731 | elements. The return value is not specified. | |
732 | @end deffn | |
733 | ||
8f85c0c6 | 734 | @deffn {Scheme Procedure} filter-map f lst1 lst2 @dots{} |
a0e07ba4 NJ |
735 | Like @code{map}, but only results from the applications of @var{f} |
736 | which are true are saved in the result list. | |
737 | @end deffn | |
738 | ||
739 | ||
740 | @node SRFI-1 Filtering and Partitioning | |
3229f68b | 741 | @subsubsection Filtering and Partitioning |
7c2e18cd KR |
742 | @cindex list filter |
743 | @cindex list partition | |
a0e07ba4 NJ |
744 | |
745 | @c FIXME::martin: Review me! | |
746 | ||
747 | Filtering means to collect all elements from a list which satisfy a | |
748 | specific condition. Partitioning a list means to make two groups of | |
749 | list elements, one which contains the elements satisfying a condition, | |
750 | and the other for the elements which don't. | |
751 | ||
60e25dc4 KR |
752 | The @code{filter} and @code{filter!} functions are implemented in the |
753 | Guile core, @xref{List Modification}. | |
a0e07ba4 | 754 | |
8f85c0c6 NJ |
755 | @deffn {Scheme Procedure} partition pred lst |
756 | @deffnx {Scheme Procedure} partition! pred lst | |
193239f1 KR |
757 | Split @var{lst} into those elements which do and don't satisfy the |
758 | predicate @var{pred}. | |
a0e07ba4 | 759 | |
193239f1 KR |
760 | The return is two values (@pxref{Multiple Values}), the first being a |
761 | list of all elements from @var{lst} which satisfy @var{pred}, the | |
762 | second a list of those which do not. | |
763 | ||
764 | The elements in the result lists are in the same order as in @var{lst} | |
765 | but the order in which the calls @code{(@var{pred} elem)} are made on | |
766 | the list elements is unspecified. | |
767 | ||
768 | @code{partition} does not change @var{lst}, but one of the returned | |
769 | lists may share a tail with it. @code{partition!} may modify | |
770 | @var{lst} to construct its return. | |
a0e07ba4 NJ |
771 | @end deffn |
772 | ||
8f85c0c6 NJ |
773 | @deffn {Scheme Procedure} remove pred lst |
774 | @deffnx {Scheme Procedure} remove! pred lst | |
a0e07ba4 NJ |
775 | Return a list containing all elements from @var{lst} which do not |
776 | satisfy the predicate @var{pred}. The elements in the result list | |
777 | have the same order as in @var{lst}. The order in which @var{pred} is | |
778 | applied to the list elements is not specified. | |
779 | ||
780 | @code{remove!} is allowed, but not required to modify the structure of | |
781 | the input list. | |
782 | @end deffn | |
783 | ||
784 | ||
785 | @node SRFI-1 Searching | |
3229f68b | 786 | @subsubsection Searching |
7c2e18cd | 787 | @cindex list search |
a0e07ba4 NJ |
788 | |
789 | @c FIXME::martin: Review me! | |
790 | ||
791 | The procedures for searching elements in lists either accept a | |
792 | predicate or a comparison object for determining which elements are to | |
793 | be searched. | |
794 | ||
8f85c0c6 | 795 | @deffn {Scheme Procedure} find pred lst |
a0e07ba4 NJ |
796 | Return the first element of @var{lst} which satisfies the predicate |
797 | @var{pred} and @code{#f} if no such element is found. | |
798 | @end deffn | |
799 | ||
8f85c0c6 | 800 | @deffn {Scheme Procedure} find-tail pred lst |
a0e07ba4 NJ |
801 | Return the first pair of @var{lst} whose @sc{car} satisfies the |
802 | predicate @var{pred} and @code{#f} if no such element is found. | |
803 | @end deffn | |
804 | ||
8f85c0c6 NJ |
805 | @deffn {Scheme Procedure} take-while pred lst |
806 | @deffnx {Scheme Procedure} take-while! pred lst | |
a0e07ba4 NJ |
807 | Return the longest initial prefix of @var{lst} whose elements all |
808 | satisfy the predicate @var{pred}. | |
809 | ||
810 | @code{take-while!} is allowed, but not required to modify the input | |
811 | list while producing the result. | |
812 | @end deffn | |
813 | ||
8f85c0c6 | 814 | @deffn {Scheme Procedure} drop-while pred lst |
a0e07ba4 NJ |
815 | Drop the longest initial prefix of @var{lst} whose elements all |
816 | satisfy the predicate @var{pred}. | |
817 | @end deffn | |
818 | ||
8f85c0c6 NJ |
819 | @deffn {Scheme Procedure} span pred lst |
820 | @deffnx {Scheme Procedure} span! pred lst | |
821 | @deffnx {Scheme Procedure} break pred lst | |
822 | @deffnx {Scheme Procedure} break! pred lst | |
a0e07ba4 NJ |
823 | @code{span} splits the list @var{lst} into the longest initial prefix |
824 | whose elements all satisfy the predicate @var{pred}, and the remaining | |
825 | tail. @code{break} inverts the sense of the predicate. | |
826 | ||
827 | @code{span!} and @code{break!} are allowed, but not required to modify | |
828 | the structure of the input list @var{lst} in order to produce the | |
829 | result. | |
3e73b6f9 KR |
830 | |
831 | Note that the name @code{break} conflicts with the @code{break} | |
832 | binding established by @code{while} (@pxref{while do}). Applications | |
833 | wanting to use @code{break} from within a @code{while} loop will need | |
834 | to make a new define under a different name. | |
a0e07ba4 NJ |
835 | @end deffn |
836 | ||
62705beb KR |
837 | @deffn {Scheme Procedure} any pred lst1 lst2 @dots{} lstN |
838 | Test whether any set of elements from @var{lst1} @dots{} lstN | |
839 | satisfies @var{pred}. If so the return value is the return from the | |
840 | successful @var{pred} call, or if not the return is @code{#f}. | |
841 | ||
842 | Each @var{pred} call is @code{(@var{pred} @var{elem1} @dots{} | |
843 | @var{elemN})} taking an element from each @var{lst}. The calls are | |
844 | made successively for the first, second, etc elements of the lists, | |
845 | stopping when @var{pred} returns non-@code{#f}, or when the end of the | |
846 | shortest list is reached. | |
847 | ||
848 | The @var{pred} call on the last set of elements (ie.@: when the end of | |
849 | the shortest list has been reached), if that point is reached, is a | |
850 | tail call. | |
851 | @end deffn | |
852 | ||
853 | @deffn {Scheme Procedure} every pred lst1 lst2 @dots{} lstN | |
854 | Test whether every set of elements from @var{lst1} @dots{} lstN | |
855 | satisfies @var{pred}. If so the return value is the return from the | |
856 | final @var{pred} call, or if not the return is @code{#f}. | |
857 | ||
858 | Each @var{pred} call is @code{(@var{pred} @var{elem1} @dots{} | |
859 | @var{elemN})} taking an element from each @var{lst}. The calls are | |
860 | made successively for the first, second, etc elements of the lists, | |
861 | stopping if @var{pred} returns @code{#f}, or when the end of any of | |
862 | the lists is reached. | |
863 | ||
864 | The @var{pred} call on the last set of elements (ie.@: when the end of | |
865 | the shortest list has been reached) is a tail call. | |
866 | ||
867 | If one of @var{lst1} @dots{} @var{lstN} is empty then no calls to | |
868 | @var{pred} are made, and the return is @code{#t}. | |
a0e07ba4 NJ |
869 | @end deffn |
870 | ||
0166e7f2 | 871 | @deffn {Scheme Procedure} list-index pred lst1 @dots{} lstN |
d1736abf KR |
872 | Return the index of the first set of elements, one from each of |
873 | @var{lst1}@dots{}@var{lstN}, which satisfies @var{pred}. | |
874 | ||
875 | @var{pred} is called as @code{(@var{pred} elem1 @dots{} elemN)}. | |
876 | Searching stops when the end of the shortest @var{lst} is reached. | |
877 | The return index starts from 0 for the first set of elements. If no | |
878 | set of elements pass then the return is @code{#f}. | |
0166e7f2 KR |
879 | |
880 | @example | |
881 | (list-index odd? '(2 4 6 9)) @result{} 3 | |
882 | (list-index = '(1 2 3) '(3 1 2)) @result{} #f | |
883 | @end example | |
a0e07ba4 NJ |
884 | @end deffn |
885 | ||
8f85c0c6 | 886 | @deffn {Scheme Procedure} member x lst [=] |
a0e07ba4 | 887 | Return the first sublist of @var{lst} whose @sc{car} is equal to |
ca04a5ae | 888 | @var{x}. If @var{x} does not appear in @var{lst}, return @code{#f}. |
ea6ea01b | 889 | |
ca04a5ae KR |
890 | Equality is determined by @code{equal?}, or by the equality predicate |
891 | @var{=} if given. @var{=} is called @code{(= @var{x} elem)}, | |
892 | ie.@: with the given @var{x} first, so for example to find the first | |
893 | element greater than 5, | |
894 | ||
895 | @example | |
896 | (member 5 '(3 5 1 7 2 9) <) @result{} (7 2 9) | |
897 | @end example | |
898 | ||
899 | This version of @code{member} extends the core @code{member} | |
900 | (@pxref{List Searching}) by accepting an equality predicate. | |
a0e07ba4 NJ |
901 | @end deffn |
902 | ||
903 | ||
904 | @node SRFI-1 Deleting | |
3229f68b | 905 | @subsubsection Deleting |
7c2e18cd | 906 | @cindex list delete |
a0e07ba4 | 907 | |
8f85c0c6 NJ |
908 | @deffn {Scheme Procedure} delete x lst [=] |
909 | @deffnx {Scheme Procedure} delete! x lst [=] | |
b6b9376a KR |
910 | Return a list containing the elements of @var{lst} but with those |
911 | equal to @var{x} deleted. The returned elements will be in the same | |
912 | order as they were in @var{lst}. | |
913 | ||
914 | Equality is determined by the @var{=} predicate, or @code{equal?} if | |
915 | not given. An equality call is made just once for each element, but | |
916 | the order in which the calls are made on the elements is unspecified. | |
a0e07ba4 | 917 | |
243bdb63 | 918 | The equality calls are always @code{(= x elem)}, ie.@: the given @var{x} |
b6b9376a KR |
919 | is first. This means for instance elements greater than 5 can be |
920 | deleted with @code{(delete 5 lst <)}. | |
921 | ||
922 | @code{delete} does not modify @var{lst}, but the return might share a | |
923 | common tail with @var{lst}. @code{delete!} may modify the structure | |
924 | of @var{lst} to construct its return. | |
ea6ea01b | 925 | |
4eb21177 KR |
926 | These functions extend the core @code{delete} and @code{delete!} |
927 | (@pxref{List Modification}) in accepting an equality predicate. See | |
928 | also @code{lset-difference} (@pxref{SRFI-1 Set Operations}) for | |
929 | deleting multiple elements from a list. | |
a0e07ba4 NJ |
930 | @end deffn |
931 | ||
8f85c0c6 NJ |
932 | @deffn {Scheme Procedure} delete-duplicates lst [=] |
933 | @deffnx {Scheme Procedure} delete-duplicates! lst [=] | |
b6b9376a KR |
934 | Return a list containing the elements of @var{lst} but without |
935 | duplicates. | |
936 | ||
937 | When elements are equal, only the first in @var{lst} is retained. | |
938 | Equal elements can be anywhere in @var{lst}, they don't have to be | |
939 | adjacent. The returned list will have the retained elements in the | |
940 | same order as they were in @var{lst}. | |
941 | ||
942 | Equality is determined by the @var{=} predicate, or @code{equal?} if | |
943 | not given. Calls @code{(= x y)} are made with element @var{x} being | |
944 | before @var{y} in @var{lst}. A call is made at most once for each | |
945 | combination, but the sequence of the calls across the elements is | |
946 | unspecified. | |
947 | ||
948 | @code{delete-duplicates} does not modify @var{lst}, but the return | |
949 | might share a common tail with @var{lst}. @code{delete-duplicates!} | |
950 | may modify the structure of @var{lst} to construct its return. | |
951 | ||
952 | In the worst case, this is an @math{O(N^2)} algorithm because it must | |
953 | check each element against all those preceding it. For long lists it | |
954 | is more efficient to sort and then compare only adjacent elements. | |
a0e07ba4 NJ |
955 | @end deffn |
956 | ||
957 | ||
958 | @node SRFI-1 Association Lists | |
3229f68b | 959 | @subsubsection Association Lists |
7c2e18cd KR |
960 | @cindex association list |
961 | @cindex alist | |
a0e07ba4 NJ |
962 | |
963 | @c FIXME::martin: Review me! | |
964 | ||
965 | Association lists are described in detail in section @ref{Association | |
966 | Lists}. The present section only documents the additional procedures | |
967 | for dealing with association lists defined by SRFI-1. | |
968 | ||
8f85c0c6 | 969 | @deffn {Scheme Procedure} assoc key alist [=] |
23f2b9a3 KR |
970 | Return the pair from @var{alist} which matches @var{key}. This |
971 | extends the core @code{assoc} (@pxref{Retrieving Alist Entries}) by | |
972 | taking an optional @var{=} comparison procedure. | |
973 | ||
974 | The default comparison is @code{equal?}. If an @var{=} parameter is | |
975 | given it's called @code{(@var{=} @var{key} @var{alistcar})}, ie. the | |
976 | given target @var{key} is the first argument, and a @code{car} from | |
977 | @var{alist} is second. | |
ea6ea01b | 978 | |
23f2b9a3 KR |
979 | For example a case-insensitive string lookup, |
980 | ||
981 | @example | |
982 | (assoc "yy" '(("XX" . 1) ("YY" . 2)) string-ci=?) | |
983 | @result{} ("YY" . 2) | |
984 | @end example | |
a0e07ba4 NJ |
985 | @end deffn |
986 | ||
8f85c0c6 | 987 | @deffn {Scheme Procedure} alist-cons key datum alist |
5e5999f9 KR |
988 | Cons a new association @var{key} and @var{datum} onto @var{alist} and |
989 | return the result. This is equivalent to | |
a0e07ba4 NJ |
990 | |
991 | @lisp | |
992 | (cons (cons @var{key} @var{datum}) @var{alist}) | |
993 | @end lisp | |
994 | ||
5e5999f9 KR |
995 | @code{acons} (@pxref{Adding or Setting Alist Entries}) in the Guile |
996 | core does the same thing. | |
a0e07ba4 NJ |
997 | @end deffn |
998 | ||
8f85c0c6 | 999 | @deffn {Scheme Procedure} alist-copy alist |
a0e07ba4 NJ |
1000 | Return a newly allocated copy of @var{alist}, that means that the |
1001 | spine of the list as well as the pairs are copied. | |
1002 | @end deffn | |
1003 | ||
8f85c0c6 NJ |
1004 | @deffn {Scheme Procedure} alist-delete key alist [=] |
1005 | @deffnx {Scheme Procedure} alist-delete! key alist [=] | |
bd35f1f0 KR |
1006 | Return a list containing the elements of @var{alist} but with those |
1007 | elements whose keys are equal to @var{key} deleted. The returned | |
1008 | elements will be in the same order as they were in @var{alist}. | |
a0e07ba4 | 1009 | |
bd35f1f0 KR |
1010 | Equality is determined by the @var{=} predicate, or @code{equal?} if |
1011 | not given. The order in which elements are tested is unspecified, but | |
1012 | each equality call is made @code{(= key alistkey)}, ie. the given | |
1013 | @var{key} parameter is first and the key from @var{alist} second. | |
1014 | This means for instance all associations with a key greater than 5 can | |
1015 | be removed with @code{(alist-delete 5 alist <)}. | |
1016 | ||
1017 | @code{alist-delete} does not modify @var{alist}, but the return might | |
1018 | share a common tail with @var{alist}. @code{alist-delete!} may modify | |
1019 | the list structure of @var{alist} to construct its return. | |
a0e07ba4 NJ |
1020 | @end deffn |
1021 | ||
1022 | ||
1023 | @node SRFI-1 Set Operations | |
3229f68b | 1024 | @subsubsection Set Operations on Lists |
7c2e18cd | 1025 | @cindex list set operation |
a0e07ba4 | 1026 | |
4eb21177 KR |
1027 | Lists can be used to represent sets of objects. The procedures in |
1028 | this section operate on such lists as sets. | |
1029 | ||
1030 | Note that lists are not an efficient way to implement large sets. The | |
9aa0c3dd | 1031 | procedures here typically take time @math{@var{m}@cross{}@var{n}} when |
4eb21177 KR |
1032 | operating on @var{m} and @var{n} element lists. Other data structures |
1033 | like trees, bitsets (@pxref{Bit Vectors}) or hash tables (@pxref{Hash | |
1034 | Tables}) are faster. | |
1035 | ||
1036 | All these procedures take an equality predicate as the first argument. | |
1037 | This predicate is used for testing the objects in the list sets for | |
1038 | sameness. This predicate must be consistent with @code{eq?} | |
1039 | (@pxref{Equality}) in the sense that if two list elements are | |
1040 | @code{eq?} then they must also be equal under the predicate. This | |
1041 | simply means a given object must be equal to itself. | |
a0e07ba4 | 1042 | |
4eb21177 KR |
1043 | @deffn {Scheme Procedure} lset<= = list1 list2 @dots{} |
1044 | Return @code{#t} if each list is a subset of the one following it. | |
1045 | Ie.@: @var{list1} a subset of @var{list2}, @var{list2} a subset of | |
1046 | @var{list3}, etc, for as many lists as given. If only one list or no | |
1047 | lists are given then the return is @code{#t}. | |
1048 | ||
1049 | A list @var{x} is a subset of @var{y} if each element of @var{x} is | |
1050 | equal to some element in @var{y}. Elements are compared using the | |
1051 | given @var{=} procedure, called as @code{(@var{=} xelem yelem)}. | |
1052 | ||
1053 | @example | |
1054 | (lset<= eq?) @result{} #t | |
1055 | (lset<= eqv? '(1 2 3) '(1)) @result{} #f | |
1056 | (lset<= eqv? '(1 3 2) '(4 3 1 2)) @result{} #t | |
1057 | @end example | |
a0e07ba4 NJ |
1058 | @end deffn |
1059 | ||
8f85c0c6 | 1060 | @deffn {Scheme Procedure} lset= = list1 list2 @dots{} |
4eb21177 KR |
1061 | Return @code{#t} if all argument lists are set-equal. @var{list1} is |
1062 | compared to @var{list2}, @var{list2} to @var{list3}, etc, for as many | |
1063 | lists as given. If only one list or no lists are given then the | |
1064 | return is @code{#t}. | |
1065 | ||
1066 | Two lists @var{x} and @var{y} are set-equal if each element of @var{x} | |
1067 | is equal to some element of @var{y} and conversely each element of | |
1068 | @var{y} is equal to some element of @var{x}. The order of the | |
1069 | elements in the lists doesn't matter. Element equality is determined | |
1070 | with the given @var{=} procedure, called as @code{(@var{=} xelem | |
1071 | yelem)}, but exactly which calls are made is unspecified. | |
1072 | ||
1073 | @example | |
1074 | (lset= eq?) @result{} #t | |
1075 | (lset= eqv? '(1 2 3) '(3 2 1)) @result{} #t | |
1076 | (lset= string-ci=? '("a" "A" "b") '("B" "b" "a")) @result{} #t | |
1077 | @end example | |
a0e07ba4 NJ |
1078 | @end deffn |
1079 | ||
4eb21177 KR |
1080 | @deffn {Scheme Procedure} lset-adjoin = list elem1 @dots{} |
1081 | Add to @var{list} any of the given @var{elem}s not already in the | |
1082 | list. @var{elem}s are @code{cons}ed onto the start of @var{list} (so | |
1083 | the return shares a common tail with @var{list}), but the order | |
1084 | they're added is unspecified. | |
1085 | ||
1086 | The given @var{=} procedure is used for comparing elements, called as | |
1087 | @code{(@var{=} listelem elem)}, ie.@: the second argument is one of | |
1088 | the given @var{elem} parameters. | |
1089 | ||
1090 | @example | |
1091 | (lset-adjoin eqv? '(1 2 3) 4 1 5) @result{} (5 4 1 2 3) | |
1092 | @end example | |
a0e07ba4 NJ |
1093 | @end deffn |
1094 | ||
4eb21177 KR |
1095 | @deffn {Scheme Procedure} lset-union = list1 list2 @dots{} |
1096 | @deffnx {Scheme Procedure} lset-union! = list1 list2 @dots{} | |
1097 | Return the union of the argument list sets. The result is built by | |
1098 | taking the union of @var{list1} and @var{list2}, then the union of | |
1099 | that with @var{list3}, etc, for as many lists as given. For one list | |
1100 | argument that list itself is the result, for no list arguments the | |
1101 | result is the empty list. | |
1102 | ||
1103 | The union of two lists @var{x} and @var{y} is formed as follows. If | |
1104 | @var{x} is empty then the result is @var{y}. Otherwise start with | |
1105 | @var{x} as the result and consider each @var{y} element (from first to | |
1106 | last). A @var{y} element not equal to something already in the result | |
1107 | is @code{cons}ed onto the result. | |
1108 | ||
1109 | The given @var{=} procedure is used for comparing elements, called as | |
1110 | @code{(@var{=} relem yelem)}. The first argument is from the result | |
1111 | accumulated so far, and the second is from the list being union-ed in. | |
1112 | But exactly which calls are made is otherwise unspecified. | |
1113 | ||
1114 | Notice that duplicate elements in @var{list1} (or the first non-empty | |
1115 | list) are preserved, but that repeated elements in subsequent lists | |
1116 | are only added once. | |
1117 | ||
1118 | @example | |
1119 | (lset-union eqv?) @result{} () | |
1120 | (lset-union eqv? '(1 2 3)) @result{} (1 2 3) | |
1121 | (lset-union eqv? '(1 2 1 3) '(2 4 5) '(5)) @result{} (5 4 1 2 1 3) | |
1122 | @end example | |
1123 | ||
1124 | @code{lset-union} doesn't change the given lists but the result may | |
1125 | share a tail with the first non-empty list. @code{lset-union!} can | |
1126 | modify all of the given lists to form the result. | |
a0e07ba4 NJ |
1127 | @end deffn |
1128 | ||
8f85c0c6 NJ |
1129 | @deffn {Scheme Procedure} lset-intersection = list1 list2 @dots{} |
1130 | @deffnx {Scheme Procedure} lset-intersection! = list1 list2 @dots{} | |
4eb21177 KR |
1131 | Return the intersection of @var{list1} with the other argument lists, |
1132 | meaning those elements of @var{list1} which are also in all of | |
1133 | @var{list2} etc. For one list argument, just that list is returned. | |
1134 | ||
1135 | The test for an element of @var{list1} to be in the return is simply | |
1136 | that it's equal to some element in each of @var{list2} etc. Notice | |
1137 | this means an element appearing twice in @var{list1} but only once in | |
1138 | each of @var{list2} etc will go into the return twice. The return has | |
1139 | its elements in the same order as they were in @var{list1}. | |
1140 | ||
1141 | The given @var{=} procedure is used for comparing elements, called as | |
1142 | @code{(@var{=} elem1 elemN)}. The first argument is from @var{list1} | |
1143 | and the second is from one of the subsequent lists. But exactly which | |
1144 | calls are made and in what order is unspecified. | |
1145 | ||
1146 | @example | |
1147 | (lset-intersection eqv? '(x y)) @result{} (x y) | |
1148 | (lset-intersection eqv? '(1 2 3) '(4 3 2)) @result{} (2 3) | |
1149 | (lset-intersection eqv? '(1 1 2 2) '(1 2) '(2 1) '(2)) @result{} (2 2) | |
1150 | @end example | |
1151 | ||
1152 | The return from @code{lset-intersection} may share a tail with | |
1153 | @var{list1}. @code{lset-intersection!} may modify @var{list1} to form | |
1154 | its result. | |
a0e07ba4 NJ |
1155 | @end deffn |
1156 | ||
8f85c0c6 NJ |
1157 | @deffn {Scheme Procedure} lset-difference = list1 list2 @dots{} |
1158 | @deffnx {Scheme Procedure} lset-difference! = list1 list2 @dots{} | |
4eb21177 KR |
1159 | Return @var{list1} with any elements in @var{list2}, @var{list3} etc |
1160 | removed (ie.@: subtracted). For one list argument, just that list is | |
1161 | returned. | |
1162 | ||
1163 | The given @var{=} procedure is used for comparing elements, called as | |
1164 | @code{(@var{=} elem1 elemN)}. The first argument is from @var{list1} | |
1165 | and the second from one of the subsequent lists. But exactly which | |
1166 | calls are made and in what order is unspecified. | |
a0e07ba4 | 1167 | |
4eb21177 KR |
1168 | @example |
1169 | (lset-difference eqv? '(x y)) @result{} (x y) | |
1170 | (lset-difference eqv? '(1 2 3) '(3 1)) @result{} (2) | |
1171 | (lset-difference eqv? '(1 2 3) '(3) '(2)) @result{} (1) | |
1172 | @end example | |
1173 | ||
1174 | The return from @code{lset-difference} may share a tail with | |
1175 | @var{list1}. @code{lset-difference!} may modify @var{list1} to form | |
1176 | its result. | |
a0e07ba4 NJ |
1177 | @end deffn |
1178 | ||
8f85c0c6 NJ |
1179 | @deffn {Scheme Procedure} lset-diff+intersection = list1 list2 @dots{} |
1180 | @deffnx {Scheme Procedure} lset-diff+intersection! = list1 list2 @dots{} | |
4eb21177 KR |
1181 | Return two values (@pxref{Multiple Values}), the difference and |
1182 | intersection of the argument lists as per @code{lset-difference} and | |
1183 | @code{lset-intersection} above. | |
1184 | ||
1185 | For two list arguments this partitions @var{list1} into those elements | |
1186 | of @var{list1} which are in @var{list2} and not in @var{list2}. (But | |
1187 | for more than two arguments there can be elements of @var{list1} which | |
1188 | are neither part of the difference nor the intersection.) | |
1189 | ||
1190 | One of the return values from @code{lset-diff+intersection} may share | |
1191 | a tail with @var{list1}. @code{lset-diff+intersection!} may modify | |
1192 | @var{list1} to form its results. | |
1193 | @end deffn | |
1194 | ||
1195 | @deffn {Scheme Procedure} lset-xor = list1 list2 @dots{} | |
1196 | @deffnx {Scheme Procedure} lset-xor! = list1 list2 @dots{} | |
1197 | Return an XOR of the argument lists. For two lists this means those | |
1198 | elements which are in exactly one of the lists. For more than two | |
1199 | lists it means those elements which appear in an odd number of the | |
1200 | lists. | |
1201 | ||
1202 | To be precise, the XOR of two lists @var{x} and @var{y} is formed by | |
1203 | taking those elements of @var{x} not equal to any element of @var{y}, | |
1204 | plus those elements of @var{y} not equal to any element of @var{x}. | |
1205 | Equality is determined with the given @var{=} procedure, called as | |
1206 | @code{(@var{=} e1 e2)}. One argument is from @var{x} and the other | |
1207 | from @var{y}, but which way around is unspecified. Exactly which | |
1208 | calls are made is also unspecified, as is the order of the elements in | |
1209 | the result. | |
1210 | ||
1211 | @example | |
1212 | (lset-xor eqv? '(x y)) @result{} (x y) | |
1213 | (lset-xor eqv? '(1 2 3) '(4 3 2)) @result{} (4 1) | |
1214 | @end example | |
1215 | ||
1216 | The return from @code{lset-xor} may share a tail with one of the list | |
1217 | arguments. @code{lset-xor!} may modify @var{list1} to form its | |
1218 | result. | |
a0e07ba4 NJ |
1219 | @end deffn |
1220 | ||
1221 | ||
1222 | @node SRFI-2 | |
3229f68b | 1223 | @subsection SRFI-2 - and-let* |
8742c48b | 1224 | @cindex SRFI-2 |
a0e07ba4 | 1225 | |
4fd0db14 KR |
1226 | @noindent |
1227 | The following syntax can be obtained with | |
a0e07ba4 | 1228 | |
4fd0db14 KR |
1229 | @lisp |
1230 | (use-modules (srfi srfi-2)) | |
1231 | @end lisp | |
a0e07ba4 | 1232 | |
4fd0db14 KR |
1233 | @deffn {library syntax} and-let* (clause @dots{}) body @dots{} |
1234 | A combination of @code{and} and @code{let*}. | |
1235 | ||
1236 | Each @var{clause} is evaluated in turn, and if @code{#f} is obtained | |
1237 | then evaluation stops and @code{#f} is returned. If all are | |
1238 | non-@code{#f} then @var{body} is evaluated and the last form gives the | |
6b1a6e4c KR |
1239 | return value, or if @var{body} is empty then the result is @code{#t}. |
1240 | Each @var{clause} should be one of the following, | |
4fd0db14 KR |
1241 | |
1242 | @table @code | |
1243 | @item (symbol expr) | |
1244 | Evaluate @var{expr}, check for @code{#f}, and bind it to @var{symbol}. | |
1245 | Like @code{let*}, that binding is available to subsequent clauses. | |
1246 | @item (expr) | |
1247 | Evaluate @var{expr} and check for @code{#f}. | |
1248 | @item symbol | |
1249 | Get the value bound to @var{symbol} and check for @code{#f}. | |
1250 | @end table | |
a0e07ba4 | 1251 | |
4fd0db14 KR |
1252 | Notice that @code{(expr)} has an ``extra'' pair of parentheses, for |
1253 | instance @code{((eq? x y))}. One way to remember this is to imagine | |
1254 | the @code{symbol} in @code{(symbol expr)} is omitted. | |
a0e07ba4 | 1255 | |
4fd0db14 KR |
1256 | @code{and-let*} is good for calculations where a @code{#f} value means |
1257 | termination, but where a non-@code{#f} value is going to be needed in | |
1258 | subsequent expressions. | |
1259 | ||
1260 | The following illustrates this, it returns text between brackets | |
1261 | @samp{[...]} in a string, or @code{#f} if there are no such brackets | |
1262 | (ie.@: either @code{string-index} gives @code{#f}). | |
1263 | ||
1264 | @example | |
1265 | (define (extract-brackets str) | |
1266 | (and-let* ((start (string-index str #\[)) | |
1267 | (end (string-index str #\] start))) | |
1268 | (substring str (1+ start) end))) | |
1269 | @end example | |
1270 | ||
1271 | The following shows plain variables and expressions tested too. | |
1272 | @code{diagnostic-levels} is taken to be an alist associating a | |
1273 | diagnostic type with a level. @code{str} is printed only if the type | |
1274 | is known and its level is high enough. | |
1275 | ||
1276 | @example | |
1277 | (define (show-diagnostic type str) | |
1278 | (and-let* (want-diagnostics | |
1279 | (level (assq-ref diagnostic-levels type)) | |
1280 | ((>= level current-diagnostic-level))) | |
1281 | (display str))) | |
1282 | @end example | |
1283 | ||
1284 | The advantage of @code{and-let*} is that an extended sequence of | |
1285 | expressions and tests doesn't require lots of nesting as would arise | |
1286 | from separate @code{and} and @code{let*}, or from @code{cond} with | |
1287 | @code{=>}. | |
1288 | ||
1289 | @end deffn | |
a0e07ba4 NJ |
1290 | |
1291 | ||
1292 | @node SRFI-4 | |
3229f68b | 1293 | @subsection SRFI-4 - Homogeneous numeric vector datatypes |
8742c48b | 1294 | @cindex SRFI-4 |
a0e07ba4 | 1295 | |
e6b226b9 | 1296 | The SRFI-4 procedures and data types are always available, @xref{Uniform |
3dd6e0cf | 1297 | Numeric Vectors}. |
a0e07ba4 NJ |
1298 | |
1299 | @node SRFI-6 | |
3229f68b | 1300 | @subsection SRFI-6 - Basic String Ports |
8742c48b | 1301 | @cindex SRFI-6 |
a0e07ba4 NJ |
1302 | |
1303 | SRFI-6 defines the procedures @code{open-input-string}, | |
1304 | @code{open-output-string} and @code{get-output-string}. These | |
1305 | procedures are included in the Guile core, so using this module does not | |
1306 | make any difference at the moment. But it is possible that support for | |
1307 | SRFI-6 will be factored out of the core library in the future, so using | |
1308 | this module does not hurt, after all. | |
1309 | ||
1310 | @node SRFI-8 | |
3229f68b | 1311 | @subsection SRFI-8 - receive |
8742c48b | 1312 | @cindex SRFI-8 |
a0e07ba4 NJ |
1313 | |
1314 | @code{receive} is a syntax for making the handling of multiple-value | |
1315 | procedures easier. It is documented in @xref{Multiple Values}. | |
1316 | ||
1317 | ||
1318 | @node SRFI-9 | |
3229f68b | 1319 | @subsection SRFI-9 - define-record-type |
8742c48b | 1320 | @cindex SRFI-9 |
7c2e18cd | 1321 | @cindex record |
a0e07ba4 | 1322 | |
6afe385d KR |
1323 | This SRFI is a syntax for defining new record types and creating |
1324 | predicate, constructor, and field getter and setter functions. In | |
1325 | Guile this is simply an alternate interface to the core record | |
1326 | functionality (@pxref{Records}). It can be used with, | |
a0e07ba4 | 1327 | |
6afe385d KR |
1328 | @example |
1329 | (use-modules (srfi srfi-9)) | |
1330 | @end example | |
1331 | ||
1332 | @deffn {library syntax} define-record-type type @* (constructor fieldname @dots{}) @* predicate @* (fieldname accessor [modifier]) @dots{} | |
1333 | @sp 1 | |
1334 | Create a new record type, and make various @code{define}s for using | |
1335 | it. This syntax can only occur at the top-level, not nested within | |
1336 | some other form. | |
1337 | ||
1338 | @var{type} is bound to the record type, which is as per the return | |
1339 | from the core @code{make-record-type}. @var{type} also provides the | |
1340 | name for the record, as per @code{record-type-name}. | |
1341 | ||
1342 | @var{constructor} is bound to a function to be called as | |
1343 | @code{(@var{constructor} fieldval @dots{})} to create a new record of | |
1344 | this type. The arguments are initial values for the fields, one | |
1345 | argument for each field, in the order they appear in the | |
1346 | @code{define-record-type} form. | |
1347 | ||
1348 | The @var{fieldname}s provide the names for the record fields, as per | |
1349 | the core @code{record-type-fields} etc, and are referred to in the | |
1350 | subsequent accessor/modifier forms. | |
1351 | ||
1352 | @var{predictate} is bound to a function to be called as | |
1353 | @code{(@var{predicate} obj)}. It returns @code{#t} or @code{#f} | |
1354 | according to whether @var{obj} is a record of this type. | |
1355 | ||
1356 | Each @var{accessor} is bound to a function to be called | |
1357 | @code{(@var{accessor} record)} to retrieve the respective field from a | |
1358 | @var{record}. Similarly each @var{modifier} is bound to a function to | |
1359 | be called @code{(@var{modifier} record val)} to set the respective | |
1360 | field in a @var{record}. | |
1361 | @end deffn | |
1362 | ||
1363 | @noindent | |
1364 | An example will illustrate typical usage, | |
a0e07ba4 NJ |
1365 | |
1366 | @example | |
6afe385d KR |
1367 | (define-record-type employee-type |
1368 | (make-employee name age salary) | |
1369 | employee? | |
1370 | (name get-employee-name) | |
1371 | (age get-employee-age set-employee-age) | |
1372 | (salary get-employee-salary set-employee-salary)) | |
a0e07ba4 NJ |
1373 | @end example |
1374 | ||
6afe385d KR |
1375 | This creates a new employee data type, with name, age and salary |
1376 | fields. Accessor functions are created for each field, but no | |
1377 | modifier function for the name (the intention in this example being | |
1378 | that it's established only when an employee object is created). These | |
1379 | can all then be used as for example, | |
a0e07ba4 NJ |
1380 | |
1381 | @example | |
6afe385d KR |
1382 | employee-type @result{} #<record-type employee-type> |
1383 | ||
1384 | (define fred (make-employee "Fred" 45 20000.00)) | |
1385 | ||
1386 | (employee? fred) @result{} #t | |
1387 | (get-employee-age fred) @result{} 45 | |
1388 | (set-employee-salary fred 25000.00) ;; pay rise | |
a0e07ba4 NJ |
1389 | @end example |
1390 | ||
6afe385d KR |
1391 | The functions created by @code{define-record-type} are ordinary |
1392 | top-level @code{define}s. They can be redefined or @code{set!} as | |
1393 | desired, exported from a module, etc. | |
1394 | ||
a0e07ba4 NJ |
1395 | |
1396 | @node SRFI-10 | |
3229f68b | 1397 | @subsection SRFI-10 - Hash-Comma Reader Extension |
8742c48b | 1398 | @cindex SRFI-10 |
a0e07ba4 NJ |
1399 | |
1400 | @cindex hash-comma | |
1401 | @cindex #,() | |
633acbe2 KR |
1402 | This SRFI implements a reader extension @code{#,()} called hash-comma. |
1403 | It allows the reader to give new kinds of objects, for use both in | |
1404 | data and as constants or literals in source code. This feature is | |
1405 | available with | |
a0e07ba4 | 1406 | |
633acbe2 KR |
1407 | @example |
1408 | (use-modules (srfi srfi-10)) | |
1409 | @end example | |
1410 | ||
1411 | @noindent | |
1412 | The new read syntax is of the form | |
a0e07ba4 NJ |
1413 | |
1414 | @example | |
633acbe2 | 1415 | #,(@var{tag} @var{arg}@dots{}) |
a0e07ba4 NJ |
1416 | @end example |
1417 | ||
633acbe2 KR |
1418 | @noindent |
1419 | where @var{tag} is a symbol and the @var{arg}s are objects taken as | |
1420 | parameters. @var{tag}s are registered with the following procedure. | |
a0e07ba4 | 1421 | |
633acbe2 KR |
1422 | @deffn {Scheme Procedure} define-reader-ctor tag proc |
1423 | Register @var{proc} as the constructor for a hash-comma read syntax | |
1424 | starting with symbol @var{tag}, ie. @nicode{#,(@var{tag} arg@dots{})}. | |
1425 | @var{proc} is called with the given arguments @code{(@var{proc} | |
1426 | arg@dots{})} and the object it returns is the result of the read. | |
1427 | @end deffn | |
a0e07ba4 | 1428 | |
633acbe2 KR |
1429 | @noindent |
1430 | For example, a syntax giving a list of @var{N} copies of an object. | |
1431 | ||
1432 | @example | |
1433 | (define-reader-ctor 'repeat | |
1434 | (lambda (obj reps) | |
1435 | (make-list reps obj))) | |
1436 | ||
1437 | (display '#,(repeat 99 3)) | |
1438 | @print{} (99 99 99) | |
1439 | @end example | |
1440 | ||
1441 | Notice the quote @nicode{'} when the @nicode{#,( )} is used. The | |
1442 | @code{repeat} handler returns a list and the program must quote to use | |
1443 | it literally, the same as any other list. Ie. | |
1444 | ||
1445 | @example | |
1446 | (display '#,(repeat 99 3)) | |
a0e07ba4 | 1447 | @result{} |
633acbe2 KR |
1448 | (display '(99 99 99)) |
1449 | @end example | |
a0e07ba4 | 1450 | |
633acbe2 KR |
1451 | When a handler returns an object which is self-evaluating, like a |
1452 | number or a string, then there's no need for quoting, just as there's | |
1453 | no need when giving those directly as literals. For example an | |
1454 | addition, | |
a0e07ba4 | 1455 | |
633acbe2 KR |
1456 | @example |
1457 | (define-reader-ctor 'sum | |
1458 | (lambda (x y) | |
1459 | (+ x y))) | |
1460 | (display #,(sum 123 456)) @print{} 579 | |
1461 | @end example | |
1462 | ||
1463 | A typical use for @nicode{#,()} is to get a read syntax for objects | |
1464 | which don't otherwise have one. For example, the following allows a | |
1465 | hash table to be given literally, with tags and values, ready for fast | |
1466 | lookup. | |
1467 | ||
1468 | @example | |
1469 | (define-reader-ctor 'hash | |
1470 | (lambda elems | |
1471 | (let ((table (make-hash-table))) | |
1472 | (for-each (lambda (elem) | |
01549abb KR |
1473 | (apply hash-set! table elem)) |
1474 | elems) | |
633acbe2 KR |
1475 | table))) |
1476 | ||
1477 | (define (animal->family animal) | |
1478 | (hash-ref '#,(hash ("tiger" "cat") | |
1479 | ("lion" "cat") | |
1480 | ("wolf" "dog")) | |
1481 | animal)) | |
1482 | ||
1483 | (animal->family "lion") @result{} "cat" | |
1484 | @end example | |
1485 | ||
1486 | Or for example the following is a syntax for a compiled regular | |
1487 | expression (@pxref{Regular Expressions}). | |
1488 | ||
1489 | @example | |
1490 | (use-modules (ice-9 regex)) | |
1491 | ||
1492 | (define-reader-ctor 'regexp make-regexp) | |
1493 | ||
1494 | (define (extract-angs str) | |
1495 | (let ((match (regexp-exec '#,(regexp "<([A-Z0-9]+)>") str))) | |
1496 | (and match | |
1497 | (match:substring match 1)))) | |
1498 | ||
1499 | (extract-angs "foo <BAR> quux") @result{} "BAR" | |
1500 | @end example | |
1501 | ||
1502 | @sp 1 | |
1503 | @nicode{#,()} is somewhat similar to @code{define-macro} | |
1504 | (@pxref{Macros}) in that handler code is run to produce a result, but | |
1505 | @nicode{#,()} operates at the read stage, so it can appear in data for | |
1506 | @code{read} (@pxref{Scheme Read}), not just in code to be executed. | |
1507 | ||
1508 | Because @nicode{#,()} is handled at read-time it has no direct access | |
1509 | to variables etc. A symbol in the arguments is just a symbol, not a | |
1510 | variable reference. The arguments are essentially constants, though | |
1511 | the handler procedure can use them in any complicated way it might | |
1512 | want. | |
1513 | ||
1514 | Once @code{(srfi srfi-10)} has loaded, @nicode{#,()} is available | |
1515 | globally, there's no need to use @code{(srfi srfi-10)} in later | |
1516 | modules. Similarly the tags registered are global and can be used | |
1517 | anywhere once registered. | |
1518 | ||
1519 | There's no attempt to record what previous @nicode{#,()} forms have | |
1520 | been seen, if two identical forms occur then two calls are made to the | |
1521 | handler procedure. The handler might like to maintain a cache or | |
1522 | similar to avoid making copies of large objects, depending on expected | |
1523 | usage. | |
1524 | ||
1525 | In code the best uses of @nicode{#,()} are generally when there's a | |
1526 | lot of objects of a particular kind as literals or constants. If | |
1527 | there's just a few then some local variables and initializers are | |
1528 | fine, but that becomes tedious and error prone when there's a lot, and | |
1529 | the anonymous and compact syntax of @nicode{#,()} is much better. | |
a0e07ba4 NJ |
1530 | |
1531 | ||
1532 | @node SRFI-11 | |
3229f68b | 1533 | @subsection SRFI-11 - let-values |
8742c48b | 1534 | @cindex SRFI-11 |
a0e07ba4 | 1535 | |
8742c48b | 1536 | @findex let-values |
c010924a | 1537 | @findex let*-values |
a0e07ba4 | 1538 | This module implements the binding forms for multiple values |
c010924a | 1539 | @code{let-values} and @code{let*-values}. These forms are similar to |
a0e07ba4 NJ |
1540 | @code{let} and @code{let*} (@pxref{Local Bindings}), but they support |
1541 | binding of the values returned by multiple-valued expressions. | |
1542 | ||
1543 | Write @code{(use-modules (srfi srfi-11))} to make the bindings | |
1544 | available. | |
1545 | ||
1546 | @lisp | |
1547 | (let-values (((x y) (values 1 2)) | |
1548 | ((z f) (values 3 4))) | |
1549 | (+ x y z f)) | |
1550 | @result{} | |
1551 | 10 | |
1552 | @end lisp | |
1553 | ||
1554 | @code{let-values} performs all bindings simultaneously, which means that | |
1555 | no expression in the binding clauses may refer to variables bound in the | |
c010924a | 1556 | same clause list. @code{let*-values}, on the other hand, performs the |
a0e07ba4 NJ |
1557 | bindings sequentially, just like @code{let*} does for single-valued |
1558 | expressions. | |
1559 | ||
1560 | ||
1561 | @node SRFI-13 | |
3229f68b | 1562 | @subsection SRFI-13 - String Library |
8742c48b | 1563 | @cindex SRFI-13 |
a0e07ba4 | 1564 | |
5676b4fa | 1565 | The SRFI-13 procedures are always available, @xref{Strings}. |
a0e07ba4 NJ |
1566 | |
1567 | @node SRFI-14 | |
3229f68b | 1568 | @subsection SRFI-14 - Character-set Library |
8742c48b | 1569 | @cindex SRFI-14 |
a0e07ba4 | 1570 | |
050ab45f MV |
1571 | The SRFI-14 data type and procedures are always available, |
1572 | @xref{Character Sets}. | |
a0e07ba4 NJ |
1573 | |
1574 | @node SRFI-16 | |
3229f68b | 1575 | @subsection SRFI-16 - case-lambda |
8742c48b | 1576 | @cindex SRFI-16 |
7c2e18cd KR |
1577 | @cindex variable arity |
1578 | @cindex arity, variable | |
a0e07ba4 | 1579 | |
f916cbc4 AW |
1580 | SRFI-16 defines a variable-arity @code{lambda} form, |
1581 | @code{case-lambda}. This form is available in the default Guile | |
1582 | environment. @xref{Case-lambda}, for more information. | |
a0e07ba4 NJ |
1583 | |
1584 | @node SRFI-17 | |
3229f68b | 1585 | @subsection SRFI-17 - Generalized set! |
8742c48b | 1586 | @cindex SRFI-17 |
a0e07ba4 | 1587 | |
9a18d8d4 KR |
1588 | This SRFI implements a generalized @code{set!}, allowing some |
1589 | ``referencing'' functions to be used as the target location of a | |
1590 | @code{set!}. This feature is available from | |
1591 | ||
1592 | @example | |
1593 | (use-modules (srfi srfi-17)) | |
1594 | @end example | |
1595 | ||
1596 | @noindent | |
1597 | For example @code{vector-ref} is extended so that | |
1598 | ||
1599 | @example | |
1600 | (set! (vector-ref vec idx) new-value) | |
1601 | @end example | |
1602 | ||
1603 | @noindent | |
1604 | is equivalent to | |
1605 | ||
1606 | @example | |
1607 | (vector-set! vec idx new-value) | |
1608 | @end example | |
1609 | ||
1610 | The idea is that a @code{vector-ref} expression identifies a location, | |
1611 | which may be either fetched or stored. The same form is used for the | |
1612 | location in both cases, encouraging visual clarity. This is similar | |
1613 | to the idea of an ``lvalue'' in C. | |
1614 | ||
1615 | The mechanism for this kind of @code{set!} is in the Guile core | |
1616 | (@pxref{Procedures with Setters}). This module adds definitions of | |
1617 | the following functions as procedures with setters, allowing them to | |
1618 | be targets of a @code{set!}, | |
1619 | ||
1620 | @quotation | |
1621 | @nicode{car}, @nicode{cdr}, @nicode{caar}, @nicode{cadr}, | |
1622 | @nicode{cdar}, @nicode{cddr}, @nicode{caaar}, @nicode{caadr}, | |
1623 | @nicode{cadar}, @nicode{caddr}, @nicode{cdaar}, @nicode{cdadr}, | |
1624 | @nicode{cddar}, @nicode{cdddr}, @nicode{caaaar}, @nicode{caaadr}, | |
1625 | @nicode{caadar}, @nicode{caaddr}, @nicode{cadaar}, @nicode{cadadr}, | |
1626 | @nicode{caddar}, @nicode{cadddr}, @nicode{cdaaar}, @nicode{cdaadr}, | |
1627 | @nicode{cdadar}, @nicode{cdaddr}, @nicode{cddaar}, @nicode{cddadr}, | |
1628 | @nicode{cdddar}, @nicode{cddddr} | |
1629 | ||
1630 | @nicode{string-ref}, @nicode{vector-ref} | |
1631 | @end quotation | |
1632 | ||
1633 | The SRFI specifies @code{setter} (@pxref{Procedures with Setters}) as | |
1634 | a procedure with setter, allowing the setter for a procedure to be | |
1635 | changed, eg.@: @code{(set! (setter foo) my-new-setter-handler)}. | |
1636 | Currently Guile does not implement this, a setter can only be | |
1637 | specified on creation (@code{getter-with-setter} below). | |
1638 | ||
1639 | @defun getter-with-setter | |
1640 | The same as the Guile core @code{make-procedure-with-setter} | |
1641 | (@pxref{Procedures with Setters}). | |
1642 | @end defun | |
a0e07ba4 | 1643 | |
12991fed | 1644 | |
e68f492a JG |
1645 | @node SRFI-18 |
1646 | @subsection SRFI-18 - Multithreading support | |
1647 | @cindex SRFI-18 | |
1648 | ||
1649 | This is an implementation of the SRFI-18 threading and synchronization | |
1650 | library. The functions and variables described here are provided by | |
1651 | ||
1652 | @example | |
1653 | (use-modules (srfi srfi-18)) | |
1654 | @end example | |
1655 | ||
1656 | As a general rule, the data types and functions in this SRFI-18 | |
1657 | implementation are compatible with the types and functions in Guile's | |
1658 | core threading code. For example, mutexes created with the SRFI-18 | |
1659 | @code{make-mutex} function can be passed to the built-in Guile | |
1660 | function @code{lock-mutex} (@pxref{Mutexes and Condition Variables}), | |
1661 | and mutexes created with the built-in Guile function @code{make-mutex} | |
1662 | can be passed to the SRFI-18 function @code{mutex-lock!}. Cases in | |
1663 | which this does not hold true are noted in the following sections. | |
1664 | ||
1665 | @menu | |
1666 | * SRFI-18 Threads:: Executing code | |
1667 | * SRFI-18 Mutexes:: Mutual exclusion devices | |
1668 | * SRFI-18 Condition variables:: Synchronizing of groups of threads | |
1669 | * SRFI-18 Time:: Representation of times and durations | |
1670 | * SRFI-18 Exceptions:: Signalling and handling errors | |
1671 | @end menu | |
1672 | ||
1673 | @node SRFI-18 Threads | |
1674 | @subsubsection SRFI-18 Threads | |
1675 | ||
1676 | Threads created by SRFI-18 differ in two ways from threads created by | |
1677 | Guile's built-in thread functions. First, a thread created by SRFI-18 | |
1678 | @code{make-thread} begins in a blocked state and will not start | |
1679 | execution until @code{thread-start!} is called on it. Second, SRFI-18 | |
1680 | threads are constructed with a top-level exception handler that | |
1681 | captures any exceptions that are thrown on thread exit. In all other | |
1682 | regards, SRFI-18 threads are identical to normal Guile threads. | |
1683 | ||
1684 | @defun current-thread | |
1685 | Returns the thread that called this function. This is the same | |
1686 | procedure as the same-named built-in procedure @code{current-thread} | |
1687 | (@pxref{Threads}). | |
1688 | @end defun | |
1689 | ||
1690 | @defun thread? obj | |
1691 | Returns @code{#t} if @var{obj} is a thread, @code{#f} otherwise. This | |
1692 | is the same procedure as the same-named built-in procedure | |
1693 | @code{thread?} (@pxref{Threads}). | |
1694 | @end defun | |
1695 | ||
1696 | @defun make-thread thunk [name] | |
1697 | Call @code{thunk} in a new thread and with a new dynamic state, | |
1698 | returning the new thread and optionally assigning it the object name | |
1699 | @var{name}, which may be any Scheme object. | |
1700 | ||
1701 | Note that the name @code{make-thread} conflicts with the | |
1702 | @code{(ice-9 threads)} function @code{make-thread}. Applications | |
1703 | wanting to use both of these functions will need to refer to them by | |
1704 | different names. | |
1705 | @end defun | |
1706 | ||
1707 | @defun thread-name thread | |
1708 | Returns the name assigned to @var{thread} at the time of its creation, | |
1709 | or @code{#f} if it was not given a name. | |
1710 | @end defun | |
1711 | ||
1712 | @defun thread-specific thread | |
1713 | @defunx thread-specific-set! thread obj | |
1714 | Get or set the ``object-specific'' property of @var{thread}. In | |
1715 | Guile's implementation of SRFI-18, this value is stored as an object | |
1716 | property, and will be @code{#f} if not set. | |
1717 | @end defun | |
1718 | ||
1719 | @defun thread-start! thread | |
1720 | Unblocks @var{thread} and allows it to begin execution if it has not | |
1721 | done so already. | |
1722 | @end defun | |
1723 | ||
1724 | @defun thread-yield! | |
1725 | If one or more threads are waiting to execute, calling | |
1726 | @code{thread-yield!} forces an immediate context switch to one of them. | |
1727 | Otherwise, @code{thread-yield!} has no effect. @code{thread-yield!} | |
1728 | behaves identically to the Guile built-in function @code{yield}. | |
1729 | @end defun | |
1730 | ||
1731 | @defun thread-sleep! timeout | |
1732 | The current thread waits until the point specified by the time object | |
1733 | @var{timeout} is reached (@pxref{SRFI-18 Time}). This blocks the | |
1734 | thread only if @var{timeout} represents a point in the future. it is | |
1735 | an error for @var{timeout} to be @code{#f}. | |
1736 | @end defun | |
1737 | ||
1738 | @defun thread-terminate! thread | |
1739 | Causes an abnormal termination of @var{thread}. If @var{thread} is | |
1740 | not already terminated, all mutexes owned by @var{thread} become | |
1741 | unlocked/abandoned. If @var{thread} is the current thread, | |
1742 | @code{thread-terminate!} does not return. Otherwise | |
1743 | @code{thread-terminate!} returns an unspecified value; the termination | |
1744 | of @var{thread} will occur before @code{thread-terminate!} returns. | |
1745 | Subsequent attempts to join on @var{thread} will cause a ``terminated | |
1746 | thread exception'' to be raised. | |
1747 | ||
1748 | @code{thread-terminate!} is compatible with the thread cancellation | |
1749 | procedures in the core threads API (@pxref{Threads}) in that if a | |
1750 | cleanup handler has been installed for the target thread, it will be | |
1751 | called before the thread exits and its return value (or exception, if | |
1752 | any) will be stored for later retrieval via a call to | |
1753 | @code{thread-join!}. | |
1754 | @end defun | |
1755 | ||
1756 | @defun thread-join! thread [timeout [timeout-val]] | |
1757 | Wait for @var{thread} to terminate and return its exit value. When a | |
1758 | time value @var{timeout} is given, it specifies a point in time where | |
1759 | the waiting should be aborted. When the waiting is aborted, | |
1760 | @var{timeoutval} is returned if it is specified; otherwise, a | |
1761 | @code{join-timeout-exception} exception is raised | |
1762 | (@pxref{SRFI-18 Exceptions}). Exceptions may also be raised if the | |
1763 | thread was terminated by a call to @code{thread-terminate!} | |
1764 | (@code{terminated-thread-exception} will be raised) or if the thread | |
1765 | exited by raising an exception that was handled by the top-level | |
1766 | exception handler (@code{uncaught-exception} will be raised; the | |
1767 | original exception can be retrieved using | |
1768 | @code{uncaught-exception-reason}). | |
1769 | @end defun | |
1770 | ||
1771 | ||
1772 | @node SRFI-18 Mutexes | |
1773 | @subsubsection SRFI-18 Mutexes | |
1774 | ||
1775 | The behavior of Guile's built-in mutexes is parameterized via a set of | |
1776 | flags passed to the @code{make-mutex} procedure in the core | |
1777 | (@pxref{Mutexes and Condition Variables}). To satisfy the requirements | |
1778 | for mutexes specified by SRFI-18, the @code{make-mutex} procedure | |
1779 | described below sets the following flags: | |
1780 | @itemize @bullet | |
1781 | @item | |
1782 | @code{recursive}: the mutex can be locked recursively | |
1783 | @item | |
1784 | @code{unchecked-unlock}: attempts to unlock a mutex that is already | |
1785 | unlocked will not raise an exception | |
1786 | @item | |
1787 | @code{allow-external-unlock}: the mutex can be unlocked by any thread, | |
1788 | not just the thread that locked it originally | |
1789 | @end itemize | |
1790 | ||
1791 | @defun make-mutex [name] | |
1792 | Returns a new mutex, optionally assigning it the object name | |
1793 | @var{name}, which may be any Scheme object. The returned mutex will be | |
1794 | created with the configuration described above. Note that the name | |
1795 | @code{make-mutex} conflicts with Guile core function @code{make-mutex}. | |
1796 | Applications wanting to use both of these functions will need to refer | |
1797 | to them by different names. | |
1798 | @end defun | |
1799 | ||
1800 | @defun mutex-name mutex | |
1801 | Returns the name assigned to @var{mutex} at the time of its creation, | |
1802 | or @code{#f} if it was not given a name. | |
1803 | @end defun | |
1804 | ||
1805 | @defun mutex-specific mutex | |
1806 | @defunx mutex-specific-set! mutex obj | |
1807 | Get or set the ``object-specific'' property of @var{mutex}. In Guile's | |
1808 | implementation of SRFI-18, this value is stored as an object property, | |
1809 | and will be @code{#f} if not set. | |
1810 | @end defun | |
1811 | ||
1812 | @defun mutex-state mutex | |
1813 | Returns information about the state of @var{mutex}. Possible values | |
1814 | are: | |
1815 | @itemize @bullet | |
1816 | @item | |
1817 | thread @code{T}: the mutex is in the locked/owned state and thread T | |
1818 | is the owner of the mutex | |
1819 | @item | |
1820 | symbol @code{not-owned}: the mutex is in the locked/not-owned state | |
1821 | @item | |
1822 | symbol @code{abandoned}: the mutex is in the unlocked/abandoned state | |
1823 | @item | |
1824 | symbol @code{not-abandoned}: the mutex is in the | |
1825 | unlocked/not-abandoned state | |
1826 | @end itemize | |
1827 | @end defun | |
1828 | ||
1829 | @defun mutex-lock! mutex [timeout [thread]] | |
1830 | Lock @var{mutex}, optionally specifying a time object @var{timeout} | |
1831 | after which to abort the lock attempt and a thread @var{thread} giving | |
1832 | a new owner for @var{mutex} different than the current thread. This | |
1833 | procedure has the same behavior as the @code{lock-mutex} procedure in | |
1834 | the core library. | |
1835 | @end defun | |
1836 | ||
1837 | @defun mutex-unlock! mutex [condition-variable [timeout]] | |
1838 | Unlock @var{mutex}, optionally specifying a condition variable | |
1839 | @var{condition-variable} on which to wait, either indefinitely or, | |
1840 | optionally, until the time object @var{timeout} has passed, to be | |
1841 | signalled. This procedure has the same behavior as the | |
1842 | @code{unlock-mutex} procedure in the core library. | |
1843 | @end defun | |
1844 | ||
1845 | ||
1846 | @node SRFI-18 Condition variables | |
1847 | @subsubsection SRFI-18 Condition variables | |
1848 | ||
1849 | SRFI-18 does not specify a ``wait'' function for condition variables. | |
1850 | Waiting on a condition variable can be simulated using the SRFI-18 | |
1851 | @code{mutex-unlock!} function described in the previous section, or | |
1852 | Guile's built-in @code{wait-condition-variable} procedure can be used. | |
1853 | ||
1854 | @defun condition-variable? obj | |
1855 | Returns @code{#t} if @var{obj} is a condition variable, @code{#f} | |
1856 | otherwise. This is the same procedure as the same-named built-in | |
1857 | procedure | |
1858 | (@pxref{Mutexes and Condition Variables, @code{condition-variable?}}). | |
1859 | @end defun | |
1860 | ||
1861 | @defun make-condition-variable [name] | |
1862 | Returns a new condition variable, optionally assigning it the object | |
1863 | name @var{name}, which may be any Scheme object. This procedure | |
1864 | replaces a procedure of the same name in the core library. | |
1865 | @end defun | |
1866 | ||
1867 | @defun condition-variable-name condition-variable | |
1868 | Returns the name assigned to @var{thread} at the time of its creation, | |
1869 | or @code{#f} if it was not given a name. | |
1870 | @end defun | |
1871 | ||
1872 | @defun condition-variable-specific condition-variable | |
1873 | @defunx condition-variable-specific-set! condition-variable obj | |
1874 | Get or set the ``object-specific'' property of | |
1875 | @var{condition-variable}. In Guile's implementation of SRFI-18, this | |
1876 | value is stored as an object property, and will be @code{#f} if not | |
1877 | set. | |
1878 | @end defun | |
1879 | ||
1880 | @defun condition-variable-signal! condition-variable | |
1881 | @defunx condition-variable-broadcast! condition-variable | |
1882 | Wake up one thread that is waiting for @var{condition-variable}, in | |
1883 | the case of @code{condition-variable-signal!}, or all threads waiting | |
1884 | for it, in the case of @code{condition-variable-broadcast!}. The | |
1885 | behavior of these procedures is equivalent to that of the procedures | |
1886 | @code{signal-condition-variable} and | |
1887 | @code{broadcast-condition-variable} in the core library. | |
1888 | @end defun | |
1889 | ||
1890 | ||
1891 | @node SRFI-18 Time | |
1892 | @subsubsection SRFI-18 Time | |
1893 | ||
1894 | The SRFI-18 time functions manipulate time in two formats: a | |
1895 | ``time object'' type that represents an absolute point in time in some | |
1896 | implementation-specific way; and the number of seconds since some | |
1897 | unspecified ``epoch''. In Guile's implementation, the epoch is the | |
1898 | Unix epoch, 00:00:00 UTC, January 1, 1970. | |
1899 | ||
1900 | @defun current-time | |
1901 | Return the current time as a time object. This procedure replaces | |
1902 | the procedure of the same name in the core library, which returns the | |
1903 | current time in seconds since the epoch. | |
1904 | @end defun | |
1905 | ||
1906 | @defun time? obj | |
1907 | Returns @code{#t} if @var{obj} is a time object, @code{#f} otherwise. | |
1908 | @end defun | |
1909 | ||
1910 | @defun time->seconds time | |
1911 | @defunx seconds->time seconds | |
1912 | Convert between time objects and numerical values representing the | |
1913 | number of seconds since the epoch. When converting from a time object | |
1914 | to seconds, the return value is the number of seconds between | |
1915 | @var{time} and the epoch. When converting from seconds to a time | |
1916 | object, the return value is a time object that represents a time | |
1917 | @var{seconds} seconds after the epoch. | |
1918 | @end defun | |
1919 | ||
1920 | ||
1921 | @node SRFI-18 Exceptions | |
1922 | @subsubsection SRFI-18 Exceptions | |
1923 | ||
1924 | SRFI-18 exceptions are identical to the exceptions provided by | |
1925 | Guile's implementation of SRFI-34. The behavior of exception | |
1926 | handlers invoked to handle exceptions thrown from SRFI-18 functions, | |
1927 | however, differs from the conventional behavior of SRFI-34 in that | |
1928 | the continuation of the handler is the same as that of the call to | |
1929 | the function. Handlers are called in a tail-recursive manner; the | |
1930 | exceptions do not ``bubble up''. | |
1931 | ||
1932 | @defun current-exception-handler | |
1933 | Returns the current exception handler. | |
1934 | @end defun | |
1935 | ||
1936 | @defun with-exception-handler handler thunk | |
1937 | Installs @var{handler} as the current exception handler and calls the | |
1938 | procedure @var{thunk} with no arguments, returning its value as the | |
1939 | value of the exception. @var{handler} must be a procedure that accepts | |
1940 | a single argument. The current exception handler at the time this | |
1941 | procedure is called will be restored after the call returns. | |
1942 | @end defun | |
1943 | ||
1944 | @defun raise obj | |
1945 | Raise @var{obj} as an exception. This is the same procedure as the | |
1946 | same-named procedure defined in SRFI 34. | |
1947 | @end defun | |
1948 | ||
1949 | @defun join-timeout-exception? obj | |
1950 | Returns @code{#t} if @var{obj} is an exception raised as the result of | |
1951 | performing a timed join on a thread that does not exit within the | |
1952 | specified timeout, @code{#f} otherwise. | |
1953 | @end defun | |
1954 | ||
1955 | @defun abandoned-mutex-exception? obj | |
1956 | Returns @code{#t} if @var{obj} is an exception raised as the result of | |
1957 | attempting to lock a mutex that has been abandoned by its owner thread, | |
1958 | @code{#f} otherwise. | |
1959 | @end defun | |
1960 | ||
1961 | @defun terminated-thread-exception? obj | |
1962 | Returns @code{#t} if @var{obj} is an exception raised as the result of | |
1963 | joining on a thread that exited as the result of a call to | |
1964 | @code{thread-terminate!}. | |
1965 | @end defun | |
1966 | ||
1967 | @defun uncaught-exception? obj | |
1968 | @defunx uncaught-exception-reason exc | |
1969 | @code{uncaught-exception?} returns @code{#t} if @var{obj} is an | |
1970 | exception thrown as the result of joining a thread that exited by | |
1971 | raising an exception that was handled by the top-level exception | |
1972 | handler installed by @code{make-thread}. When this occurs, the | |
1973 | original exception is preserved as part of the exception thrown by | |
1974 | @code{thread-join!} and can be accessed by calling | |
1975 | @code{uncaught-exception-reason} on that exception. Note that | |
1976 | because this exception-preservation mechanism is a side-effect of | |
1977 | @code{make-thread}, joining on threads that exited as described above | |
1978 | but were created by other means will not raise this | |
1979 | @code{uncaught-exception} error. | |
1980 | @end defun | |
1981 | ||
1982 | ||
12991fed | 1983 | @node SRFI-19 |
3229f68b | 1984 | @subsection SRFI-19 - Time/Date Library |
8742c48b | 1985 | @cindex SRFI-19 |
7c2e18cd KR |
1986 | @cindex time |
1987 | @cindex date | |
12991fed | 1988 | |
85600a0f KR |
1989 | This is an implementation of the SRFI-19 time/date library. The |
1990 | functions and variables described here are provided by | |
12991fed TTN |
1991 | |
1992 | @example | |
85600a0f | 1993 | (use-modules (srfi srfi-19)) |
12991fed TTN |
1994 | @end example |
1995 | ||
7d281fa5 KR |
1996 | @strong{Caution}: The current code in this module incorrectly extends |
1997 | the Gregorian calendar leap year rule back prior to the introduction | |
1998 | of those reforms in 1582 (or the appropriate year in various | |
1999 | countries). The Julian calendar was used prior to 1582, and there | |
2000 | were 10 days skipped for the reform, but the code doesn't implement | |
2001 | that. | |
2002 | ||
2003 | This will be fixed some time. Until then calculations for 1583 | |
2004 | onwards are correct, but prior to that any day/month/year and day of | |
2005 | the week calculations are wrong. | |
2006 | ||
85600a0f KR |
2007 | @menu |
2008 | * SRFI-19 Introduction:: | |
2009 | * SRFI-19 Time:: | |
2010 | * SRFI-19 Date:: | |
2011 | * SRFI-19 Time/Date conversions:: | |
2012 | * SRFI-19 Date to string:: | |
2013 | * SRFI-19 String to date:: | |
2014 | @end menu | |
12991fed | 2015 | |
85600a0f | 2016 | @node SRFI-19 Introduction |
3229f68b | 2017 | @subsubsection SRFI-19 Introduction |
85600a0f KR |
2018 | |
2019 | @cindex universal time | |
2020 | @cindex atomic time | |
2021 | @cindex UTC | |
2022 | @cindex TAI | |
2023 | This module implements time and date representations and calculations, | |
2024 | in various time systems, including universal time (UTC) and atomic | |
2025 | time (TAI). | |
2026 | ||
2027 | For those not familiar with these time systems, TAI is based on a | |
2028 | fixed length second derived from oscillations of certain atoms. UTC | |
2029 | differs from TAI by an integral number of seconds, which is increased | |
2030 | or decreased at announced times to keep UTC aligned to a mean solar | |
2031 | day (the orbit and rotation of the earth are not quite constant). | |
2032 | ||
2033 | @cindex leap second | |
2034 | So far, only increases in the TAI | |
2035 | @tex | |
2036 | $\leftrightarrow$ | |
2037 | @end tex | |
2038 | @ifnottex | |
2039 | <-> | |
2040 | @end ifnottex | |
2041 | UTC difference have been needed. Such an increase is a ``leap | |
2042 | second'', an extra second of TAI introduced at the end of a UTC day. | |
2043 | When working entirely within UTC this is never seen, every day simply | |
2044 | has 86400 seconds. But when converting from TAI to a UTC date, an | |
2045 | extra 23:59:60 is present, where normally a day would end at 23:59:59. | |
2046 | Effectively the UTC second from 23:59:59 to 00:00:00 has taken two TAI | |
2047 | seconds. | |
2048 | ||
2049 | @cindex system clock | |
2050 | In the current implementation, the system clock is assumed to be UTC, | |
2051 | and a table of leap seconds in the code converts to TAI. See comments | |
2052 | in @file{srfi-19.scm} for how to update this table. | |
2053 | ||
2054 | @cindex julian day | |
2055 | @cindex modified julian day | |
2056 | Also, for those not familiar with the terminology, a @dfn{Julian Day} | |
2057 | is a real number which is a count of days and fraction of a day, in | |
2058 | UTC, starting from -4713-01-01T12:00:00Z, ie.@: midday Monday 1 Jan | |
7c2e18cd KR |
2059 | 4713 B.C. A @dfn{Modified Julian Day} is the same, but starting from |
2060 | 1858-11-17T00:00:00Z, ie.@: midnight 17 November 1858 UTC. That time | |
2061 | is julian day 2400000.5. | |
85600a0f KR |
2062 | |
2063 | @c The SRFI-1 spec says -4714-11-24T12:00:00Z (November 24, -4714 at | |
2064 | @c noon, UTC), but this is incorrect. It looks like it might have | |
2065 | @c arisen from the code incorrectly treating years a multiple of 100 | |
7c2e18cd | 2066 | @c but not 400 prior to 1582 as non-leap years, where instead the Julian |
85600a0f KR |
2067 | @c calendar should be used so all multiples of 4 before 1582 are leap |
2068 | @c years. | |
2069 | ||
2070 | ||
2071 | @node SRFI-19 Time | |
3229f68b | 2072 | @subsubsection SRFI-19 Time |
85600a0f KR |
2073 | @cindex time |
2074 | ||
2075 | A @dfn{time} object has type, seconds and nanoseconds fields | |
2076 | representing a point in time starting from some epoch. This is an | |
2077 | arbitrary point in time, not just a time of day. Although times are | |
2078 | represented in nanoseconds, the actual resolution may be lower. | |
2079 | ||
2080 | The following variables hold the possible time types. For instance | |
2081 | @code{(current-time time-process)} would give the current CPU process | |
2082 | time. | |
2083 | ||
2084 | @defvar time-utc | |
2085 | Universal Coordinated Time (UTC). | |
2086 | @cindex UTC | |
2087 | @end defvar | |
12991fed | 2088 | |
85600a0f KR |
2089 | @defvar time-tai |
2090 | International Atomic Time (TAI). | |
2091 | @cindex TAI | |
2092 | @end defvar | |
12991fed | 2093 | |
85600a0f KR |
2094 | @defvar time-monotonic |
2095 | Monotonic time, meaning a monotonically increasing time starting from | |
2096 | an unspecified epoch. | |
12991fed | 2097 | |
85600a0f KR |
2098 | Note that in the current implementation @code{time-monotonic} is the |
2099 | same as @code{time-tai}, and unfortunately is therefore affected by | |
2100 | adjustments to the system clock. Perhaps this will change in the | |
2101 | future. | |
2102 | @end defvar | |
12991fed | 2103 | |
85600a0f KR |
2104 | @defvar time-duration |
2105 | A duration, meaning simply a difference between two times. | |
2106 | @end defvar | |
12991fed | 2107 | |
85600a0f KR |
2108 | @defvar time-process |
2109 | CPU time spent in the current process, starting from when the process | |
2110 | began. | |
2111 | @cindex process time | |
2112 | @end defvar | |
12991fed | 2113 | |
85600a0f KR |
2114 | @defvar time-thread |
2115 | CPU time spent in the current thread. Not currently implemented. | |
2116 | @cindex thread time | |
2117 | @end defvar | |
12991fed | 2118 | |
85600a0f KR |
2119 | @sp 1 |
2120 | @defun time? obj | |
2121 | Return @code{#t} if @var{obj} is a time object, or @code{#f} if not. | |
2122 | @end defun | |
2123 | ||
2124 | @defun make-time type nanoseconds seconds | |
2125 | Create a time object with the given @var{type}, @var{seconds} and | |
2126 | @var{nanoseconds}. | |
2127 | @end defun | |
2128 | ||
2129 | @defun time-type time | |
2130 | @defunx time-nanosecond time | |
2131 | @defunx time-second time | |
2132 | @defunx set-time-type! time type | |
2133 | @defunx set-time-nanosecond! time nsec | |
2134 | @defunx set-time-second! time sec | |
2135 | Get or set the type, seconds or nanoseconds fields of a time object. | |
2136 | ||
2137 | @code{set-time-type!} merely changes the field, it doesn't convert the | |
2138 | time value. For conversions, see @ref{SRFI-19 Time/Date conversions}. | |
2139 | @end defun | |
2140 | ||
2141 | @defun copy-time time | |
2142 | Return a new time object, which is a copy of the given @var{time}. | |
2143 | @end defun | |
2144 | ||
2145 | @defun current-time [type] | |
2146 | Return the current time of the given @var{type}. The default | |
2147 | @var{type} is @code{time-utc}. | |
2148 | ||
2149 | Note that the name @code{current-time} conflicts with the Guile core | |
e68f492a JG |
2150 | @code{current-time} function (@pxref{Time}) as well as the SRFI-18 |
2151 | @code{current-time} function (@pxref{SRFI-18 Time}). Applications | |
2152 | wanting to use more than one of these functions will need to refer to | |
2153 | them by different names. | |
85600a0f KR |
2154 | @end defun |
2155 | ||
2156 | @defun time-resolution [type] | |
2157 | Return the resolution, in nanoseconds, of the given time @var{type}. | |
2158 | The default @var{type} is @code{time-utc}. | |
2159 | @end defun | |
2160 | ||
2161 | @defun time<=? t1 t2 | |
2162 | @defunx time<? t1 t2 | |
2163 | @defunx time=? t1 t2 | |
2164 | @defunx time>=? t1 t2 | |
2165 | @defunx time>? t1 t2 | |
2166 | Return @code{#t} or @code{#f} according to the respective relation | |
2167 | between time objects @var{t1} and @var{t2}. @var{t1} and @var{t2} | |
2168 | must be the same time type. | |
2169 | @end defun | |
2170 | ||
2171 | @defun time-difference t1 t2 | |
2172 | @defunx time-difference! t1 t2 | |
2173 | Return a time object of type @code{time-duration} representing the | |
2174 | period between @var{t1} and @var{t2}. @var{t1} and @var{t2} must be | |
2175 | the same time type. | |
2176 | ||
2177 | @code{time-difference} returns a new time object, | |
2178 | @code{time-difference!} may modify @var{t1} to form its return. | |
2179 | @end defun | |
2180 | ||
2181 | @defun add-duration time duration | |
2182 | @defunx add-duration! time duration | |
2183 | @defunx subtract-duration time duration | |
2184 | @defunx subtract-duration! time duration | |
2185 | Return a time object which is @var{time} with the given @var{duration} | |
2186 | added or subtracted. @var{duration} must be a time object of type | |
2187 | @code{time-duration}. | |
2188 | ||
2189 | @code{add-duration} and @code{subtract-duration} return a new time | |
2190 | object. @code{add-duration!} and @code{subtract-duration!} may modify | |
2191 | the given @var{time} to form their return. | |
2192 | @end defun | |
2193 | ||
2194 | ||
2195 | @node SRFI-19 Date | |
3229f68b | 2196 | @subsubsection SRFI-19 Date |
85600a0f KR |
2197 | @cindex date |
2198 | ||
2199 | A @dfn{date} object represents a date in the Gregorian calendar and a | |
2200 | time of day on that date in some timezone. | |
2201 | ||
2202 | The fields are year, month, day, hour, minute, second, nanoseconds and | |
2203 | timezone. A date object is immutable, its fields can be read but they | |
2204 | cannot be modified once the object is created. | |
2205 | ||
2206 | @defun date? obj | |
2207 | Return @code{#t} if @var{obj} is a date object, or @code{#f} if not. | |
2208 | @end defun | |
2209 | ||
2210 | @defun make-date nsecs seconds minutes hours date month year zone-offset | |
2211 | Create a new date object. | |
2212 | @c | |
2213 | @c FIXME: What can we say about the ranges of the values. The | |
2214 | @c current code looks it doesn't normalize, but expects then in their | |
2215 | @c usual range already. | |
2216 | @c | |
2217 | @end defun | |
2218 | ||
2219 | @defun date-nanosecond date | |
2220 | Nanoseconds, 0 to 999999999. | |
2221 | @end defun | |
2222 | ||
2223 | @defun date-second date | |
7c2e18cd KR |
2224 | Seconds, 0 to 59, or 60 for a leap second. 60 is never seen when working |
2225 | entirely within UTC, it's only when converting to or from TAI. | |
85600a0f KR |
2226 | @end defun |
2227 | ||
2228 | @defun date-minute date | |
2229 | Minutes, 0 to 59. | |
2230 | @end defun | |
2231 | ||
2232 | @defun date-hour date | |
2233 | Hour, 0 to 23. | |
2234 | @end defun | |
2235 | ||
2236 | @defun date-day date | |
2237 | Day of the month, 1 to 31 (or less, according to the month). | |
2238 | @end defun | |
2239 | ||
2240 | @defun date-month date | |
2241 | Month, 1 to 12. | |
2242 | @end defun | |
2243 | ||
2244 | @defun date-year date | |
7c2e18cd KR |
2245 | Year, eg.@: 2003. Dates B.C.@: are negative, eg.@: @math{-46} is 46 |
2246 | B.C. There is no year 0, year @math{-1} is followed by year 1. | |
85600a0f KR |
2247 | @end defun |
2248 | ||
2249 | @defun date-zone-offset date | |
2250 | Time zone, an integer number of seconds east of Greenwich. | |
2251 | @end defun | |
2252 | ||
2253 | @defun date-year-day date | |
2254 | Day of the year, starting from 1 for 1st January. | |
2255 | @end defun | |
2256 | ||
2257 | @defun date-week-day date | |
2258 | Day of the week, starting from 0 for Sunday. | |
2259 | @end defun | |
2260 | ||
2261 | @defun date-week-number date dstartw | |
2262 | Week of the year, ignoring a first partial week. @var{dstartw} is the | |
2263 | day of the week which is taken to start a week, 0 for Sunday, 1 for | |
2264 | Monday, etc. | |
2265 | @c | |
2266 | @c FIXME: The spec doesn't say whether numbering starts at 0 or 1. | |
2267 | @c The code looks like it's 0, if that's the correct intention. | |
2268 | @c | |
2269 | @end defun | |
2270 | ||
2271 | @c The SRFI text doesn't actually give the default for tz-offset, but | |
2272 | @c the reference implementation has the local timezone and the | |
2273 | @c conversions functions all specify that, so it should be ok to | |
2274 | @c document it here. | |
2275 | @c | |
2276 | @defun current-date [tz-offset] | |
7c2e18cd KR |
2277 | Return a date object representing the current date/time, in UTC offset |
2278 | by @var{tz-offset}. @var{tz-offset} is seconds east of Greenwich and | |
2279 | defaults to the local timezone. | |
85600a0f KR |
2280 | @end defun |
2281 | ||
2282 | @defun current-julian-day | |
2283 | @cindex julian day | |
2284 | Return the current Julian Day. | |
2285 | @end defun | |
2286 | ||
2287 | @defun current-modified-julian-day | |
2288 | @cindex modified julian day | |
2289 | Return the current Modified Julian Day. | |
2290 | @end defun | |
2291 | ||
2292 | ||
2293 | @node SRFI-19 Time/Date conversions | |
3229f68b | 2294 | @subsubsection SRFI-19 Time/Date conversions |
7c2e18cd KR |
2295 | @cindex time conversion |
2296 | @cindex date conversion | |
85600a0f KR |
2297 | |
2298 | @defun date->julian-day date | |
2299 | @defunx date->modified-julian-day date | |
2300 | @defunx date->time-monotonic date | |
2301 | @defunx date->time-tai date | |
2302 | @defunx date->time-utc date | |
2303 | @end defun | |
2304 | @defun julian-day->date jdn [tz-offset] | |
2305 | @defunx julian-day->time-monotonic jdn | |
2306 | @defunx julian-day->time-tai jdn | |
2307 | @defunx julian-day->time-utc jdn | |
2308 | @end defun | |
2309 | @defun modified-julian-day->date jdn [tz-offset] | |
2310 | @defunx modified-julian-day->time-monotonic jdn | |
2311 | @defunx modified-julian-day->time-tai jdn | |
2312 | @defunx modified-julian-day->time-utc jdn | |
2313 | @end defun | |
2314 | @defun time-monotonic->date time [tz-offset] | |
2315 | @defunx time-monotonic->time-tai time | |
2316 | @defunx time-monotonic->time-tai! time | |
2317 | @defunx time-monotonic->time-utc time | |
2318 | @defunx time-monotonic->time-utc! time | |
2319 | @end defun | |
2320 | @defun time-tai->date time [tz-offset] | |
2321 | @defunx time-tai->julian-day time | |
2322 | @defunx time-tai->modified-julian-day time | |
2323 | @defunx time-tai->time-monotonic time | |
2324 | @defunx time-tai->time-monotonic! time | |
2325 | @defunx time-tai->time-utc time | |
2326 | @defunx time-tai->time-utc! time | |
2327 | @end defun | |
2328 | @defun time-utc->date time [tz-offset] | |
2329 | @defunx time-utc->julian-day time | |
2330 | @defunx time-utc->modified-julian-day time | |
2331 | @defunx time-utc->time-monotonic time | |
2332 | @defunx time-utc->time-monotonic! time | |
2333 | @defunx time-utc->time-tai time | |
2334 | @defunx time-utc->time-tai! time | |
2335 | @sp 1 | |
2336 | Convert between dates, times and days of the respective types. For | |
2337 | instance @code{time-tai->time-utc} accepts a @var{time} object of type | |
2338 | @code{time-tai} and returns an object of type @code{time-utc}. | |
2339 | ||
85600a0f KR |
2340 | The @code{!} variants may modify their @var{time} argument to form |
2341 | their return. The plain functions create a new object. | |
702e6e09 KR |
2342 | |
2343 | For conversions to dates, @var{tz-offset} is seconds east of | |
2344 | Greenwich. The default is the local timezone, at the given time, as | |
2345 | provided by the system, using @code{localtime} (@pxref{Time}). | |
2346 | ||
2347 | On 32-bit systems, @code{localtime} is limited to a 32-bit | |
2348 | @code{time_t}, so a default @var{tz-offset} is only available for | |
2349 | times between Dec 1901 and Jan 2038. For prior dates an application | |
2350 | might like to use the value in 1902, though some locations have zone | |
2351 | changes prior to that. For future dates an application might like to | |
2352 | assume today's rules extend indefinitely. But for correct daylight | |
2353 | savings transitions it will be necessary to take an offset for the | |
2354 | same day and time but a year in range and which has the same starting | |
2355 | weekday and same leap/non-leap (to support rules like last Sunday in | |
2356 | October). | |
85600a0f KR |
2357 | @end defun |
2358 | ||
2359 | @node SRFI-19 Date to string | |
3229f68b | 2360 | @subsubsection SRFI-19 Date to string |
85600a0f | 2361 | @cindex date to string |
7c2e18cd | 2362 | @cindex string, from date |
85600a0f KR |
2363 | |
2364 | @defun date->string date [format] | |
2365 | Convert a date to a string under the control of a format. | |
2366 | @var{format} should be a string containing @samp{~} escapes, which | |
2367 | will be expanded as per the following conversion table. The default | |
2368 | @var{format} is @samp{~c}, a locale-dependent date and time. | |
2369 | ||
2370 | Many of these conversion characters are the same as POSIX | |
2371 | @code{strftime} (@pxref{Time}), but there are some extras and some | |
2372 | variations. | |
2373 | ||
2374 | @multitable {MMMM} {MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM} | |
2375 | @item @nicode{~~} @tab literal ~ | |
2376 | @item @nicode{~a} @tab locale abbreviated weekday, eg.@: @samp{Sun} | |
2377 | @item @nicode{~A} @tab locale full weekday, eg.@: @samp{Sunday} | |
2378 | @item @nicode{~b} @tab locale abbreviated month, eg.@: @samp{Jan} | |
2379 | @item @nicode{~B} @tab locale full month, eg.@: @samp{January} | |
2380 | @item @nicode{~c} @tab locale date and time, eg.@: @* | |
2381 | @samp{Fri Jul 14 20:28:42-0400 2000} | |
2382 | @item @nicode{~d} @tab day of month, zero padded, @samp{01} to @samp{31} | |
2383 | ||
2384 | @c Spec says d/m/y, reference implementation says m/d/y. | |
2385 | @c Apparently the reference code was the intention, but would like to | |
2386 | @c see an errata published for the spec before contradicting it here. | |
2387 | @c | |
2388 | @c @item @nicode{~D} @tab date @nicode{~d/~m/~y} | |
2389 | ||
2390 | @item @nicode{~e} @tab day of month, blank padded, @samp{ 1} to @samp{31} | |
2391 | @item @nicode{~f} @tab seconds and fractional seconds, | |
2392 | with locale decimal point, eg.@: @samp{5.2} | |
2393 | @item @nicode{~h} @tab same as @nicode{~b} | |
2394 | @item @nicode{~H} @tab hour, 24-hour clock, zero padded, @samp{00} to @samp{23} | |
2395 | @item @nicode{~I} @tab hour, 12-hour clock, zero padded, @samp{01} to @samp{12} | |
2396 | @item @nicode{~j} @tab day of year, zero padded, @samp{001} to @samp{366} | |
2397 | @item @nicode{~k} @tab hour, 24-hour clock, blank padded, @samp{ 0} to @samp{23} | |
2398 | @item @nicode{~l} @tab hour, 12-hour clock, blank padded, @samp{ 1} to @samp{12} | |
2399 | @item @nicode{~m} @tab month, zero padded, @samp{01} to @samp{12} | |
2400 | @item @nicode{~M} @tab minute, zero padded, @samp{00} to @samp{59} | |
2401 | @item @nicode{~n} @tab newline | |
2402 | @item @nicode{~N} @tab nanosecond, zero padded, @samp{000000000} to @samp{999999999} | |
2403 | @item @nicode{~p} @tab locale AM or PM | |
2404 | @item @nicode{~r} @tab time, 12 hour clock, @samp{~I:~M:~S ~p} | |
2405 | @item @nicode{~s} @tab number of full seconds since ``the epoch'' in UTC | |
2406 | @item @nicode{~S} @tab second, zero padded @samp{00} to @samp{60} @* | |
2407 | (usual limit is 59, 60 is a leap second) | |
2408 | @item @nicode{~t} @tab horizontal tab character | |
2409 | @item @nicode{~T} @tab time, 24 hour clock, @samp{~H:~M:~S} | |
2410 | @item @nicode{~U} @tab week of year, Sunday first day of week, | |
2411 | @samp{00} to @samp{52} | |
2412 | @item @nicode{~V} @tab week of year, Monday first day of week, | |
2413 | @samp{01} to @samp{53} | |
2414 | @item @nicode{~w} @tab day of week, 0 for Sunday, @samp{0} to @samp{6} | |
2415 | @item @nicode{~W} @tab week of year, Monday first day of week, | |
2416 | @samp{00} to @samp{52} | |
2417 | ||
2418 | @c The spec has ~x as an apparent duplicate of ~W, and ~X as a locale | |
2419 | @c date. The reference code has ~x as the locale date and ~X as a | |
2420 | @c locale time. The rule is apparently that the code should be | |
2421 | @c believed, but would like to see an errata for the spec before | |
2422 | @c contradicting it here. | |
2423 | @c | |
2424 | @c @item @nicode{~x} @tab week of year, Monday as first day of week, | |
2425 | @c @samp{00} to @samp{53} | |
2426 | @c @item @nicode{~X} @tab locale date, eg.@: @samp{07/31/00} | |
2427 | ||
2428 | @item @nicode{~y} @tab year, two digits, @samp{00} to @samp{99} | |
2429 | @item @nicode{~Y} @tab year, full, eg.@: @samp{2003} | |
2430 | @item @nicode{~z} @tab time zone, RFC-822 style | |
2431 | @item @nicode{~Z} @tab time zone symbol (not currently implemented) | |
2432 | @item @nicode{~1} @tab ISO-8601 date, @samp{~Y-~m-~d} | |
2433 | @item @nicode{~2} @tab ISO-8601 time+zone, @samp{~k:~M:~S~z} | |
2434 | @item @nicode{~3} @tab ISO-8601 time, @samp{~k:~M:~S} | |
2435 | @item @nicode{~4} @tab ISO-8601 date/time+zone, @samp{~Y-~m-~dT~k:~M:~S~z} | |
2436 | @item @nicode{~5} @tab ISO-8601 date/time, @samp{~Y-~m-~dT~k:~M:~S} | |
2437 | @end multitable | |
2438 | @end defun | |
2439 | ||
2440 | Conversions @samp{~D}, @samp{~x} and @samp{~X} are not currently | |
2441 | described here, since the specification and reference implementation | |
2442 | differ. | |
2443 | ||
a2f00b9b LC |
2444 | Conversion is locale-dependent on systems that support it |
2445 | (@pxref{Accessing Locale Information}). @xref{Locales, | |
2446 | @code{setlocale}}, for information on how to change the current | |
2447 | locale. | |
85600a0f KR |
2448 | |
2449 | ||
2450 | @node SRFI-19 String to date | |
3229f68b | 2451 | @subsubsection SRFI-19 String to date |
85600a0f | 2452 | @cindex string to date |
7c2e18cd | 2453 | @cindex date, from string |
85600a0f KR |
2454 | |
2455 | @c FIXME: Can we say what happens when an incomplete date is | |
2456 | @c converted? Ie. fields left as 0, or what? The spec seems to be | |
2457 | @c silent on this. | |
2458 | ||
2459 | @defun string->date input template | |
2460 | Convert an @var{input} string to a date under the control of a | |
2461 | @var{template} string. Return a newly created date object. | |
2462 | ||
2463 | Literal characters in @var{template} must match characters in | |
2464 | @var{input} and @samp{~} escapes must match the input forms described | |
2465 | in the table below. ``Skip to'' means characters up to one of the | |
2466 | given type are ignored, or ``no skip'' for no skipping. ``Read'' is | |
2467 | what's then read, and ``Set'' is the field affected in the date | |
2468 | object. | |
2469 | ||
2470 | For example @samp{~Y} skips input characters until a digit is reached, | |
2471 | at which point it expects a year and stores that to the year field of | |
2472 | the date. | |
2473 | ||
2474 | @multitable {MMMM} {@nicode{char-alphabetic?}} {MMMMMMMMMMMMMMMMMMMMMMMMM} {@nicode{date-zone-offset}} | |
2475 | @item | |
2476 | @tab Skip to | |
2477 | @tab Read | |
2478 | @tab Set | |
2479 | ||
2480 | @item @nicode{~~} | |
2481 | @tab no skip | |
2482 | @tab literal ~ | |
2483 | @tab nothing | |
2484 | ||
2485 | @item @nicode{~a} | |
2486 | @tab @nicode{char-alphabetic?} | |
2487 | @tab locale abbreviated weekday name | |
2488 | @tab nothing | |
2489 | ||
2490 | @item @nicode{~A} | |
2491 | @tab @nicode{char-alphabetic?} | |
2492 | @tab locale full weekday name | |
2493 | @tab nothing | |
2494 | ||
2495 | @c Note that the SRFI spec says that ~b and ~B don't set anything, | |
2496 | @c but that looks like a mistake. The reference implementation sets | |
2497 | @c the month field, which seems sensible and is what we describe | |
2498 | @c here. | |
2499 | ||
2500 | @item @nicode{~b} | |
2501 | @tab @nicode{char-alphabetic?} | |
2502 | @tab locale abbreviated month name | |
2503 | @tab @nicode{date-month} | |
2504 | ||
2505 | @item @nicode{~B} | |
2506 | @tab @nicode{char-alphabetic?} | |
2507 | @tab locale full month name | |
2508 | @tab @nicode{date-month} | |
2509 | ||
2510 | @item @nicode{~d} | |
2511 | @tab @nicode{char-numeric?} | |
2512 | @tab day of month | |
2513 | @tab @nicode{date-day} | |
2514 | ||
2515 | @item @nicode{~e} | |
2516 | @tab no skip | |
2517 | @tab day of month, blank padded | |
2518 | @tab @nicode{date-day} | |
2519 | ||
2520 | @item @nicode{~h} | |
2521 | @tab same as @samp{~b} | |
2522 | ||
2523 | @item @nicode{~H} | |
2524 | @tab @nicode{char-numeric?} | |
2525 | @tab hour | |
2526 | @tab @nicode{date-hour} | |
2527 | ||
2528 | @item @nicode{~k} | |
2529 | @tab no skip | |
2530 | @tab hour, blank padded | |
2531 | @tab @nicode{date-hour} | |
2532 | ||
2533 | @item @nicode{~m} | |
2534 | @tab @nicode{char-numeric?} | |
2535 | @tab month | |
2536 | @tab @nicode{date-month} | |
2537 | ||
2538 | @item @nicode{~M} | |
2539 | @tab @nicode{char-numeric?} | |
2540 | @tab minute | |
2541 | @tab @nicode{date-minute} | |
2542 | ||
2543 | @item @nicode{~S} | |
2544 | @tab @nicode{char-numeric?} | |
2545 | @tab second | |
2546 | @tab @nicode{date-second} | |
2547 | ||
2548 | @item @nicode{~y} | |
2549 | @tab no skip | |
2550 | @tab 2-digit year | |
2551 | @tab @nicode{date-year} within 50 years | |
2552 | ||
2553 | @item @nicode{~Y} | |
2554 | @tab @nicode{char-numeric?} | |
2555 | @tab year | |
2556 | @tab @nicode{date-year} | |
2557 | ||
2558 | @item @nicode{~z} | |
2559 | @tab no skip | |
2560 | @tab time zone | |
2561 | @tab date-zone-offset | |
2562 | @end multitable | |
2563 | ||
2564 | Notice that the weekday matching forms don't affect the date object | |
2565 | returned, instead the weekday will be derived from the day, month and | |
2566 | year. | |
2567 | ||
a2f00b9b LC |
2568 | Conversion is locale-dependent on systems that support it |
2569 | (@pxref{Accessing Locale Information}). @xref{Locales, | |
2570 | @code{setlocale}}, for information on how to change the current | |
2571 | locale. | |
85600a0f | 2572 | @end defun |
12991fed | 2573 | |
1de8c1ae | 2574 | |
b0b55bd6 | 2575 | @node SRFI-26 |
3229f68b | 2576 | @subsection SRFI-26 - specializing parameters |
1de8c1ae | 2577 | @cindex SRFI-26 |
7c2e18cd KR |
2578 | @cindex parameter specialize |
2579 | @cindex argument specialize | |
2580 | @cindex specialize parameter | |
1de8c1ae KR |
2581 | |
2582 | This SRFI provides a syntax for conveniently specializing selected | |
2583 | parameters of a function. It can be used with, | |
2584 | ||
2585 | @example | |
2586 | (use-modules (srfi srfi-26)) | |
2587 | @end example | |
2588 | ||
2589 | @deffn {library syntax} cut slot @dots{} | |
2590 | @deffnx {library syntax} cute slot @dots{} | |
2591 | Return a new procedure which will make a call (@var{slot} @dots{}) but | |
2592 | with selected parameters specialized to given expressions. | |
2593 | ||
2594 | An example will illustrate the idea. The following is a | |
2595 | specialization of @code{write}, sending output to | |
2596 | @code{my-output-port}, | |
2597 | ||
2598 | @example | |
2599 | (cut write <> my-output-port) | |
2600 | @result{} | |
2601 | (lambda (obj) (write obj my-output-port)) | |
2602 | @end example | |
2603 | ||
2604 | The special symbol @code{<>} indicates a slot to be filled by an | |
2605 | argument to the new procedure. @code{my-output-port} on the other | |
2606 | hand is an expression to be evaluated and passed, ie.@: it specializes | |
2607 | the behaviour of @code{write}. | |
2608 | ||
2609 | @table @nicode | |
2610 | @item <> | |
2611 | A slot to be filled by an argument from the created procedure. | |
2612 | Arguments are assigned to @code{<>} slots in the order they appear in | |
2613 | the @code{cut} form, there's no way to re-arrange arguments. | |
2614 | ||
2615 | The first argument to @code{cut} is usually a procedure (or expression | |
2616 | giving a procedure), but @code{<>} is allowed there too. For example, | |
2617 | ||
2618 | @example | |
2619 | (cut <> 1 2 3) | |
2620 | @result{} | |
2621 | (lambda (proc) (proc 1 2 3)) | |
2622 | @end example | |
2623 | ||
2624 | @item <...> | |
2625 | A slot to be filled by all remaining arguments from the new procedure. | |
2626 | This can only occur at the end of a @code{cut} form. | |
2627 | ||
2628 | For example, a procedure taking a variable number of arguments like | |
2629 | @code{max} but in addition enforcing a lower bound, | |
2630 | ||
2631 | @example | |
2632 | (define my-lower-bound 123) | |
2633 | ||
2634 | (cut max my-lower-bound <...>) | |
2635 | @result{} | |
2636 | (lambda arglist (apply max my-lower-bound arglist)) | |
2637 | @end example | |
2638 | @end table | |
2639 | ||
2640 | For @code{cut} the specializing expressions are evaluated each time | |
2641 | the new procedure is called. For @code{cute} they're evaluated just | |
2642 | once, when the new procedure is created. The name @code{cute} stands | |
2643 | for ``@code{cut} with evaluated arguments''. In all cases the | |
2644 | evaluations take place in an unspecified order. | |
2645 | ||
2646 | The following illustrates the difference between @code{cut} and | |
2647 | @code{cute}, | |
2648 | ||
2649 | @example | |
2650 | (cut format <> "the time is ~s" (current-time)) | |
2651 | @result{} | |
2652 | (lambda (port) (format port "the time is ~s" (current-time))) | |
2653 | ||
2654 | (cute format <> "the time is ~s" (current-time)) | |
2655 | @result{} | |
2656 | (let ((val (current-time))) | |
2657 | (lambda (port) (format port "the time is ~s" val)) | |
2658 | @end example | |
2659 | ||
2660 | (There's no provision for a mixture of @code{cut} and @code{cute} | |
2661 | where some expressions would be evaluated every time but others | |
2662 | evaluated only once.) | |
2663 | ||
2664 | @code{cut} is really just a shorthand for the sort of @code{lambda} | |
2665 | forms shown in the above examples. But notice @code{cut} avoids the | |
2666 | need to name unspecialized parameters, and is more compact. Use in | |
2667 | functional programming style or just with @code{map}, @code{for-each} | |
2668 | or similar is typical. | |
2669 | ||
2670 | @example | |
2671 | (map (cut * 2 <>) '(1 2 3 4)) | |
2672 | ||
2673 | (for-each (cut write <> my-port) my-list) | |
2674 | @end example | |
2675 | @end deffn | |
b0b55bd6 | 2676 | |
620c8965 LC |
2677 | @node SRFI-30 |
2678 | @subsection SRFI-30 - Nested Multi-line Comments | |
2679 | @cindex SRFI-30 | |
2680 | ||
2681 | Starting from version 2.0, Guile's @code{read} supports SRFI-30/R6RS | |
2682 | nested multi-line comments by default, @ref{Block Comments}. | |
2683 | ||
8638c417 RB |
2684 | @node SRFI-31 |
2685 | @subsection SRFI-31 - A special form `rec' for recursive evaluation | |
2686 | @cindex SRFI-31 | |
7c2e18cd | 2687 | @cindex recursive expression |
8638c417 RB |
2688 | @findex rec |
2689 | ||
2690 | SRFI-31 defines a special form that can be used to create | |
2691 | self-referential expressions more conveniently. The syntax is as | |
2692 | follows: | |
2693 | ||
2694 | @example | |
2695 | @group | |
2696 | <rec expression> --> (rec <variable> <expression>) | |
2697 | <rec expression> --> (rec (<variable>+) <body>) | |
2698 | @end group | |
2699 | @end example | |
2700 | ||
2701 | The first syntax can be used to create self-referential expressions, | |
2702 | for example: | |
2703 | ||
2704 | @lisp | |
2705 | guile> (define tmp (rec ones (cons 1 (delay ones)))) | |
2706 | @end lisp | |
2707 | ||
2708 | The second syntax can be used to create anonymous recursive functions: | |
2709 | ||
2710 | @lisp | |
2711 | guile> (define tmp (rec (display-n item n) | |
2712 | (if (positive? n) | |
2713 | (begin (display n) (display-n (- n 1)))))) | |
2714 | guile> (tmp 42 3) | |
2715 | 424242 | |
2716 | guile> | |
2717 | @end lisp | |
12991fed | 2718 | |
eeadfda1 | 2719 | |
f50ca8da LC |
2720 | @node SRFI-34 |
2721 | @subsection SRFI-34 - Exception handling for programs | |
2722 | ||
2723 | @cindex SRFI-34 | |
2724 | Guile provides an implementation of | |
2725 | @uref{http://srfi.schemers.org/srfi-34/srfi-34.html, SRFI-34's exception | |
2726 | handling mechanisms} as an alternative to its own built-in mechanisms | |
2727 | (@pxref{Exceptions}). It can be made available as follows: | |
2728 | ||
2729 | @lisp | |
2730 | (use-modules (srfi srfi-34)) | |
2731 | @end lisp | |
2732 | ||
2733 | @c FIXME: Document it. | |
2734 | ||
2735 | ||
2736 | @node SRFI-35 | |
2737 | @subsection SRFI-35 - Conditions | |
2738 | ||
2739 | @cindex SRFI-35 | |
2740 | @cindex conditions | |
2741 | @cindex exceptions | |
2742 | ||
2743 | @uref{http://srfi.schemers.org/srfi-35/srfi-35.html, SRFI-35} implements | |
2744 | @dfn{conditions}, a data structure akin to records designed to convey | |
2745 | information about exceptional conditions between parts of a program. It | |
2746 | is normally used in conjunction with SRFI-34's @code{raise}: | |
2747 | ||
2748 | @lisp | |
2749 | (raise (condition (&message | |
2750 | (message "An error occurred")))) | |
2751 | @end lisp | |
2752 | ||
2753 | Users can define @dfn{condition types} containing arbitrary information. | |
2754 | Condition types may inherit from one another. This allows the part of | |
2755 | the program that handles (or ``catches'') conditions to get accurate | |
2756 | information about the exceptional condition that arose. | |
2757 | ||
2758 | SRFI-35 conditions are made available using: | |
2759 | ||
2760 | @lisp | |
2761 | (use-modules (srfi srfi-35)) | |
2762 | @end lisp | |
2763 | ||
2764 | The procedures available to manipulate condition types are the | |
2765 | following: | |
2766 | ||
2767 | @deffn {Scheme Procedure} make-condition-type id parent field-names | |
2768 | Return a new condition type named @var{id}, inheriting from | |
2769 | @var{parent}, and with the fields whose names are listed in | |
2770 | @var{field-names}. @var{field-names} must be a list of symbols and must | |
2771 | not contain names already used by @var{parent} or one of its supertypes. | |
2772 | @end deffn | |
2773 | ||
2774 | @deffn {Scheme Procedure} condition-type? obj | |
2775 | Return true if @var{obj} is a condition type. | |
2776 | @end deffn | |
2777 | ||
2778 | Conditions can be created and accessed with the following procedures: | |
2779 | ||
2780 | @deffn {Scheme Procedure} make-condition type . field+value | |
2781 | Return a new condition of type @var{type} with fields initialized as | |
2782 | specified by @var{field+value}, a sequence of field names (symbols) and | |
2783 | values as in the following example: | |
2784 | ||
2785 | @lisp | |
1317062f | 2786 | (let ((&ct (make-condition-type 'foo &condition '(a b c)))) |
f50ca8da LC |
2787 | (make-condition &ct 'a 1 'b 2 'c 3)) |
2788 | @end lisp | |
2789 | ||
2790 | Note that all fields of @var{type} and its supertypes must be specified. | |
2791 | @end deffn | |
2792 | ||
2793 | @deffn {Scheme Procedure} make-compound-condition . conditions | |
2794 | Return a new compound condition composed of @var{conditions}. The | |
2795 | returned condition has the type of each condition of @var{conditions} | |
2796 | (per @code{condition-has-type?}). | |
2797 | @end deffn | |
2798 | ||
2799 | @deffn {Scheme Procedure} condition-has-type? c type | |
2800 | Return true if condition @var{c} has type @var{type}. | |
2801 | @end deffn | |
2802 | ||
2803 | @deffn {Scheme Procedure} condition-ref c field-name | |
2804 | Return the value of the field named @var{field-name} from condition @var{c}. | |
2805 | ||
2806 | If @var{c} is a compound condition and several underlying condition | |
2807 | types contain a field named @var{field-name}, then the value of the | |
2808 | first such field is returned, using the order in which conditions were | |
2809 | passed to @var{make-compound-condition}. | |
2810 | @end deffn | |
2811 | ||
2812 | @deffn {Scheme Procedure} extract-condition c type | |
2813 | Return a condition of condition type @var{type} with the field values | |
2814 | specified by @var{c}. | |
2815 | ||
2816 | If @var{c} is a compound condition, extract the field values from the | |
2817 | subcondition belonging to @var{type} that appeared first in the call to | |
2818 | @code{make-compound-condition} that created the the condition. | |
2819 | @end deffn | |
2820 | ||
2821 | Convenience macros are also available to create condition types and | |
2822 | conditions. | |
2823 | ||
2824 | @deffn {library syntax} define-condition-type type supertype predicate field-spec... | |
2825 | Define a new condition type named @var{type} that inherits from | |
2826 | @var{supertype}. In addition, bind @var{predicate} to a type predicate | |
2827 | that returns true when passed a condition of type @var{type} or any of | |
2828 | its subtypes. @var{field-spec} must have the form @code{(field | |
2829 | accessor)} where @var{field} is the name of field of @var{type} and | |
2830 | @var{accessor} is the name of a procedure to access field @var{field} in | |
2831 | conditions of type @var{type}. | |
2832 | ||
2833 | The example below defines condition type @code{&foo}, inheriting from | |
2834 | @code{&condition} with fields @code{a}, @code{b} and @code{c}: | |
2835 | ||
2836 | @lisp | |
2837 | (define-condition-type &foo &condition | |
2838 | foo-condition? | |
2839 | (a foo-a) | |
2840 | (b foo-b) | |
2841 | (c foo-c)) | |
2842 | @end lisp | |
2843 | @end deffn | |
2844 | ||
2845 | @deffn {library syntax} condition type-field-bindings... | |
2846 | Return a new condition, or compound condition, initialized according to | |
2847 | @var{type-field-bindings}. Each @var{type-field-binding} must have the | |
2848 | form @code{(type field-specs...)}, where @var{type} is the name of a | |
2849 | variable bound to condition type; each @var{field-spec} must have the | |
2850 | form @code{(field-name value)} where @var{field-name} is a symbol | |
2851 | denoting the field being initialized to @var{value}. As for | |
2852 | @code{make-condition}, all fields must be specified. | |
2853 | ||
2854 | The following example returns a simple condition: | |
2855 | ||
2856 | @lisp | |
2857 | (condition (&message (message "An error occurred"))) | |
2858 | @end lisp | |
2859 | ||
2860 | The one below returns a compound condition: | |
2861 | ||
2862 | @lisp | |
2863 | (condition (&message (message "An error occurred")) | |
2864 | (&serious)) | |
2865 | @end lisp | |
2866 | @end deffn | |
2867 | ||
2868 | Finally, SRFI-35 defines a several standard condition types. | |
2869 | ||
2870 | @defvar &condition | |
2871 | This condition type is the root of all condition types. It has no | |
2872 | fields. | |
2873 | @end defvar | |
2874 | ||
2875 | @defvar &message | |
2876 | A condition type that carries a message describing the nature of the | |
2877 | condition to humans. | |
2878 | @end defvar | |
2879 | ||
2880 | @deffn {Scheme Procedure} message-condition? c | |
2881 | Return true if @var{c} is of type @code{&message} or one of its | |
2882 | subtypes. | |
2883 | @end deffn | |
2884 | ||
2885 | @deffn {Scheme Procedure} condition-message c | |
2886 | Return the message associated with message condition @var{c}. | |
2887 | @end deffn | |
2888 | ||
2889 | @defvar &serious | |
2890 | This type describes conditions serious enough that they cannot safely be | |
2891 | ignored. It has no fields. | |
2892 | @end defvar | |
2893 | ||
2894 | @deffn {Scheme Procedure} serious-condition? c | |
2895 | Return true if @var{c} is of type @code{&serious} or one of its | |
2896 | subtypes. | |
2897 | @end deffn | |
2898 | ||
2899 | @defvar &error | |
2900 | This condition describes errors, typically caused by something that has | |
2901 | gone wrong in the interaction of the program with the external world or | |
2902 | the user. | |
2903 | @end defvar | |
2904 | ||
2905 | @deffn {Scheme Procedure} error? c | |
2906 | Return true if @var{c} is of type @code{&error} or one of its subtypes. | |
2907 | @end deffn | |
2908 | ||
2909 | ||
d4c38221 LC |
2910 | @node SRFI-37 |
2911 | @subsection SRFI-37 - args-fold | |
2912 | @cindex SRFI-37 | |
2913 | ||
2914 | This is a processor for GNU @code{getopt_long}-style program | |
2915 | arguments. It provides an alternative, less declarative interface | |
2916 | than @code{getopt-long} in @code{(ice-9 getopt-long)} | |
2917 | (@pxref{getopt-long,,The (ice-9 getopt-long) Module}). Unlike | |
2918 | @code{getopt-long}, it supports repeated options and any number of | |
2919 | short and long names per option. Access it with: | |
2920 | ||
2921 | @lisp | |
2922 | (use-modules (srfi srfi-37)) | |
2923 | @end lisp | |
2924 | ||
2925 | @acronym{SRFI}-37 principally provides an @code{option} type and the | |
2926 | @code{args-fold} function. To use the library, create a set of | |
2927 | options with @code{option} and use it as a specification for invoking | |
2928 | @code{args-fold}. | |
2929 | ||
2930 | Here is an example of a simple argument processor for the typical | |
2931 | @samp{--version} and @samp{--help} options, which returns a backwards | |
2932 | list of files given on the command line: | |
2933 | ||
2934 | @lisp | |
2935 | (args-fold (cdr (program-arguments)) | |
2936 | (let ((display-and-exit-proc | |
2937 | (lambda (msg) | |
2938 | (lambda (opt name arg loads) | |
2939 | (display msg) (quit))))) | |
2940 | (list (option '(#\v "version") #f #f | |
2941 | (display-and-exit-proc "Foo version 42.0\n")) | |
2942 | (option '(#\h "help") #f #f | |
2943 | (display-and-exit-proc | |
2944 | "Usage: foo scheme-file ...")))) | |
2945 | (lambda (opt name arg loads) | |
2946 | (error "Unrecognized option `~A'" name)) | |
2947 | (lambda (op loads) (cons op loads)) | |
2948 | '()) | |
2949 | @end lisp | |
2950 | ||
2951 | @deffn {Scheme Procedure} option names required-arg? optional-arg? processor | |
2952 | Return an object that specifies a single kind of program option. | |
2953 | ||
2954 | @var{names} is a list of command-line option names, and should consist of | |
2955 | characters for traditional @code{getopt} short options and strings for | |
2956 | @code{getopt_long}-style long options. | |
2957 | ||
2958 | @var{required-arg?} and @var{optional-arg?} are mutually exclusive; | |
2959 | one or both must be @code{#f}. If @var{required-arg?}, the option | |
2960 | must be followed by an argument on the command line, such as | |
2961 | @samp{--opt=value} for long options, or an error will be signalled. | |
2962 | If @var{optional-arg?}, an argument will be taken if available. | |
2963 | ||
2964 | @var{processor} is a procedure that takes at least 3 arguments, called | |
2965 | when @code{args-fold} encounters the option: the containing option | |
2966 | object, the name used on the command line, and the argument given for | |
2967 | the option (or @code{#f} if none). The rest of the arguments are | |
2968 | @code{args-fold} ``seeds'', and the @var{processor} should return | |
2969 | seeds as well. | |
2970 | @end deffn | |
2971 | ||
2972 | @deffn {Scheme Procedure} option-names opt | |
2973 | @deffnx {Scheme Procedure} option-required-arg? opt | |
2974 | @deffnx {Scheme Procedure} option-optional-arg? opt | |
2975 | @deffnx {Scheme Procedure} option-processor opt | |
2976 | Return the specified field of @var{opt}, an option object, as | |
2977 | described above for @code{option}. | |
2978 | @end deffn | |
2979 | ||
2980 | @deffn {Scheme Procedure} args-fold args options unrecognized-option-proc operand-proc seeds @dots{} | |
2981 | Process @var{args}, a list of program arguments such as that returned | |
2982 | by @code{(cdr (program-arguments))}, in order against @var{options}, a | |
2983 | list of option objects as described above. All functions called take | |
2984 | the ``seeds'', or the last multiple-values as multiple arguments, | |
2985 | starting with @var{seeds}, and must return the new seeds. Return the | |
2986 | final seeds. | |
2987 | ||
2988 | Call @code{unrecognized-option-proc}, which is like an option object's | |
2989 | processor, for any options not found in @var{options}. | |
2990 | ||
2991 | Call @code{operand-proc} with any items on the command line that are | |
2992 | not named options. This includes arguments after @samp{--}. It is | |
2993 | called with the argument in question, as well as the seeds. | |
2994 | @end deffn | |
2995 | ||
2996 | ||
eeadfda1 KR |
2997 | @node SRFI-39 |
2998 | @subsection SRFI-39 - Parameters | |
2999 | @cindex SRFI-39 | |
3000 | @cindex parameter object | |
3001 | @tindex Parameter | |
3002 | ||
3003 | This SRFI provides parameter objects, which implement dynamically | |
3004 | bound locations for values. The functions below are available from | |
3005 | ||
3006 | @example | |
3007 | (use-modules (srfi srfi-39)) | |
3008 | @end example | |
3009 | ||
3010 | A parameter object is a procedure. Called with no arguments it | |
3011 | returns its value, called with one argument it sets the value. | |
3012 | ||
3013 | @example | |
3014 | (define my-param (make-parameter 123)) | |
3015 | (my-param) @result{} 123 | |
3016 | (my-param 456) | |
3017 | (my-param) @result{} 456 | |
3018 | @end example | |
3019 | ||
3020 | The @code{parameterize} special form establishes new locations for | |
3021 | parameters, those new locations having effect within the dynamic scope | |
3022 | of the @code{parameterize} body. Leaving restores the previous | |
3023 | locations, or re-entering through a saved continuation will again use | |
3024 | the new locations. | |
3025 | ||
3026 | @example | |
3027 | (parameterize ((my-param 789)) | |
3028 | (my-param) @result{} 789 | |
3029 | ) | |
3030 | (my-param) @result{} 456 | |
3031 | @end example | |
3032 | ||
3033 | Parameters are like dynamically bound variables in other Lisp dialets. | |
3034 | They allow an application to establish parameter settings (as the name | |
3035 | suggests) just for the execution of a particular bit of code, | |
3036 | restoring when done. Examples of such parameters might be | |
3037 | case-sensitivity for a search, or a prompt for user input. | |
3038 | ||
3039 | Global variables are not as good as parameter objects for this sort of | |
3040 | thing. Changes to them are visible to all threads, but in Guile | |
3041 | parameter object locations are per-thread, thereby truely limiting the | |
3042 | effect of @code{parameterize} to just its dynamic execution. | |
3043 | ||
3044 | Passing arguments to functions is thread-safe, but that soon becomes | |
3045 | tedious when there's more than a few or when they need to pass down | |
3046 | through several layers of calls before reaching the point they should | |
3047 | affect. And introducing a new setting to existing code is often | |
3048 | easier with a parameter object than adding arguments. | |
3049 | ||
3050 | ||
3051 | @sp 1 | |
3052 | @defun make-parameter init [converter] | |
3053 | Return a new parameter object, with initial value @var{init}. | |
3054 | ||
3055 | A parameter object is a procedure. When called @code{(param)} it | |
3056 | returns its value, or a call @code{(param val)} sets its value. For | |
3057 | example, | |
3058 | ||
3059 | @example | |
3060 | (define my-param (make-parameter 123)) | |
3061 | (my-param) @result{} 123 | |
3062 | ||
3063 | (my-param 456) | |
3064 | (my-param) @result{} 456 | |
3065 | @end example | |
3066 | ||
3067 | If a @var{converter} is given, then a call @code{(@var{converter} | |
3068 | val)} is made for each value set, its return is the value stored. | |
3069 | Such a call is made for the @var{init} initial value too. | |
3070 | ||
3071 | A @var{converter} allows values to be validated, or put into a | |
3072 | canonical form. For example, | |
3073 | ||
3074 | @example | |
3075 | (define my-param (make-parameter 123 | |
3076 | (lambda (val) | |
3077 | (if (not (number? val)) | |
3078 | (error "must be a number")) | |
3079 | (inexact->exact val)))) | |
3080 | (my-param 0.75) | |
3081 | (my-param) @result{} 3/4 | |
3082 | @end example | |
3083 | @end defun | |
3084 | ||
3085 | @deffn {library syntax} parameterize ((param value) @dots{}) body @dots{} | |
3086 | Establish a new dynamic scope with the given @var{param}s bound to new | |
3087 | locations and set to the given @var{value}s. @var{body} is evaluated | |
3088 | in that environment, the result is the return from the last form in | |
3089 | @var{body}. | |
3090 | ||
3091 | Each @var{param} is an expression which is evaluated to get the | |
3092 | parameter object. Often this will just be the name of a variable | |
3093 | holding the object, but it can be anything that evaluates to a | |
3094 | parameter. | |
3095 | ||
3096 | The @var{param} expressions and @var{value} expressions are all | |
3097 | evaluated before establishing the new dynamic bindings, and they're | |
3098 | evaluated in an unspecified order. | |
3099 | ||
3100 | For example, | |
3101 | ||
3102 | @example | |
3103 | (define prompt (make-parameter "Type something: ")) | |
3104 | (define (get-input) | |
3105 | (display (prompt)) | |
3106 | ...) | |
3107 | ||
3108 | (parameterize ((prompt "Type a number: ")) | |
3109 | (get-input) | |
3110 | ...) | |
3111 | @end example | |
3112 | @end deffn | |
3113 | ||
3114 | @deffn {Parameter object} current-input-port [new-port] | |
3115 | @deffnx {Parameter object} current-output-port [new-port] | |
3116 | @deffnx {Parameter object} current-error-port [new-port] | |
3117 | This SRFI extends the core @code{current-input-port} and | |
3118 | @code{current-output-port}, making them parameter objects. The | |
3119 | Guile-specific @code{current-error-port} is extended too, for | |
3120 | consistency. (@pxref{Default Ports}.) | |
3121 | ||
3122 | This is an upwardly compatible extension, a plain call like | |
3123 | @code{(current-input-port)} still returns the current input port, and | |
3124 | @code{set-current-input-port} can still be used. But the port can now | |
3125 | also be set with @code{(current-input-port my-port)} and bound | |
3126 | dynamically with @code{parameterize}. | |
3127 | @end deffn | |
3128 | ||
3129 | @defun with-parameters* param-list value-list thunk | |
3130 | Establish a new dynamic scope, as per @code{parameterize} above, | |
3131 | taking parameters from @var{param-list} and corresponding values from | |
3132 | @var{values-list}. A call @code{(@var{thunk})} is made in the new | |
3133 | scope and the result from that @var{thunk} is the return from | |
3134 | @code{with-parameters*}. | |
3135 | ||
3136 | This function is a Guile-specific addition to the SRFI, it's similar | |
b4fddbbe | 3137 | to the core @code{with-fluids*} (@pxref{Fluids and Dynamic States}). |
eeadfda1 KR |
3138 | @end defun |
3139 | ||
3140 | ||
3141 | @sp 1 | |
b4fddbbe MV |
3142 | Parameter objects are implemented using fluids (@pxref{Fluids and |
3143 | Dynamic States}), so each dynamic state has it's own parameter | |
3144 | locations. That includes the separate locations when outside any | |
3145 | @code{parameterize} form. When a parameter is created it gets a | |
3146 | separate initial location in each dynamic state, all initialized to | |
3147 | the given @var{init} value. | |
3148 | ||
3149 | As alluded to above, because each thread usually has a separate | |
3150 | dynamic state, each thread has it's own locations behind parameter | |
3151 | objects, and changes in one thread are not visible to any other. When | |
3152 | a new dynamic state or thread is created, the values of parameters in | |
3153 | the originating context are copied, into new locations. | |
eeadfda1 KR |
3154 | |
3155 | SRFI-39 doesn't specify the interaction between parameter objects and | |
3156 | threads, so the threading behaviour described here should be regarded | |
3157 | as Guile-specific. | |
3158 | ||
3159 | ||
4ea9becb KR |
3160 | @node SRFI-55 |
3161 | @subsection SRFI-55 - Requiring Features | |
3162 | @cindex SRFI-55 | |
3163 | ||
3164 | SRFI-55 provides @code{require-extension} which is a portable | |
3165 | mechanism to load selected SRFI modules. This is implemented in the | |
3166 | Guile core, there's no module needed to get SRFI-55 itself. | |
3167 | ||
3168 | @deffn {library syntax} require-extension clause@dots{} | |
3169 | Require each of the given @var{clause} features, throwing an error if | |
3170 | any are unavailable. | |
3171 | ||
3172 | A @var{clause} is of the form @code{(@var{identifier} arg...)}. The | |
3173 | only @var{identifier} currently supported is @code{srfi} and the | |
3174 | arguments are SRFI numbers. For example to get SRFI-1 and SRFI-6, | |
3175 | ||
3176 | @example | |
3177 | (require-extension (srfi 1 6)) | |
3178 | @end example | |
3179 | ||
3180 | @code{require-extension} can only be used at the top-level. | |
3181 | ||
3182 | A Guile-specific program can simply @code{use-modules} to load SRFIs | |
3183 | not already in the core, @code{require-extension} is for programs | |
3184 | designed to be portable to other Scheme implementations. | |
3185 | @end deffn | |
3186 | ||
3187 | ||
8503beb8 KR |
3188 | @node SRFI-60 |
3189 | @subsection SRFI-60 - Integers as Bits | |
3190 | @cindex SRFI-60 | |
3191 | @cindex integers as bits | |
3192 | @cindex bitwise logical | |
3193 | ||
3194 | This SRFI provides various functions for treating integers as bits and | |
3195 | for bitwise manipulations. These functions can be obtained with, | |
3196 | ||
3197 | @example | |
3198 | (use-modules (srfi srfi-60)) | |
3199 | @end example | |
3200 | ||
3201 | Integers are treated as infinite precision twos-complement, the same | |
3202 | as in the core logical functions (@pxref{Bitwise Operations}). And | |
3203 | likewise bit indexes start from 0 for the least significant bit. The | |
3204 | following functions in this SRFI are already in the Guile core, | |
3205 | ||
3206 | @quotation | |
3207 | @code{logand}, | |
3208 | @code{logior}, | |
3209 | @code{logxor}, | |
3210 | @code{lognot}, | |
3211 | @code{logtest}, | |
3212 | @code{logcount}, | |
3213 | @code{integer-length}, | |
3214 | @code{logbit?}, | |
3215 | @code{ash} | |
3216 | @end quotation | |
3217 | ||
3218 | @sp 1 | |
3219 | @defun bitwise-and n1 ... | |
3220 | @defunx bitwise-ior n1 ... | |
3221 | @defunx bitwise-xor n1 ... | |
3222 | @defunx bitwise-not n | |
3223 | @defunx any-bits-set? j k | |
3224 | @defunx bit-set? index n | |
3225 | @defunx arithmetic-shift n count | |
3226 | @defunx bit-field n start end | |
3227 | @defunx bit-count n | |
3228 | Aliases for @code{logand}, @code{logior}, @code{logxor}, | |
3229 | @code{lognot}, @code{logtest}, @code{logbit?}, @code{ash}, | |
3230 | @code{bit-extract} and @code{logcount} respectively. | |
3231 | ||
3232 | Note that the name @code{bit-count} conflicts with @code{bit-count} in | |
3233 | the core (@pxref{Bit Vectors}). | |
3234 | @end defun | |
3235 | ||
3236 | @defun bitwise-if mask n1 n0 | |
3237 | @defunx bitwise-merge mask n1 n0 | |
3238 | Return an integer with bits selected from @var{n1} and @var{n0} | |
3239 | according to @var{mask}. Those bits where @var{mask} has 1s are taken | |
3240 | from @var{n1}, and those where @var{mask} has 0s are taken from | |
3241 | @var{n0}. | |
3242 | ||
3243 | @example | |
3244 | (bitwise-if 3 #b0101 #b1010) @result{} 9 | |
3245 | @end example | |
3246 | @end defun | |
3247 | ||
3248 | @defun log2-binary-factors n | |
3249 | @defunx first-set-bit n | |
3250 | Return a count of how many factors of 2 are present in @var{n}. This | |
3251 | is also the bit index of the lowest 1 bit in @var{n}. If @var{n} is | |
3252 | 0, the return is @math{-1}. | |
3253 | ||
3254 | @example | |
3255 | (log2-binary-factors 6) @result{} 1 | |
3256 | (log2-binary-factors -8) @result{} 3 | |
3257 | @end example | |
3258 | @end defun | |
3259 | ||
3260 | @defun copy-bit index n newbit | |
3261 | Return @var{n} with the bit at @var{index} set according to | |
3262 | @var{newbit}. @var{newbit} should be @code{#t} to set the bit to 1, | |
3263 | or @code{#f} to set it to 0. Bits other than at @var{index} are | |
3264 | unchanged in the return. | |
3265 | ||
3266 | @example | |
3267 | (copy-bit 1 #b0101 #t) @result{} 7 | |
3268 | @end example | |
3269 | @end defun | |
3270 | ||
3271 | @defun copy-bit-field n newbits start end | |
3272 | Return @var{n} with the bits from @var{start} (inclusive) to @var{end} | |
3273 | (exclusive) changed to the value @var{newbits}. | |
3274 | ||
3275 | The least significant bit in @var{newbits} goes to @var{start}, the | |
3276 | next to @math{@var{start}+1}, etc. Anything in @var{newbits} past the | |
3277 | @var{end} given is ignored. | |
3278 | ||
3279 | @example | |
3280 | (copy-bit-field #b10000 #b11 1 3) @result{} #b10110 | |
3281 | @end example | |
3282 | @end defun | |
3283 | ||
3284 | @defun rotate-bit-field n count start end | |
3285 | Return @var{n} with the bit field from @var{start} (inclusive) to | |
3286 | @var{end} (exclusive) rotated upwards by @var{count} bits. | |
3287 | ||
3288 | @var{count} can be positive or negative, and it can be more than the | |
3289 | field width (it'll be reduced modulo the width). | |
3290 | ||
3291 | @example | |
3292 | (rotate-bit-field #b0110 2 1 4) @result{} #b1010 | |
3293 | @end example | |
3294 | @end defun | |
3295 | ||
3296 | @defun reverse-bit-field n start end | |
3297 | Return @var{n} with the bits from @var{start} (inclusive) to @var{end} | |
3298 | (exclusive) reversed. | |
3299 | ||
3300 | @example | |
3301 | (reverse-bit-field #b101001 2 4) @result{} #b100101 | |
3302 | @end example | |
3303 | @end defun | |
3304 | ||
3305 | @defun integer->list n [len] | |
3306 | Return bits from @var{n} in the form of a list of @code{#t} for 1 and | |
3307 | @code{#f} for 0. The least significant @var{len} bits are returned, | |
3308 | and the first list element is the most significant of those bits. If | |
3309 | @var{len} is not given, the default is @code{(integer-length @var{n})} | |
3310 | (@pxref{Bitwise Operations}). | |
3311 | ||
3312 | @example | |
3313 | (integer->list 6) @result{} (#t #t #f) | |
3314 | (integer->list 1 4) @result{} (#f #f #f #t) | |
3315 | @end example | |
3316 | @end defun | |
3317 | ||
3318 | @defun list->integer lst | |
3319 | @defunx booleans->integer bool@dots{} | |
3320 | Return an integer formed bitwise from the given @var{lst} list of | |
3321 | booleans, or for @code{booleans->integer} from the @var{bool} | |
3322 | arguments. | |
3323 | ||
3324 | Each boolean is @code{#t} for a 1 and @code{#f} for a 0. The first | |
3325 | element becomes the most significant bit in the return. | |
3326 | ||
3327 | @example | |
3328 | (list->integer '(#t #f #t #f)) @result{} 10 | |
3329 | @end example | |
3330 | @end defun | |
3331 | ||
3332 | ||
43ed3b69 MV |
3333 | @node SRFI-61 |
3334 | @subsection SRFI-61 - A more general @code{cond} clause | |
3335 | ||
3336 | This SRFI extends RnRS @code{cond} to support test expressions that | |
3337 | return multiple values, as well as arbitrary definitions of test | |
3338 | success. SRFI 61 is implemented in the Guile core; there's no module | |
3339 | needed to get SRFI-61 itself. Extended @code{cond} is documented in | |
3340 | @ref{if cond case,, Simple Conditional Evaluation}. | |
3341 | ||
3342 | ||
1317062f LC |
3343 | @node SRFI-69 |
3344 | @subsection SRFI-69 - Basic hash tables | |
3345 | @cindex SRFI-69 | |
3346 | ||
3347 | This is a portable wrapper around Guile's built-in hash table and weak | |
3348 | table support. @xref{Hash Tables}, for information on that built-in | |
3349 | support. Above that, this hash-table interface provides association | |
3350 | of equality and hash functions with tables at creation time, so | |
3351 | variants of each function are not required, as well as a procedure | |
3352 | that takes care of most uses for Guile hash table handles, which this | |
3353 | SRFI does not provide as such. | |
3354 | ||
3355 | Access it with: | |
3356 | ||
3357 | @lisp | |
3358 | (use-modules (srfi srfi-69)) | |
3359 | @end lisp | |
3360 | ||
3361 | @menu | |
3362 | * SRFI-69 Creating hash tables:: | |
3363 | * SRFI-69 Accessing table items:: | |
3364 | * SRFI-69 Table properties:: | |
3365 | * SRFI-69 Hash table algorithms:: | |
3366 | @end menu | |
3367 | ||
3368 | @node SRFI-69 Creating hash tables | |
3369 | @subsubsection Creating hash tables | |
3370 | ||
3371 | @deffn {Scheme Procedure} make-hash-table [equal-proc hash-proc #:weak weakness start-size] | |
3372 | Create and answer a new hash table with @var{equal-proc} as the | |
3373 | equality function and @var{hash-proc} as the hashing function. | |
3374 | ||
3375 | By default, @var{equal-proc} is @code{equal?}. It can be any | |
3376 | two-argument procedure, and should answer whether two keys are the | |
3377 | same for this table's purposes. | |
3378 | ||
3379 | My default @var{hash-proc} assumes that @code{equal-proc} is no | |
3380 | coarser than @code{equal?} unless it is literally @code{string-ci=?}. | |
3381 | If provided, @var{hash-proc} should be a two-argument procedure that | |
3382 | takes a key and the current table size, and answers a reasonably good | |
3383 | hash integer between 0 (inclusive) and the size (exclusive). | |
3384 | ||
3385 | @var{weakness} should be @code{#f} or a symbol indicating how ``weak'' | |
3386 | the hash table is: | |
3387 | ||
3388 | @table @code | |
3389 | @item #f | |
3390 | An ordinary non-weak hash table. This is the default. | |
3391 | ||
3392 | @item key | |
3393 | When the key has no more non-weak references at GC, remove that entry. | |
3394 | ||
3395 | @item value | |
3396 | When the value has no more non-weak references at GC, remove that | |
3397 | entry. | |
3398 | ||
3399 | @item key-or-value | |
3400 | When either has no more non-weak references at GC, remove the | |
3401 | association. | |
3402 | @end table | |
3403 | ||
3404 | As a legacy of the time when Guile couldn't grow hash tables, | |
3405 | @var{start-size} is an optional integer argument that specifies the | |
dfe8c13b LC |
3406 | approximate starting size for the hash table, which will be rounded to |
3407 | an algorithmically-sounder number. | |
1317062f LC |
3408 | @end deffn |
3409 | ||
dfe8c13b | 3410 | By @dfn{coarser} than @code{equal?}, we mean that for all @var{x} and |
1317062f LC |
3411 | @var{y} values where @code{(@var{equal-proc} @var{x} @var{y})}, |
3412 | @code{(equal? @var{x} @var{y})} as well. If that does not hold for | |
3413 | your @var{equal-proc}, you must provide a @var{hash-proc}. | |
3414 | ||
3415 | In the case of weak tables, remember that @dfn{references} above | |
3416 | always refers to @code{eq?}-wise references. Just because you have a | |
3417 | reference to some string @code{"foo"} doesn't mean that an association | |
3418 | with key @code{"foo"} in a weak-key table @emph{won't} be collected; | |
3419 | it only counts as a reference if the two @code{"foo"}s are @code{eq?}, | |
3420 | regardless of @var{equal-proc}. As such, it is usually only sensible | |
3421 | to use @code{eq?} and @code{hashq} as the equivalence and hash | |
3422 | functions for a weak table. @xref{Weak References}, for more | |
3423 | information on Guile's built-in weak table support. | |
3424 | ||
3425 | @deffn {Scheme Procedure} alist->hash-table alist [equal-proc hash-proc #:weak weakness start-size] | |
3426 | As with @code{make-hash-table}, but initialize it with the | |
3427 | associations in @var{alist}. Where keys are repeated in @var{alist}, | |
3428 | the leftmost association takes precedence. | |
3429 | @end deffn | |
3430 | ||
3431 | @node SRFI-69 Accessing table items | |
3432 | @subsubsection Accessing table items | |
3433 | ||
3434 | @deffn {Scheme Procedure} hash-table-ref table key [default-thunk] | |
3435 | @deffnx {Scheme Procedure} hash-table-ref/default table key default | |
3436 | Answer the value associated with @var{key} in @var{table}. If | |
3437 | @var{key} is not present, answer the result of invoking the thunk | |
3438 | @var{default-thunk}, which signals an error instead by default. | |
3439 | ||
3440 | @code{hash-table-ref/default} is a variant that requires a third | |
3441 | argument, @var{default}, and answers @var{default} itself instead of | |
3442 | invoking it. | |
3443 | @end deffn | |
3444 | ||
3445 | @deffn {Scheme Procedure} hash-table-set! table key new-value | |
3446 | Set @var{key} to @var{new-value} in @var{table}. | |
3447 | @end deffn | |
3448 | ||
3449 | @deffn {Scheme Procedure} hash-table-delete! table key | |
3450 | Remove the association of @var{key} in @var{table}, if present. If | |
3451 | absent, do nothing. | |
3452 | @end deffn | |
3453 | ||
3454 | @deffn {Scheme Procedure} hash-table-exists? table key | |
3455 | Answer whether @var{key} has an association in @var{table}. | |
3456 | @end deffn | |
3457 | ||
3458 | @deffn {Scheme Procedure} hash-table-update! table key modifier [default-thunk] | |
3459 | @deffnx {Scheme Procedure} hash-table-update!/default table key modifier default | |
3460 | Replace @var{key}'s associated value in @var{table} by invoking | |
3461 | @var{modifier} with one argument, the old value. | |
3462 | ||
3463 | If @var{key} is not present, and @var{default-thunk} is provided, | |
3464 | invoke it with no arguments to get the ``old value'' to be passed to | |
3465 | @var{modifier} as above. If @var{default-thunk} is not provided in | |
3466 | such a case, signal an error. | |
3467 | ||
3468 | @code{hash-table-update!/default} is a variant that requires the | |
3469 | fourth argument, which is used directly as the ``old value'' rather | |
3470 | than as a thunk to be invoked to retrieve the ``old value''. | |
3471 | @end deffn | |
3472 | ||
3473 | @node SRFI-69 Table properties | |
3474 | @subsubsection Table properties | |
3475 | ||
3476 | @deffn {Scheme Procedure} hash-table-size table | |
3477 | Answer the number of associations in @var{table}. This is guaranteed | |
3478 | to run in constant time for non-weak tables. | |
3479 | @end deffn | |
3480 | ||
3481 | @deffn {Scheme Procedure} hash-table-keys table | |
3482 | Answer an unordered list of the keys in @var{table}. | |
3483 | @end deffn | |
3484 | ||
3485 | @deffn {Scheme Procedure} hash-table-values table | |
3486 | Answer an unordered list of the values in @var{table}. | |
3487 | @end deffn | |
3488 | ||
3489 | @deffn {Scheme Procedure} hash-table-walk table proc | |
3490 | Invoke @var{proc} once for each association in @var{table}, passing | |
3491 | the key and value as arguments. | |
3492 | @end deffn | |
3493 | ||
3494 | @deffn {Scheme Procedure} hash-table-fold table proc init | |
3495 | Invoke @code{(@var{proc} @var{key} @var{value} @var{previous})} for | |
3496 | each @var{key} and @var{value} in @var{table}, where @var{previous} is | |
3497 | the result of the previous invocation, using @var{init} as the first | |
3498 | @var{previous} value. Answer the final @var{proc} result. | |
3499 | @end deffn | |
3500 | ||
3501 | @deffn {Scheme Procedure} hash-table->alist table | |
3502 | Answer an alist where each association in @var{table} is an | |
3503 | association in the result. | |
3504 | @end deffn | |
3505 | ||
3506 | @node SRFI-69 Hash table algorithms | |
3507 | @subsubsection Hash table algorithms | |
3508 | ||
3509 | Each hash table carries an @dfn{equivalence function} and a @dfn{hash | |
3510 | function}, used to implement key lookups. Beginning users should | |
3511 | follow the rules for consistency of the default @var{hash-proc} | |
3512 | specified above. Advanced users can use these to implement their own | |
3513 | equivalence and hash functions for specialized lookup semantics. | |
3514 | ||
3515 | @deffn {Scheme Procedure} hash-table-equivalence-function hash-table | |
3516 | @deffnx {Scheme Procedure} hash-table-hash-function hash-table | |
3517 | Answer the equivalence and hash function of @var{hash-table}, respectively. | |
3518 | @end deffn | |
3519 | ||
3520 | @deffn {Scheme Procedure} hash obj [size] | |
3521 | @deffnx {Scheme Procedure} string-hash obj [size] | |
3522 | @deffnx {Scheme Procedure} string-ci-hash obj [size] | |
3523 | @deffnx {Scheme Procedure} hash-by-identity obj [size] | |
3524 | Answer a hash value appropriate for equality predicate @code{equal?}, | |
3525 | @code{string=?}, @code{string-ci=?}, and @code{eq?}, respectively. | |
3526 | @end deffn | |
3527 | ||
3528 | @code{hash} is a backwards-compatible replacement for Guile's built-in | |
3529 | @code{hash}. | |
3530 | ||
189681f5 LC |
3531 | @node SRFI-88 |
3532 | @subsection SRFI-88 Keyword Objects | |
3533 | @cindex SRFI-88 | |
3534 | @cindex keyword objects | |
3535 | ||
e36280cb | 3536 | @uref{http://srfi.schemers.org/srfi-88/srfi-88.html, SRFI-88} provides |
189681f5 LC |
3537 | @dfn{keyword objects}, which are equivalent to Guile's keywords |
3538 | (@pxref{Keywords}). SRFI-88 keywords can be entered using the | |
3539 | @dfn{postfix keyword syntax}, which consists of an identifier followed | |
3540 | by @code{:} (@pxref{Reader options, @code{postfix} keyword syntax}). | |
3541 | SRFI-88 can be made available with: | |
3542 | ||
3543 | @example | |
3544 | (use-modules (srfi srfi-88)) | |
3545 | @end example | |
3546 | ||
3547 | Doing so installs the right reader option for keyword syntax, using | |
3548 | @code{(read-set! keywords 'postfix)}. It also provides the procedures | |
3549 | described below. | |
3550 | ||
3551 | @deffn {Scheme Procedure} keyword? obj | |
3552 | Return @code{#t} if @var{obj} is a keyword. This is the same procedure | |
3553 | as the same-named built-in procedure (@pxref{Keyword Procedures, | |
3554 | @code{keyword?}}). | |
3555 | ||
3556 | @example | |
3557 | (keyword? foo:) @result{} #t | |
3558 | (keyword? 'foo:) @result{} #t | |
3559 | (keyword? "foo") @result{} #f | |
3560 | @end example | |
3561 | @end deffn | |
3562 | ||
3563 | @deffn {Scheme Procedure} keyword->string kw | |
3564 | Return the name of @var{kw} as a string, i.e., without the trailing | |
3565 | colon. The returned string may not be modified, e.g., with | |
3566 | @code{string-set!}. | |
3567 | ||
3568 | @example | |
3569 | (keyword->string foo:) @result{} "foo" | |
3570 | @end example | |
3571 | @end deffn | |
3572 | ||
3573 | @deffn {Scheme Procedure} string->keyword str | |
3574 | Return the keyword object whose name is @var{str}. | |
3575 | ||
3576 | @example | |
3577 | (keyword->string (string->keyword "a b c")) @result{} "a b c" | |
3578 | @end example | |
3579 | @end deffn | |
3580 | ||
922d417b JG |
3581 | @node SRFI-98 |
3582 | @subsection SRFI-98 Accessing environment variables. | |
3583 | @cindex SRFI-98 | |
3584 | @cindex environment variables | |
3585 | ||
3586 | This is a portable wrapper around Guile's built-in support for | |
3587 | interacting with the current environment, @xref{Runtime Environment}. | |
3588 | ||
3589 | @deffn {Scheme Procedure} get-environment-variable name | |
3590 | Returns a string containing the value of the environment variable | |
3591 | given by the string @code{name}, or @code{#f} if the named | |
3592 | environment variable is not found. This is equivalent to | |
3593 | @code{(getenv name)}. | |
3594 | @end deffn | |
3595 | ||
3596 | @deffn {Scheme Procedure} get-environment-variables | |
3597 | Returns the names and values of all the environment variables as an | |
3598 | association list in which both the keys and the values are strings. | |
3599 | @end deffn | |
1317062f | 3600 | |
12991fed | 3601 | @c srfi-modules.texi ends here |
193239f1 KR |
3602 | |
3603 | @c Local Variables: | |
3604 | @c TeX-master: "guile.texi" | |
3605 | @c End: |