Commit | Line | Data |
---|---|---|
b2cbe8d8 | 1 | Guile NEWS --- history of user-visible changes. |
fe11efee | 2 | Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc. |
5c54da76 JB |
3 | See the end for copying conditions. |
4 | ||
1e457544 | 5 | Please send Guile bug reports to bug-guile@gnu.org. |
5ebbe4ef | 6 | |
5c54da76 | 7 | \f |
ef283979 AW |
8 | (During the 1.9 series, we will keep an incremental NEWS for the latest |
9 | prerelease, and a full NEWS corresponding to 1.8 -> 2.0.) | |
10 | ||
5adcdb65 MG |
11 | Changes in 1.9.2 (since the 1.9.1 prerelease): |
12 | ||
acf04ab4 | 13 | ** VM speed improvements |
5adcdb65 | 14 | |
acf04ab4 AW |
15 | Closures now copy the free variables that they need into a flat vector |
16 | instead of capturing all heap-allocated variables. This speeds up access | |
17 | to free variables, avoids unnecessary garbage retention, and allows all | |
18 | variables to be allocated on the stack. | |
5adcdb65 | 19 | |
acf04ab4 AW |
20 | Variables which are `set!' are now allocated on the stack, but in |
21 | "boxes". This allows a more uniform local variable allocation | |
22 | discipline, and allows faster access to these variables. | |
5adcdb65 | 23 | |
acf04ab4 AW |
24 | The VM has new special-case operations, `add1' and `sub1'. |
25 | ||
26 | ** VM robustness improvements | |
5adcdb65 | 27 | |
acf04ab4 AW |
28 | The maximum number of live local variables has been increased from 256 |
29 | to 65535. | |
ef283979 | 30 | |
acf04ab4 AW |
31 | The default VM stack size is 64 kilo-words, up from 16 kilo-words. This |
32 | allows more programs to execute in the default stack space. In the | |
33 | future we will probably implement extensible stacks via overflow | |
34 | handlers. | |
ef283979 | 35 | |
acf04ab4 AW |
36 | Some lingering cases in which the VM could perform unaligned accesses |
37 | have been fixed. | |
ef283979 | 38 | |
acf04ab4 AW |
39 | The address range for relative jumps has been expanded from 16-bit |
40 | addresses to 19-bit addresses via 8-byte alignment of jump targets. This | |
41 | will probably change to a 24-bit byte-addressable strategy before Guile | |
42 | 2.0. | |
19fef497 | 43 | |
acf04ab4 | 44 | ** Compiler optimizations |
19fef497 | 45 | |
acf04ab4 AW |
46 | Procedures bound by `letrec' are no longer allocated on the heap, |
47 | subject to a few constraints. In many cases, procedures bound by | |
48 | `letrec' and `let' can be rendered inline to their parent function, with | |
49 | loop detection for mutually tail-recursive procedures. | |
19fef497 | 50 | |
acf04ab4 | 51 | Unreferenced variables are now optimized away. |
19fef497 | 52 | |
acf04ab4 | 53 | ** Compiler robustness |
19fef497 | 54 | |
acf04ab4 AW |
55 | Guile may now warn about unused lexically-bound variables. Pass |
56 | `-Wunused-variable' to `guile-tools compile', or `#:warnings | |
57 | (unused-variable)' within the #:opts argument to the `compile' procedure | |
58 | from `(system base compile)'. | |
19fef497 | 59 | |
acf04ab4 | 60 | ** Incomplete support for Unicode characters and strings |
19fef497 | 61 | |
acf04ab4 AW |
62 | Preliminary support for Unicode has landed. Characters may be entered in |
63 | octal format via e.g. `#\454', or created via (integer->char 300). A hex | |
64 | external representation will probably be introduced at some point. | |
19fef497 | 65 | |
acf04ab4 AW |
66 | Internally, strings are now represented either in the `latin-1' |
67 | encoding, one byte per character, or in UTF-32, with four bytes per | |
68 | character. Strings manage their own allocation, switching if needed. | |
19fef497 | 69 | |
acf04ab4 AW |
70 | Currently no locale conversion is performed. Extended characters may be |
71 | written in a string using the hexadecimal escapes `\xXX', `\uXXXX', or | |
72 | `\UXXXXXX', for 8-bit, 16-bit, or 24-bit codepoints, respectively. | |
19fef497 | 73 | |
acf04ab4 AW |
74 | This support is obviously incomplete. Many C functions have not yet been |
75 | updated to deal with the new representations. Users are advised to wait | |
76 | for the next release for more serious use of Unicode strings. | |
19fef497 | 77 | |
acf04ab4 | 78 | ** `defined?' may accept a module as its second argument |
19fef497 | 79 | |
acf04ab4 | 80 | Previously it only accepted internal structures from the evaluator. |
19fef497 | 81 | |
acf04ab4 | 82 | ** `let-values' is now implemented with a hygienic macro |
19fef497 | 83 | |
acf04ab4 AW |
84 | This could have implications discussed below in the NEWS entry titled, |
85 | "Lexical bindings introduced by hygienic macros may not be referenced by | |
86 | nonhygienic macros". | |
19fef497 | 87 | |
acf04ab4 | 88 | ** Global variables `scm_charnames' and `scm_charnums' are removed |
19fef497 | 89 | |
acf04ab4 AW |
90 | These variables contained the names of control characters and were |
91 | used when writing characters. While these were global, they were | |
92 | never intended to be public API. They have been replaced with private | |
93 | functions. | |
19fef497 | 94 | |
acf04ab4 | 95 | ** EBCDIC support is removed |
ba4c43dc | 96 | |
acf04ab4 AW |
97 | There was an EBCDIC compile flag that altered some of the character |
98 | processing. It appeared that full EBCDIC support was never completed | |
99 | and was unmaintained. | |
19fef497 | 100 | |
54dd0ca5 LC |
101 | ** Packaging changes |
102 | ||
103 | Guile now provides `guile-2.0.pc' (used by pkg-config) instead of | |
104 | `guile-1.8.pc'. | |
105 | ||
acf04ab4 AW |
106 | ** And of course, the usual collection of bugfixes |
107 | ||
19fef497 AW |
108 | Interested users should see the ChangeLog for more information. |
109 | ||
acf04ab4 | 110 | |
ef283979 | 111 | Changes in 1.9.x (since the 1.8.x series): |
96b73e84 AW |
112 | |
113 | * New modules (see the manual for details) | |
114 | ||
115 | ** `(srfi srfi-18)', more sophisticated multithreading support | |
116 | ** `(ice-9 i18n)', internationalization support | |
117 | ** `(rnrs bytevector)', the R6RS bytevector API | |
93617170 | 118 | ** `(rnrs io ports)', a subset of the R6RS I/O port API |
96b73e84 AW |
119 | ** `(system xref)', a cross-referencing facility (FIXME undocumented) |
120 | ||
121 | * Changes to the stand-alone interpreter | |
122 | ||
123 | ** Guile now can compile Scheme to bytecode for a custom virtual machine. | |
124 | ||
125 | Compiled code loads much faster than Scheme source code, and runs around | |
126 | 3 or 4 times as fast, generating much less garbage in the process. | |
fa1804e9 AW |
127 | |
128 | ** The stack limit is now initialized from the environment. | |
129 | ||
130 | If getrlimit(2) is available and a stack limit is set, Guile will set | |
131 | its stack limit to 80% of the rlimit. Otherwise the limit is 160000 | |
132 | words, a four-fold increase from the earlier default limit. | |
133 | ||
96b73e84 AW |
134 | ** New environment variables: GUILE_LOAD_COMPILED_PATH, |
135 | GUILE_SYSTEM_LOAD_COMPILED_PATH | |
fa1804e9 | 136 | |
96b73e84 AW |
137 | GUILE_LOAD_COMPILED_PATH is for compiled files what GUILE_LOAD_PATH is |
138 | for source files. It is a different path, however, because compiled | |
139 | files are architecture-specific. GUILE_SYSTEM_LOAD_COMPILED_PATH is like | |
140 | GUILE_SYSTEM_PATH. | |
141 | ||
142 | ** New read-eval-print loop (REPL) implementation | |
143 | ||
144 | Running Guile with no arguments drops the user into the new REPL. While | |
145 | it is self-documenting to an extent, the new REPL has not yet been | |
146 | documented in the manual. This will be fixed before 2.0. | |
147 | ||
148 | ** New `guile-tools' commands: `compile', `disassemble' | |
149 | ||
93617170 | 150 | Pass the `--help' command-line option to these commands for more |
96b73e84 AW |
151 | information. |
152 | ||
153 | * Changes to Scheme functions and syntax | |
154 | ||
155 | ** Procedure removed: `the-environment' | |
156 | ||
157 | This procedure was part of the interpreter's execution model, and does | |
158 | not apply to the compiler. | |
fa1804e9 | 159 | |
93617170 | 160 | ** Files loaded with `primitive-load-path' will now be compiled |
fa1804e9 AW |
161 | automatically. |
162 | ||
163 | If a compiled .go file corresponding to a .scm file is not found or is | |
164 | not fresh, the .scm file will be compiled on the fly, and the resulting | |
165 | .go file stored away. An advisory note will be printed on the console. | |
166 | ||
167 | Note that this mechanism depends on preservation of the .scm and .go | |
168 | modification times; if the .scm or .go files are moved after | |
169 | installation, care should be taken to preserve their original | |
170 | timestamps. | |
171 | ||
19fef497 AW |
172 | Autocompiled files will be stored in the $XDG_CACHE_HOME/guile/ccache |
173 | directory, where $XDG_CACHE_HOME defaults to ~/.cache. This directory | |
174 | will be created if needed. | |
fa1804e9 AW |
175 | |
176 | To inhibit autocompilation, set the GUILE_AUTO_COMPILE environment | |
177 | variable to 0, or pass --no-autocompile on the Guile command line. | |
178 | ||
96b73e84 AW |
179 | Note that there is currently a bug here: automatic compilation will |
180 | sometimes be attempted when it shouldn't. | |
fa1804e9 | 181 | |
96b73e84 AW |
182 | For example, the old (lang elisp) modules are meant to be interpreted, |
183 | not compiled. This bug will be fixed before 2.0. FIXME 2.0: Should say | |
184 | something here about module-transformer called for compile. | |
fa1804e9 | 185 | |
96b73e84 | 186 | ** New POSIX procedures: `getrlimit' and `setrlimit' |
fa1804e9 | 187 | |
96b73e84 AW |
188 | Note however that the interface of these functions is likely to change |
189 | in the next prerelease. | |
fa1804e9 | 190 | |
96b73e84 | 191 | ** New procedure in `(oops goops)': `method-formals' |
fa1804e9 | 192 | |
96b73e84 AW |
193 | ** BUG: (procedure-property func 'arity) does not work on compiled |
194 | procedures | |
fa1804e9 | 195 | |
96b73e84 | 196 | This will be fixed one way or another before 2.0. |
fa1804e9 | 197 | |
96b73e84 AW |
198 | ** New procedures in (ice-9 session): `add-value-help-handler!', |
199 | `remove-value-help-handler!', `add-name-help-handler!' | |
200 | `remove-name-help-handler!', `procedure-arguments', | |
fa1804e9 | 201 | |
96b73e84 AW |
202 | The value and name help handlers provide some minimal extensibility to |
203 | the help interface. Guile-lib's `(texinfo reflection)' uses them, for | |
204 | example, to make stexinfo help documentation available. See those | |
205 | procedures' docstrings for more information. | |
206 | ||
207 | `procedure-arguments' describes the arguments that a procedure can take, | |
208 | combining arity and formals. For example: | |
209 | ||
210 | (procedure-arguments resolve-interface) | |
211 | => ((required . (name)) (rest . args)) | |
fa1804e9 | 212 | |
96b73e84 AW |
213 | Additionally, `module-commentary' is now publically exported from |
214 | `(ice-9 session). | |
215 | ||
216 | ** Deprecated: `procedure->memoizing-macro', `procedure->syntax' | |
217 | ||
218 | These procedures will not work with syncase expansion, and indeed are | |
219 | not used in the normal course of Guile. They are still used by the old | |
220 | Emacs Lisp support, however. | |
221 | ||
222 | ** New language: ECMAScript | |
223 | ||
224 | Guile now ships with one other high-level language supported, | |
225 | ECMAScript. The goal is to support all of version 3.1 of the standard, | |
226 | but not all of the libraries are there yet. This support is not yet | |
227 | documented; ask on the mailing list if you are interested. | |
228 | ||
19fef497 AW |
229 | ** New language: Brainfuck |
230 | ||
231 | Brainfuck is a toy language that closely models Turing machines. Guile's | |
232 | brainfuck compiler is meant to be an example of implementing other | |
233 | languages. See the manual for details, or | |
234 | http://en.wikipedia.org/wiki/Brainfuck for more information about the | |
235 | Brainfuck language itself. | |
236 | ||
96b73e84 AW |
237 | ** Defmacros may now have docstrings. |
238 | ||
239 | Indeed, any macro may have a docstring. `object-documentation' from | |
240 | `(ice-9 documentation)' may be used to retrieve the docstring, once you | |
241 | have a macro value -- but see the above note about first-class macros. | |
242 | Docstrings are associated with the syntax transformer procedures. | |
243 | ||
244 | ** The psyntax expander now knows how to interpret the @ and @@ special | |
245 | forms. | |
246 | ||
247 | ** The psyntax expander is now hygienic with respect to modules. | |
248 | ||
249 | Free variables in a macro are scoped in the module that the macro was | |
250 | defined in, not in the module the macro is used in. For example, code | |
251 | like this works now: | |
252 | ||
253 | (define-module (foo) #:export (bar)) | |
254 | (define (helper x) ...) | |
255 | (define-syntax bar | |
256 | (syntax-rules () ((_ x) (helper x)))) | |
257 | ||
258 | (define-module (baz) #:use-module (foo)) | |
259 | (bar qux) | |
260 | ||
261 | It used to be you had to export `helper' from `(foo)' as well. | |
262 | Thankfully, this has been fixed. | |
263 | ||
264 | ** New function, `procedure-module' | |
265 | ||
266 | While useful on its own, `procedure-module' is used by psyntax on syntax | |
267 | transformers to determine the module in which to scope introduced | |
268 | identifiers. | |
269 | ||
270 | ** `eval-case' has been deprecated, and replaced by `eval-when'. | |
271 | ||
272 | The semantics of `eval-when' are easier to understand. It is still | |
273 | missing documentation, however. | |
274 | ||
275 | ** Guile is now more strict about prohibiting definitions in expression | |
276 | contexts. | |
277 | ||
278 | Although previous versions of Guile accepted it, the following | |
279 | expression is not valid, in R5RS or R6RS: | |
280 | ||
281 | (if test (define foo 'bar) (define foo 'baz)) | |
282 | ||
283 | In this specific case, it would be better to do: | |
284 | ||
285 | (define foo (if test 'bar 'baz)) | |
286 | ||
287 | It is certainly possible to circumvent this resriction with e.g. | |
288 | `(module-define! (current-module) 'foo 'baz)'. We would appreciate | |
289 | feedback about this change (a consequence of using psyntax as the | |
290 | default expander), and may choose to revisit this situation before 2.0 | |
291 | in response to user feedback. | |
292 | ||
293 | ** Defmacros must now produce valid Scheme expressions. | |
294 | ||
295 | It used to be that defmacros could unquote in Scheme values, as a way of | |
296 | supporting partial evaluation, and avoiding some hygiene issues. For | |
297 | example: | |
298 | ||
299 | (define (helper x) ...) | |
300 | (define-macro (foo bar) | |
301 | `(,helper ,bar)) | |
302 | ||
303 | Assuming this macro is in the `(baz)' module, the direct translation of | |
304 | this code would be: | |
305 | ||
306 | (define (helper x) ...) | |
307 | (define-macro (foo bar) | |
308 | `((@@ (baz) helper) ,bar)) | |
309 | ||
310 | Of course, one could just use a hygienic macro instead: | |
311 | ||
312 | (define-syntax foo | |
313 | (syntax-rules () | |
314 | ((_ bar) (helper bar)))) | |
315 | ||
316 | ** Guile's psyntax now supports docstrings and internal definitions. | |
317 | ||
318 | The following Scheme is not strictly legal: | |
319 | ||
320 | (define (foo) | |
321 | "bar" | |
322 | (define (baz) ...) | |
323 | (baz)) | |
324 | ||
325 | However its intent is fairly clear. Guile interprets "bar" to be the | |
326 | docstring of `foo', and the definition of `baz' is still in definition | |
327 | context. | |
328 | ||
329 | ** Macros need to be defined before their first use. | |
330 | ||
331 | It used to be that with lazy memoization, this might work: | |
332 | ||
333 | (define (foo x) | |
334 | (ref x)) | |
335 | (define-macro (ref x) x) | |
336 | (foo 1) => 1 | |
337 | ||
338 | But now, the body of `foo' is interpreted to mean a call to the toplevel | |
339 | `ref' function, instead of a macro expansion. The solution is to define | |
340 | macros before code that uses them. | |
341 | ||
342 | ** Functions needed by macros at expand-time need to be present at | |
343 | expand-time. | |
344 | ||
345 | For example, this code will work at the REPL: | |
346 | ||
347 | (define (double-helper x) (* x x)) | |
348 | (define-macro (double-literal x) (double-helper x)) | |
349 | (double-literal 2) => 4 | |
350 | ||
351 | But it will not work when a file is compiled, because the definition of | |
352 | `double-helper' is not present at expand-time. The solution is to wrap | |
353 | the definition of `double-helper' in `eval-when': | |
354 | ||
355 | (eval-when (load compile eval) | |
356 | (define (double-helper x) (* x x))) | |
357 | (define-macro (double-literal x) (double-helper x)) | |
358 | (double-literal 2) => 4 | |
359 | ||
360 | See the (currently missing) documentation for eval-when for more | |
361 | information. | |
362 | ||
363 | ** New variable, %pre-modules-transformer | |
364 | ||
365 | Need to document this one some more. | |
366 | ||
367 | ** Temporarily removed functions: `macroexpand', `macroexpand-1' | |
368 | ||
369 | `macroexpand' will be added back before 2.0. It is unclear how to | |
370 | implement `macroexpand-1' with syntax-case, though PLT Scheme does prove | |
371 | that it is possible. | |
fa1804e9 AW |
372 | |
373 | ** New reader macros: #' #` #, #,@ | |
374 | ||
375 | These macros translate, respectively, to `syntax', `quasisyntax', | |
376 | `unsyntax', and `unsyntax-splicing'. See the R6RS for more information. | |
377 | These reader macros may be overridden by `read-hash-extend'. | |
378 | ||
379 | ** Incompatible change to #' | |
380 | ||
381 | Guile did have a #' hash-extension, by default, which just returned the | |
382 | subsequent datum: #'foo => foo. In the unlikely event that anyone | |
383 | actually used this, this behavior may be reinstated via the | |
384 | `read-hash-extend' mechanism. | |
385 | ||
386 | ** Scheme expresssions may be commented out with #; | |
387 | ||
93617170 LC |
388 | #; comments out an entire expression. See SRFI-62 or the R6RS for more |
389 | information. | |
fa1804e9 | 390 | |
93617170 | 391 | ** `make-stack' with a tail-called procedural narrowing argument no longer |
fa1804e9 AW |
392 | works (with compiled procedures) |
393 | ||
394 | It used to be the case that a captured stack could be narrowed to select | |
395 | calls only up to or from a certain procedure, even if that procedure | |
396 | already tail-called another procedure. This was because the debug | |
397 | information from the original procedure was kept on the stack. | |
398 | ||
399 | Now with the new compiler, the stack only contains active frames from | |
400 | the current continuation. A narrow to a procedure that is not in the | |
401 | stack will result in an empty stack. To fix this, narrow to a procedure | |
402 | that is active in the current continuation, or narrow to a specific | |
403 | number of stack frames. | |
404 | ||
405 | ** backtraces through compiled procedures only show procedures that are | |
406 | active in the current continuation | |
407 | ||
408 | Similarly to the previous issue, backtraces in compiled code may be | |
409 | different from backtraces in interpreted code. There are no semantic | |
410 | differences, however. Please mail bug-guile@gnu.org if you see any | |
411 | deficiencies with Guile's backtraces. | |
412 | ||
413 | ** syntax-rules and syntax-case macros now propagate source information | |
414 | through to the expanded code | |
415 | ||
416 | This should result in better backtraces. | |
417 | ||
418 | ** The currying behavior of `define' has been removed. | |
419 | ||
420 | Before, `(define ((f a) b) (* a b))' would translate to | |
421 | ||
422 | (define f (lambda (a) (lambda (b) (* a b)))) | |
423 | ||
93617170 | 424 | Now a syntax error is signaled, as this syntax is not supported by |
fa1804e9 AW |
425 | default. If there is sufficient demand, this syntax can be supported |
426 | again by default. | |
427 | ||
428 | ** All modules have names now | |
429 | ||
430 | Before, you could have anonymous modules: modules without names. Now, | |
431 | because of hygiene and macros, all modules have names. If a module was | |
432 | created without a name, the first time `module-name' is called on it, a | |
433 | fresh name will be lazily generated for it. | |
434 | ||
435 | ** Many syntax errors have different texts now | |
436 | ||
437 | Syntax errors still throw to the `syntax-error' key, but the arguments | |
438 | are often different now. Perhaps in the future, Guile will switch to | |
93617170 | 439 | using standard SRFI-35 conditions. |
fa1804e9 AW |
440 | |
441 | ** Returning multiple values to compiled code will silently truncate the | |
442 | values to the expected number | |
443 | ||
444 | For example, the interpreter would raise an error evaluating the form, | |
445 | `(+ (values 1 2) (values 3 4))', because it would see the operands as | |
446 | being two compound "values" objects, to which `+' does not apply. | |
447 | ||
448 | The compiler, on the other hand, receives multiple values on the stack, | |
449 | not as a compound object. Given that it must check the number of values | |
450 | anyway, if too many values are provided for a continuation, it chooses | |
451 | to truncate those values, effectively evaluating `(+ 1 3)' instead. | |
452 | ||
453 | The idea is that the semantics that the compiler implements is more | |
454 | intuitive, and the use of the interpreter will fade out with time. | |
455 | This behavior is allowed both by the R5RS and the R6RS. | |
456 | ||
457 | ** Multiple values in compiled code are not represented by compound | |
458 | objects | |
459 | ||
460 | This change may manifest itself in the following situation: | |
461 | ||
462 | (let ((val (foo))) (do-something) val) | |
463 | ||
464 | In the interpreter, if `foo' returns multiple values, multiple values | |
465 | are produced from the `let' expression. In the compiler, those values | |
466 | are truncated to the first value, and that first value is returned. In | |
467 | the compiler, if `foo' returns no values, an error will be raised, while | |
468 | the interpreter would proceed. | |
469 | ||
470 | Both of these behaviors are allowed by R5RS and R6RS. The compiler's | |
471 | behavior is more correct, however. If you wish to preserve a potentially | |
472 | multiply-valued return, you will need to set up a multiple-value | |
473 | continuation, using `call-with-values'. | |
474 | ||
475 | ** Defmacros are now implemented in terms of syntax-case. | |
476 | ||
477 | The practical ramification of this is that the `defmacro?' predicate has | |
478 | been removed, along with `defmacro-transformer', `macro-table', | |
479 | `xformer-table', `assert-defmacro?!', `set-defmacro-transformer!' and | |
480 | `defmacro:transformer'. This is because defmacros are simply macros. If | |
481 | any of these procedures provided useful facilities to you, we encourage | |
482 | you to contact the Guile developers. | |
483 | ||
484 | ** psyntax is now the default expander | |
485 | ||
486 | Scheme code is now expanded by default by the psyntax hygienic macro | |
487 | expander. Expansion is performed completely before compilation or | |
488 | interpretation. | |
489 | ||
490 | Notably, syntax errors will be signalled before interpretation begins. | |
491 | In the past, many syntax errors were only detected at runtime if the | |
492 | code in question was memoized. | |
493 | ||
494 | As part of its expansion, psyntax renames all lexically-bound | |
495 | identifiers. Original identifier names are preserved and given to the | |
496 | compiler, but the interpreter will see the renamed variables, e.g., | |
497 | `x432' instead of `x'. | |
498 | ||
499 | Note that the psyntax that Guile uses is a fork, as Guile already had | |
500 | modules before incompatible modules were added to psyntax -- about 10 | |
501 | years ago! Thus there are surely a number of bugs that have been fixed | |
502 | in psyntax since then. If you find one, please notify bug-guile@gnu.org. | |
503 | ||
504 | ** syntax-rules and syntax-case are available by default. | |
505 | ||
506 | There is no longer any need to import the `(ice-9 syncase)' module | |
507 | (which is now deprecated). The expander may be invoked directly via | |
508 | `sc-expand', though it is normally searched for via the current module | |
509 | transformer. | |
510 | ||
511 | Also, the helper routines for syntax-case are available in the default | |
512 | environment as well: `syntax->datum', `datum->syntax', | |
513 | `bound-identifier=?', `free-identifier=?', `generate-temporaries', | |
514 | `identifier?', and `syntax-violation'. See the R6RS for documentation. | |
515 | ||
516 | ** Lexical bindings introduced by hygienic macros may not be referenced | |
517 | by nonhygienic macros. | |
518 | ||
519 | If a lexical binding is introduced by a hygienic macro, it may not be | |
520 | referenced by a nonhygienic macro. For example, this works: | |
521 | ||
522 | (let () | |
523 | (define-macro (bind-x val body) | |
524 | `(let ((x ,val)) ,body)) | |
525 | (define-macro (ref x) | |
526 | x) | |
527 | (bind-x 10 (ref x))) | |
528 | ||
529 | But this does not: | |
530 | ||
531 | (let () | |
532 | (define-syntax bind-x | |
533 | (syntax-rules () | |
534 | ((_ val body) (let ((x val)) body)))) | |
535 | (define-macro (ref x) | |
536 | x) | |
537 | (bind-x 10 (ref x))) | |
538 | ||
539 | It is not normal to run into this situation with existing code. However, | |
540 | as code is ported over from defmacros to syntax-case, it is possible to | |
541 | run into situations like this. In the future, Guile will probably port | |
542 | its `while' macro to syntax-case, which makes this issue one to know | |
543 | about. | |
544 | ||
545 | ** Macros may no longer be referenced as first-class values. | |
546 | ||
547 | In the past, you could evaluate e.g. `if', and get its macro value. Now, | |
548 | expanding this form raises a syntax error. | |
549 | ||
550 | Macros still /exist/ as first-class values, but they must be | |
551 | /referenced/ via the module system, e.g. `(module-ref (current-module) | |
552 | 'if)'. | |
553 | ||
554 | This decision may be revisited before the 2.0 release. Feedback welcome | |
555 | to guile-devel@gnu.org (subscription required) or bug-guile@gnu.org (no | |
556 | subscription required). | |
557 | ||
558 | ** New macro type: syncase-macro | |
559 | ||
560 | XXX Need to decide whether to document this for 2.0, probably should: | |
561 | make-syncase-macro, make-extended-syncase-macro, macro-type, | |
562 | syncase-macro-type, syncase-macro-binding | |
563 | ||
93617170 LC |
564 | ** A new `memoize-symbol' evaluator trap has been added. |
565 | ||
566 | This trap can be used for efficiently implementing a Scheme code | |
567 | coverage. | |
fa1804e9 | 568 | |
96b73e84 | 569 | ** Duplicate bindings among used modules are resolved lazily. |
93617170 | 570 | |
96b73e84 | 571 | This slightly improves program startup times. |
fa1804e9 | 572 | |
96b73e84 | 573 | ** New thread cancellation and thread cleanup API |
93617170 | 574 | |
96b73e84 | 575 | See `cancel-thread', `set-thread-cleanup!', and `thread-cleanup'. |
fa1804e9 | 576 | |
96b73e84 | 577 | ** Fix bad interaction between `false-if-exception' and stack-call. |
fa1804e9 | 578 | |
96b73e84 AW |
579 | Exceptions thrown by `false-if-exception' were erronously causing the |
580 | stack to be saved, causing later errors to show the incorrectly-saved | |
581 | backtrace. This has been fixed. | |
fa1804e9 | 582 | |
96b73e84 | 583 | ** New global variables: %load-compiled-path, %load-compiled-extensions |
fa1804e9 | 584 | |
96b73e84 | 585 | These are analogous to %load-path and %load-extensions. |
fa1804e9 | 586 | |
96b73e84 | 587 | ** New procedure, `make-promise' |
fa1804e9 | 588 | |
96b73e84 | 589 | `(make-promise (lambda () foo))' is equivalent to `(delay foo)'. |
fa1804e9 | 590 | |
96b73e84 | 591 | ** New entry into %guile-build-info: `ccachedir' |
fa1804e9 | 592 | |
96b73e84 | 593 | ** Fix bug in `module-bound?'. |
fa1804e9 | 594 | |
96b73e84 AW |
595 | `module-bound?' was returning true if a module did have a local |
596 | variable, but one that was unbound, but another imported module bound | |
597 | the variable. This was an error, and was fixed. | |
fa1804e9 | 598 | |
96b73e84 | 599 | ** `(ice-9 syncase)' has been deprecated. |
fa1804e9 | 600 | |
96b73e84 AW |
601 | As syntax-case is available by default, importing `(ice-9 syncase)' has |
602 | no effect, and will trigger a deprecation warning. | |
fa1804e9 | 603 | |
96b73e84 | 604 | * Changes to the C interface |
fa1804e9 | 605 | |
96b73e84 | 606 | ** The GH interface (deprecated in version 1.6, 2001) was removed. |
fa1804e9 | 607 | |
96b73e84 | 608 | ** Internal `scm_i_' functions now have "hidden" linkage with GCC/ELF |
fa1804e9 | 609 | |
96b73e84 AW |
610 | This makes these internal functions technically not callable from |
611 | application code. | |
fa1804e9 | 612 | |
96b73e84 AW |
613 | ** Functions for handling `scm_option' now no longer require an argument |
614 | indicating length of the `scm_t_option' array. | |
fa1804e9 | 615 | |
96b73e84 | 616 | ** scm_primitive_load_path has additional argument, exception_on_error |
fa1804e9 | 617 | |
96b73e84 | 618 | ** New C function: scm_module_public_interface |
a4f1c77d | 619 | |
96b73e84 | 620 | This procedure corresponds to Scheme's `module-public-interface'. |
24d6fae8 | 621 | |
93617170 LC |
622 | ** `scm_stat' has an additional argument, `exception_on_error' |
623 | ** `scm_primitive_load_path' has an additional argument `exception_on_not_found' | |
24d6fae8 | 624 | |
f1ce9199 LC |
625 | ** `scm_set_port_seek' and `scm_set_port_truncate' use the `scm_t_off' type |
626 | ||
627 | Previously they would use the `off_t' type, which is fragile since its | |
628 | definition depends on the application's value for `_FILE_OFFSET_BITS'. | |
629 | ||
ba4c43dc LC |
630 | ** The `long_long' C type, deprecated in 1.8, has been removed |
631 | ||
a4f1c77d | 632 | * Changes to the distribution |
6caac03c | 633 | |
53befeb7 NJ |
634 | ** Guile's license is now LGPLv3+ |
635 | ||
636 | In other words the GNU Lesser General Public License, version 3 or | |
637 | later (at the discretion of each person that chooses to redistribute | |
638 | part of Guile). | |
639 | ||
96b73e84 | 640 | ** `guile-config' will be deprecated in favor of `pkg-config' |
8a9faebc | 641 | |
96b73e84 | 642 | `guile-config' has been rewritten to get its information from |
93617170 | 643 | `pkg-config', so this should be a transparent change. Note however that |
96b73e84 AW |
644 | guile.m4 has yet to be modified to call pkg-config instead of |
645 | guile-config. | |
2e77f720 | 646 | |
54dd0ca5 LC |
647 | ** Guile now provides `guile-2.0.pc' instead of `guile-1.8.pc' |
648 | ||
649 | Programs that use `pkg-config' to find Guile or one of its Autoconf | |
650 | macros should now require `guile-2.0' instead of `guile-1.8'. | |
651 | ||
96b73e84 | 652 | ** New installation directory: $(pkglibdir)/1.9/ccache |
62560650 | 653 | |
96b73e84 AW |
654 | If $(libdir) is /usr/lib, for example, Guile will install its .go files |
655 | to /usr/lib/guile/1.9/ccache. These files are architecture-specific. | |
89bc270d | 656 | |
96b73e84 | 657 | ** New dependency: GNU libunistring. |
32e29e24 | 658 | |
96b73e84 AW |
659 | See http://www.gnu.org/software/libunistring/. We hope to merge in |
660 | Unicode support in the next prerelease. | |
32e29e24 | 661 | |
a4f1c77d | 662 | |
dc686d7b | 663 | \f |
9957b1c7 LC |
664 | Changes in 1.8.8 (since 1.8.7) |
665 | ||
666 | * Bugs fixed | |
667 | ||
668 | ** Fix possible buffer overruns when parsing numbers | |
669 | ||
670 | \f | |
dc686d7b NJ |
671 | Changes in 1.8.7 (since 1.8.6) |
672 | ||
922d417b JG |
673 | * New modules (see the manual for details) |
674 | ||
675 | ** `(srfi srfi-98)', an interface to access environment variables | |
676 | ||
dc686d7b NJ |
677 | * Bugs fixed |
678 | ||
f5851b89 | 679 | ** Fix compilation with `--disable-deprecated' |
dc686d7b | 680 | ** Fix %fast-slot-ref/set!, to avoid possible segmentation fault |
cbee5075 | 681 | ** Fix MinGW build problem caused by HAVE_STRUCT_TIMESPEC confusion |
ab878b0f | 682 | ** Fix build problem when scm_t_timespec is different from struct timespec |
95a040cd | 683 | ** Fix build when compiled with -Wundef -Werror |
1bcf7993 | 684 | ** More build fixes for `alphaev56-dec-osf5.1b' (Tru64) |
5374ec9c | 685 | ** Build fixes for `powerpc-ibm-aix5.3.0.0' (AIX 5.3) |
5c006c3f LC |
686 | ** With GCC, always compile with `-mieee' on `alpha*' and `sh*' |
687 | ** Better diagnose broken `(strftime "%z" ...)' in `time.test' (bug #24130) | |
fc76c08d | 688 | ** Fix parsing of SRFI-88/postfix keywords longer than 128 characters |
40f89215 | 689 | ** Fix reading of complex numbers where both parts are inexact decimals |
d41668fa | 690 | |
ad5f5ada NJ |
691 | ** Allow @ macro to work with (ice-9 syncase) |
692 | ||
693 | Previously, use of the @ macro in a module whose code is being | |
694 | transformed by (ice-9 syncase) would cause an "Invalid syntax" error. | |
695 | Now it works as you would expect (giving the value of the specified | |
696 | module binding). | |
697 | ||
05588a1a LC |
698 | ** Have `scm_take_locale_symbol ()' return an interned symbol (bug #25865) |
699 | ||
d41668fa | 700 | \f |
8c40b75d LC |
701 | Changes in 1.8.6 (since 1.8.5) |
702 | ||
071bb6a8 LC |
703 | * New features (see the manual for details) |
704 | ||
705 | ** New convenience function `scm_c_symbol_length ()' | |
706 | ||
091baf9e NJ |
707 | ** Single stepping through code from Emacs |
708 | ||
709 | When you use GDS to evaluate Scheme code from Emacs, you can now use | |
710 | `C-u' to indicate that you want to single step through that code. See | |
711 | `Evaluating Scheme Code' in the manual for more details. | |
712 | ||
9e4db0ef LC |
713 | ** New "guile(1)" man page! |
714 | ||
242ebeaf LC |
715 | * Changes to the distribution |
716 | ||
717 | ** Automake's `AM_MAINTAINER_MODE' is no longer used | |
718 | ||
719 | Thus, the `--enable-maintainer-mode' configure option is no longer | |
720 | available: Guile is now always configured in "maintainer mode". | |
721 | ||
e0063477 LC |
722 | ** `ChangeLog' files are no longer updated |
723 | ||
724 | Instead, changes are detailed in the version control system's logs. See | |
725 | the top-level `ChangeLog' files for details. | |
726 | ||
727 | ||
8c40b75d LC |
728 | * Bugs fixed |
729 | ||
fd2b17b9 | 730 | ** `symbol->string' now returns a read-only string, as per R5RS |
c6333102 | 731 | ** Fix incorrect handling of the FLAGS argument of `fold-matches' |
589d9eb8 | 732 | ** `guile-config link' now prints `-L$libdir' before `-lguile' |
4a1db3a9 | 733 | ** Fix memory corruption involving GOOPS' `class-redefinition' |
191e7165 | 734 | ** Fix possible deadlock in `mutex-lock' |
95c6523b | 735 | ** Fix build issue on Tru64 and ia64-hp-hpux11.23 (`SCM_UNPACK' macro) |
4696a666 | 736 | ** Fix build issue on mips, mipsel, powerpc and ia64 (stack direction) |
450be18d | 737 | ** Fix build issue on hppa2.0w-hp-hpux11.11 (`dirent64' and `readdir64_r') |
88cefbc7 | 738 | ** Fix build issue on i386-unknown-freebsd7.0 ("break strict-aliasing rules") |
76dae881 | 739 | ** Fix misleading output from `(help rationalize)' |
5ea8e76e | 740 | ** Fix build failure on Debian hppa architecture (bad stack growth detection) |
1dd79792 | 741 | ** Fix `gcd' when called with a single, negative argument. |
d8b6e191 | 742 | ** Fix `Stack overflow' errors seen when building on some platforms |
ccf1ca4a LC |
743 | ** Fix bug when `scm_with_guile ()' was called several times from the |
744 | same thread | |
76350432 LC |
745 | ** The handler of SRFI-34 `with-exception-handler' is now invoked in the |
746 | dynamic environment of the call to `raise' | |
cb823e63 | 747 | ** Fix potential deadlock in `make-struct' |
691343ea | 748 | ** Fix compilation problem with libltdl from Libtool 2.2.x |
3ae3166b | 749 | ** Fix sloppy bound checking in `string-{ref,set!}' with the empty string |
6eadcdab | 750 | |
8c40b75d | 751 | \f |
5305df84 LC |
752 | Changes in 1.8.5 (since 1.8.4) |
753 | ||
4b824aae LC |
754 | * Infrastructure changes |
755 | ||
756 | ** Guile repository switched from CVS to Git | |
757 | ||
758 | The new repository can be accessed using | |
759 | "git-clone git://git.sv.gnu.org/guile.git", or can be browsed on-line at | |
760 | http://git.sv.gnu.org/gitweb/?p=guile.git . See `README' for details. | |
761 | ||
92826dd0 LC |
762 | ** Add support for `pkg-config' |
763 | ||
764 | See "Autoconf Support" in the manual for details. | |
765 | ||
189681f5 LC |
766 | * New modules (see the manual for details) |
767 | ||
768 | ** `(srfi srfi-88)' | |
769 | ||
ef4cbc08 LC |
770 | * New features (see the manual for details) |
771 | ||
772 | ** New `postfix' read option, for SRFI-88 keyword syntax | |
f5c2af4b | 773 | ** Some I/O primitives have been inlined, which improves I/O performance |
b20ef3a6 | 774 | ** New object-based traps infrastructure |
ef4cbc08 | 775 | |
b20ef3a6 NJ |
776 | This is a GOOPS-based infrastructure that builds on Guile's low-level |
777 | evaluator trap calls and facilitates the development of debugging | |
778 | features like single-stepping, breakpoints, tracing and profiling. | |
779 | See the `Traps' node of the manual for details. | |
780 | ||
781 | ** New support for working on Guile code from within Emacs | |
782 | ||
783 | Guile now incorporates the `GDS' library (previously distributed | |
784 | separately) for working on Guile code from within Emacs. See the | |
785 | `Using Guile In Emacs' node of the manual for details. | |
786 | ||
5305df84 LC |
787 | * Bugs fixed |
788 | ||
e27d2495 LC |
789 | ** `scm_add_slot ()' no longer segfaults (fixes bug #22369) |
790 | ** Fixed `(ice-9 match)' for patterns like `((_ ...) ...)' | |
791 | ||
792 | Previously, expressions like `(match '((foo) (bar)) (((_ ...) ...) #t))' | |
793 | would trigger an unbound variable error for `match:andmap'. | |
794 | ||
62c5382b LC |
795 | ** `(oop goops describe)' now properly provides the `describe' feature |
796 | ** Fixed `args-fold' from `(srfi srfi-37)' | |
797 | ||
798 | Previously, parsing short option names of argument-less options would | |
799 | lead to a stack overflow. | |
800 | ||
816e3edf | 801 | ** `(srfi srfi-35)' is now visible through `cond-expand' |
61b6542a | 802 | ** Fixed type-checking for the second argument of `eval' |
0fb11ae4 | 803 | ** Fixed type-checking for SRFI-1 `partition' |
f1c212b1 LC |
804 | ** Fixed `struct-ref' and `struct-set!' on "light structs" |
805 | ** Honor struct field access rights in GOOPS | |
be10cba8 | 806 | ** Changed the storage strategy of source properties, which fixes a deadlock |
979eade6 | 807 | ** Allow compilation of Guile-using programs in C99 mode with GCC 4.3 and later |
bfb64eb4 | 808 | ** Fixed build issue for GNU/Linux on IA64 |
fa80e280 | 809 | ** Fixed build issues on NetBSD 1.6 |
a2c25234 | 810 | ** Fixed build issue on Solaris 2.10 x86_64 |
3f520967 | 811 | ** Fixed build issue with DEC/Compaq/HP's compiler |
c2ad98ad LC |
812 | ** Fixed `scm_from_complex_double' build issue on FreeBSD |
813 | ** Fixed `alloca' build issue on FreeBSD 6 | |
a7286720 | 814 | ** Removed use of non-portable makefile constructs |
535b3592 | 815 | ** Fixed shadowing of libc's <random.h> on Tru64, which broke compilation |
eedcb08a | 816 | ** Make sure all tests honor `$TMPDIR' |
5305df84 LC |
817 | |
818 | \f | |
d41668fa LC |
819 | Changes in 1.8.4 (since 1.8.3) |
820 | ||
821 | * Bugs fixed | |
822 | ||
823 | ** CR (ASCII 0x0d) is (again) recognized as a token delimiter by the reader | |
6e14de7d NJ |
824 | ** Fixed a segmentation fault which occurred when displaying the |
825 | backtrace of a stack with a promise object (made by `delay') in it. | |
7d1fc872 | 826 | ** Make `accept' leave guile mode while blocking |
693758d5 | 827 | ** `scm_c_read ()' and `scm_c_write ()' now type-check their port argument |
378cc645 | 828 | ** Fixed a build problem on AIX (use of func_data identifier) |
15bd90ea NJ |
829 | ** Fixed a segmentation fault which occurred when hashx-ref or hashx-set! was |
830 | called with an associator proc that returns neither a pair nor #f. | |
3ac8359a | 831 | ** Secondary threads now always return a valid module for (current-module). |
d05bcb2e NJ |
832 | ** Avoid MacOS build problems caused by incorrect combination of "64" |
833 | system and library calls. | |
9a6fac59 | 834 | ** `guile-snarf' now honors `$TMPDIR' |
25a640ca | 835 | ** `guile-config compile' now reports CPPFLAGS used at compile-time |
7f74cf9a | 836 | ** Fixed build with Sun Studio (Solaris 9) |
4a19ed04 NJ |
837 | ** Fixed wrong-type-arg errors when creating zero length SRFI-4 |
838 | uniform vectors on AIX. | |
86a597f8 | 839 | ** Fixed a deadlock that occurs upon GC with multiple threads. |
4b26c03e | 840 | ** Fixed compile problem with GCC on Solaris and AIX (use of _Complex_I) |
d4a00708 | 841 | ** Fixed autotool-derived build problems on AIX 6.1. |
9a6fac59 | 842 | ** Fixed NetBSD/alpha support |
b226295a | 843 | ** Fixed MacOS build problem caused by use of rl_get_keymap(_name) |
7d1fc872 LC |
844 | |
845 | * New modules (see the manual for details) | |
846 | ||
847 | ** `(srfi srfi-69)' | |
d41668fa | 848 | |
b226295a NJ |
849 | * Documentation fixes and improvements |
850 | ||
851 | ** Removed premature breakpoint documentation | |
852 | ||
853 | The features described are not available in the series of 1.8.x | |
854 | releases, so the documentation was misleading and has been removed. | |
855 | ||
856 | ** More about Guile's default *random-state* variable | |
857 | ||
858 | ** GOOPS: more about how to use `next-method' | |
859 | ||
d3cf93bc NJ |
860 | * Changes to the distribution |
861 | ||
862 | ** Corrected a few files that referred incorrectly to the old GPL + special exception licence | |
863 | ||
864 | In fact Guile since 1.8.0 has been licensed with the GNU Lesser | |
865 | General Public License, and the few incorrect files have now been | |
866 | fixed to agree with the rest of the Guile distribution. | |
867 | ||
5e42b8e7 NJ |
868 | ** Removed unnecessary extra copies of COPYING* |
869 | ||
870 | The distribution now contains a single COPYING.LESSER at its top level. | |
871 | ||
a4f1c77d | 872 | \f |
d4c38221 LC |
873 | Changes in 1.8.3 (since 1.8.2) |
874 | ||
875 | * New modules (see the manual for details) | |
876 | ||
f50ca8da | 877 | ** `(srfi srfi-35)' |
d4c38221 LC |
878 | ** `(srfi srfi-37)' |
879 | ||
e08f3f7a LC |
880 | * Bugs fixed |
881 | ||
dc061a74 | 882 | ** The `(ice-9 slib)' module now works as expected |
e08f3f7a | 883 | ** Expressions like "(set! 'x #t)" no longer yield a crash |
d7c0c26d | 884 | ** Warnings about duplicate bindings now go to stderr |
1ac5fb45 | 885 | ** A memory leak in `make-socket-address' was fixed |
f43f3620 | 886 | ** Alignment issues (e.g., on SPARC) in network routines were fixed |
29776e85 | 887 | ** A threading issue that showed up at least on NetBSD was fixed |
66302618 | 888 | ** Build problems on Solaris and IRIX fixed |
e08f3f7a | 889 | |
1fdd8ffa LC |
890 | * Implementation improvements |
891 | ||
7ff6c169 | 892 | ** The reader is now faster, which reduces startup time |
1fdd8ffa LC |
893 | ** Procedures returned by `record-accessor' and `record-modifier' are faster |
894 | ||
d4c38221 | 895 | \f |
45c0ff10 KR |
896 | Changes in 1.8.2 (since 1.8.1): |
897 | ||
898 | * New procedures (see the manual for details) | |
899 | ||
900 | ** set-program-arguments | |
b3aa4626 | 901 | ** make-vtable |
45c0ff10 | 902 | |
9320e933 LC |
903 | * Incompatible changes |
904 | ||
905 | ** The body of a top-level `define' no longer sees the binding being created | |
906 | ||
907 | In a top-level `define', the binding being created is no longer visible | |
908 | from the `define' body. This breaks code like | |
909 | "(define foo (begin (set! foo 1) (+ foo 1)))", where `foo' is now | |
910 | unbound in the body. However, such code was not R5RS-compliant anyway, | |
911 | per Section 5.2.1. | |
912 | ||
45c0ff10 KR |
913 | * Bugs fixed |
914 | ||
915 | ** Fractions were not `equal?' if stored in unreduced form. | |
916 | (A subtle problem, since printing a value reduced it, making it work.) | |
917 | ** srfi-60 `copy-bit' failed on 64-bit systems | |
918 | ** "guile --use-srfi" option at the REPL can replace core functions | |
919 | (Programs run with that option were ok, but in the interactive REPL | |
920 | the core bindings got priority, preventing SRFI replacements or | |
921 | extensions.) | |
922 | ** `regexp-exec' doesn't abort() on #\nul in the input or bad flags arg | |
df449722 | 923 | ** `kill' on mingw throws an error for a PID other than oneself |
45c0ff10 KR |
924 | ** Procedure names are attached to procedure-with-setters |
925 | ** Array read syntax works with negative lower bound | |
926 | ** `array-in-bounds?' fix if an array has different lower bounds on each index | |
927 | ** `*' returns exact 0 for "(* inexact 0)" | |
928 | This follows what it always did for "(* 0 inexact)". | |
c122500a | 929 | ** SRFI-19: Value returned by `(current-time time-process)' was incorrect |
0867f7ba | 930 | ** SRFI-19: `date->julian-day' did not account for timezone offset |
a1ef7406 | 931 | ** `ttyname' no longer crashes when passed a non-tty argument |
27782696 | 932 | ** `inet-ntop' no longer crashes on SPARC when passed an `AF_INET' address |
0867f7ba | 933 | ** Small memory leaks have been fixed in `make-fluid' and `add-history' |
b1f57ea4 | 934 | ** GOOPS: Fixed a bug in `method-more-specific?' |
45c0ff10 | 935 | ** Build problems on Solaris fixed |
df449722 LC |
936 | ** Build problems on HP-UX IA64 fixed |
937 | ** Build problems on MinGW fixed | |
45c0ff10 KR |
938 | |
939 | \f | |
a4f1c77d KR |
940 | Changes in 1.8.1 (since 1.8.0): |
941 | ||
8ab3d8a0 | 942 | * LFS functions are now used to access 64-bit files on 32-bit systems. |
a4f1c77d | 943 | |
8ab3d8a0 | 944 | * New procedures (see the manual for details) |
4f416616 | 945 | |
8ab3d8a0 KR |
946 | ** primitive-_exit - [Scheme] the-root-module |
947 | ** scm_primitive__exit - [C] | |
948 | ** make-completion-function - [Scheme] (ice-9 readline) | |
949 | ** scm_c_locale_stringn_to_number - [C] | |
950 | ** scm_srfi1_append_reverse [C] | |
951 | ** scm_srfi1_append_reverse_x [C] | |
952 | ** scm_log - [C] | |
953 | ** scm_log10 - [C] | |
954 | ** scm_exp - [C] | |
955 | ** scm_sqrt - [C] | |
956 | ||
957 | * Bugs fixed | |
958 | ||
959 | ** Build problems have been fixed on MacOS, SunOS, and QNX. | |
af4f8612 | 960 | |
b3aa4626 KR |
961 | ** `strftime' fix sign of %z timezone offset. |
962 | ||
534cd148 | 963 | ** A one-dimensional array can now be 'equal?' to a vector. |
8ab3d8a0 | 964 | |
ad97642e | 965 | ** Structures, records, and SRFI-9 records can now be compared with `equal?'. |
af4f8612 | 966 | |
8ab3d8a0 KR |
967 | ** SRFI-14 standard char sets are recomputed upon a successful `setlocale'. |
968 | ||
969 | ** `record-accessor' and `record-modifier' now have strict type checks. | |
970 | ||
971 | Record accessor and modifier procedures now throw an error if the | |
972 | record type of the record they're given is not the type expected. | |
973 | (Previously accessors returned #f and modifiers silently did nothing). | |
974 | ||
975 | ** It is now OK to use both autoload and use-modules on a given module. | |
976 | ||
977 | ** `apply' checks the number of arguments more carefully on "0 or 1" funcs. | |
978 | ||
979 | Previously there was no checking on primatives like make-vector that | |
980 | accept "one or two" arguments. Now there is. | |
981 | ||
982 | ** The srfi-1 assoc function now calls its equality predicate properly. | |
983 | ||
984 | Previously srfi-1 assoc would call the equality predicate with the key | |
985 | last. According to the SRFI, the key should be first. | |
986 | ||
987 | ** A bug in n-par-for-each and n-for-each-par-map has been fixed. | |
988 | ||
989 | ** The array-set! procedure no longer segfaults when given a bit vector. | |
990 | ||
991 | ** Bugs in make-shared-array have been fixed. | |
992 | ||
993 | ** string<? and friends now follow char<? etc order on 8-bit chars. | |
994 | ||
995 | ** The format procedure now handles inf and nan values for ~f correctly. | |
996 | ||
997 | ** exact->inexact should no longer overflow when given certain large fractions. | |
998 | ||
999 | ** srfi-9 accessor and modifier procedures now have strict record type checks. | |
a4f1c77d | 1000 | |
8ab3d8a0 | 1001 | This matches the srfi-9 specification. |
a4f1c77d | 1002 | |
8ab3d8a0 | 1003 | ** (ice-9 ftw) procedures won't ignore different files with same inode number. |
a4f1c77d | 1004 | |
8ab3d8a0 KR |
1005 | Previously the (ice-9 ftw) procedures would ignore any file that had |
1006 | the same inode number as a file they had already seen, even if that | |
1007 | file was on a different device. | |
4f416616 KR |
1008 | |
1009 | \f | |
8ab3d8a0 | 1010 | Changes in 1.8.0 (changes since the 1.6.x series): |
ee0c7345 | 1011 | |
4e250ded MV |
1012 | * Changes to the distribution |
1013 | ||
eff2965e MV |
1014 | ** Guile is now licensed with the GNU Lesser General Public License. |
1015 | ||
77e51fd6 MV |
1016 | ** The manual is now licensed with the GNU Free Documentation License. |
1017 | ||
e2d0a649 RB |
1018 | ** Guile now requires GNU MP (http://swox.com/gmp). |
1019 | ||
1020 | Guile now uses the GNU MP library for arbitrary precision arithmetic. | |
e2d0a649 | 1021 | |
5ebbe4ef RB |
1022 | ** Guile now has separate private and public configuration headers. |
1023 | ||
b0d10ba6 MV |
1024 | That is, things like HAVE_STRING_H no longer leak from Guile's |
1025 | headers. | |
5ebbe4ef RB |
1026 | |
1027 | ** Guile now provides and uses an "effective" version number. | |
b2cbe8d8 RB |
1028 | |
1029 | Guile now provides scm_effective_version and effective-version | |
1030 | functions which return the "effective" version number. This is just | |
1031 | the normal full version string without the final micro-version number, | |
a4f1c77d | 1032 | so the current effective-version is "1.8". The effective version |
b2cbe8d8 RB |
1033 | should remain unchanged during a stable series, and should be used for |
1034 | items like the versioned share directory name | |
a4f1c77d | 1035 | i.e. /usr/share/guile/1.8. |
b2cbe8d8 RB |
1036 | |
1037 | Providing an unchanging version number during a stable release for | |
1038 | things like the versioned share directory can be particularly | |
1039 | important for Guile "add-on" packages, since it provides a directory | |
1040 | that they can install to that won't be changed out from under them | |
1041 | with each micro release during a stable series. | |
1042 | ||
8d54e73a | 1043 | ** Thread implementation has changed. |
f0b4d944 MV |
1044 | |
1045 | When you configure "--with-threads=null", you will get the usual | |
1046 | threading API (call-with-new-thread, make-mutex, etc), but you can't | |
429d88d4 MV |
1047 | actually create new threads. Also, "--with-threads=no" is now |
1048 | equivalent to "--with-threads=null". This means that the thread API | |
1049 | is always present, although you might not be able to create new | |
1050 | threads. | |
f0b4d944 | 1051 | |
8d54e73a MV |
1052 | When you configure "--with-threads=pthreads" or "--with-threads=yes", |
1053 | you will get threads that are implemented with the portable POSIX | |
1054 | threads. These threads can run concurrently (unlike the previous | |
1055 | "coop" thread implementation), but need to cooperate for things like | |
a558cc63 | 1056 | the GC. |
f0b4d944 | 1057 | |
8d54e73a MV |
1058 | The default is "pthreads", unless your platform doesn't have pthreads, |
1059 | in which case "null" threads are used. | |
2902a459 | 1060 | |
a6d75e53 MV |
1061 | See the manual for details, nodes "Initialization", "Multi-Threading", |
1062 | "Blocking", and others. | |
a558cc63 | 1063 | |
f74bdbd3 MV |
1064 | ** There is the new notion of 'discouraged' features. |
1065 | ||
1066 | This is a milder form of deprecation. | |
1067 | ||
1068 | Things that are discouraged should not be used in new code, but it is | |
1069 | OK to leave them in old code for now. When a discouraged feature is | |
1070 | used, no warning message is printed like there is for 'deprecated' | |
1071 | features. Also, things that are merely discouraged are nevertheless | |
1072 | implemented efficiently, while deprecated features can be very slow. | |
1073 | ||
1074 | You can omit discouraged features from libguile by configuring it with | |
1075 | the '--disable-discouraged' option. | |
1076 | ||
1077 | ** Deprecation warnings can be controlled at run-time. | |
1078 | ||
1079 | (debug-enable 'warn-deprecated) switches them on and (debug-disable | |
1080 | 'warn-deprecated) switches them off. | |
1081 | ||
0f24e75b | 1082 | ** Support for SRFI 61, extended cond syntax for multiple values has |
a81d0de1 MV |
1083 | been added. |
1084 | ||
1085 | This SRFI is always available. | |
1086 | ||
f7fb2f39 | 1087 | ** Support for require-extension, SRFI-55, has been added. |
9a5fc8c2 | 1088 | |
f7fb2f39 RB |
1089 | The SRFI-55 special form `require-extension' has been added. It is |
1090 | available at startup, and provides a portable way to load Scheme | |
1091 | extensions. SRFI-55 only requires support for one type of extension, | |
1092 | "srfi"; so a set of SRFIs may be loaded via (require-extension (srfi 1 | |
1093 | 13 14)). | |
1094 | ||
1095 | ** New module (srfi srfi-26) provides support for `cut' and `cute'. | |
1096 | ||
1097 | The (srfi srfi-26) module is an implementation of SRFI-26 which | |
1098 | provides the `cut' and `cute' syntax. These may be used to specialize | |
1099 | parameters without currying. | |
9a5fc8c2 | 1100 | |
f5d54eb7 RB |
1101 | ** New module (srfi srfi-31) |
1102 | ||
1103 | This is an implementation of SRFI-31 which provides a special form | |
1104 | `rec' for recursive evaluation. | |
1105 | ||
7b1574ed MV |
1106 | ** The modules (srfi srfi-13), (srfi srfi-14) and (srfi srfi-4) have |
1107 | been merged with the core, making their functionality always | |
1108 | available. | |
c5080b51 | 1109 | |
ce7c0293 MV |
1110 | The modules are still available, tho, and you could use them together |
1111 | with a renaming import, for example. | |
c5080b51 | 1112 | |
6191ccec | 1113 | ** Guile no longer includes its own version of libltdl. |
4e250ded | 1114 | |
6191ccec | 1115 | The official version is good enough now. |
4e250ded | 1116 | |
ae7ded56 MV |
1117 | ** The --enable-htmldoc option has been removed from 'configure'. |
1118 | ||
1119 | Support for translating the documentation into HTML is now always | |
1120 | provided. Use 'make html'. | |
1121 | ||
0f24e75b MV |
1122 | ** New module (ice-9 serialize): |
1123 | ||
1124 | (serialize FORM1 ...) and (parallelize FORM1 ...) are useful when you | |
1125 | don't trust the thread safety of most of your program, but where you | |
1126 | have some section(s) of code which you consider can run in parallel to | |
1127 | other sections. See ice-9/serialize.scm for more information. | |
1128 | ||
c34e5780 MV |
1129 | ** The configure option '--disable-arrays' has been removed. |
1130 | ||
1131 | Support for arrays and uniform numeric arrays is now always included | |
1132 | in Guile. | |
1133 | ||
328dc9a3 | 1134 | * Changes to the stand-alone interpreter |
f12ef3fd | 1135 | |
3ece39d6 MV |
1136 | ** New command line option `-L'. |
1137 | ||
1138 | This option adds a directory to the front of the load path. | |
1139 | ||
f12ef3fd MV |
1140 | ** New command line option `--no-debug'. |
1141 | ||
1142 | Specifying `--no-debug' on the command line will keep the debugging | |
1143 | evaluator turned off, even for interactive sessions. | |
1144 | ||
1145 | ** User-init file ~/.guile is now loaded with the debugging evaluator. | |
1146 | ||
1147 | Previously, the normal evaluator would have been used. Using the | |
1148 | debugging evaluator gives better error messages. | |
1149 | ||
aff7e166 MV |
1150 | ** The '-e' option now 'read's its argument. |
1151 | ||
1152 | This is to allow the new '(@ MODULE-NAME VARIABLE-NAME)' construct to | |
1153 | be used with '-e'. For example, you can now write a script like | |
1154 | ||
1155 | #! /bin/sh | |
1156 | exec guile -e '(@ (demo) main)' -s "$0" "$@" | |
1157 | !# | |
1158 | ||
1159 | (define-module (demo) | |
1160 | :export (main)) | |
1161 | ||
1162 | (define (main args) | |
1163 | (format #t "Demo: ~a~%" args)) | |
1164 | ||
1165 | ||
f12ef3fd MV |
1166 | * Changes to Scheme functions and syntax |
1167 | ||
930888e8 MV |
1168 | ** Guardians have changed back to their original semantics |
1169 | ||
1170 | Guardians now behave like described in the paper by Dybvig et al. In | |
1171 | particular, they no longer make guarantees about the order in which | |
1172 | they return objects, and they can no longer be greedy. | |
1173 | ||
1174 | They no longer drop cyclic data structures. | |
1175 | ||
1176 | The C function scm_make_guardian has been changed incompatibly and no | |
1177 | longer takes the 'greedy_p' argument. | |
1178 | ||
87bdbdbc MV |
1179 | ** New function hashx-remove! |
1180 | ||
1181 | This function completes the set of 'hashx' functions. | |
1182 | ||
a558cc63 MV |
1183 | ** The concept of dynamic roots has been factored into continuation |
1184 | barriers and dynamic states. | |
1185 | ||
1186 | Each thread has a current dynamic state that carries the values of the | |
1187 | fluids. You can create and copy dynamic states and use them as the | |
1188 | second argument for 'eval'. See "Fluids and Dynamic States" in the | |
1189 | manual. | |
1190 | ||
1191 | To restrict the influence that captured continuations can have on the | |
1192 | control flow, you can errect continuation barriers. See "Continuation | |
1193 | Barriers" in the manual. | |
1194 | ||
1195 | The function call-with-dynamic-root now essentially temporarily | |
1196 | installs a new dynamic state and errects a continuation barrier. | |
1197 | ||
a2b6a0e7 MV |
1198 | ** The default load path no longer includes "." at the end. |
1199 | ||
1200 | Automatically loading modules from the current directory should not | |
1201 | happen by default. If you want to allow it in a more controlled | |
1202 | manner, set the environment variable GUILE_LOAD_PATH or the Scheme | |
1203 | variable %load-path. | |
1204 | ||
7b1574ed MV |
1205 | ** The uniform vector and array support has been overhauled. |
1206 | ||
1207 | It now complies with SRFI-4 and the weird prototype based uniform | |
1208 | array creation has been deprecated. See the manual for more details. | |
1209 | ||
d233b123 MV |
1210 | Some non-compatible changes have been made: |
1211 | - characters can no longer be stored into byte arrays. | |
0f24e75b MV |
1212 | - strings and bit vectors are no longer considered to be uniform numeric |
1213 | vectors. | |
3167d5e4 MV |
1214 | - array-rank throws an error for non-arrays instead of returning zero. |
1215 | - array-ref does no longer accept non-arrays when no indices are given. | |
d233b123 MV |
1216 | |
1217 | There is the new notion of 'generalized vectors' and corresponding | |
1218 | procedures like 'generalized-vector-ref'. Generalized vectors include | |
c34e5780 | 1219 | strings, bitvectors, ordinary vectors, and uniform numeric vectors. |
d233b123 | 1220 | |
a558cc63 MV |
1221 | Arrays use generalized vectors as their storage, so that you still |
1222 | have arrays of characters, bits, etc. However, uniform-array-read! | |
1223 | and uniform-array-write can no longer read/write strings and | |
1224 | bitvectors. | |
bb9f50ae | 1225 | |
ce7c0293 MV |
1226 | ** There is now support for copy-on-write substrings, mutation-sharing |
1227 | substrings and read-only strings. | |
3ff9283d | 1228 | |
ce7c0293 MV |
1229 | Three new procedures are related to this: substring/shared, |
1230 | substring/copy, and substring/read-only. See the manual for more | |
1231 | information. | |
1232 | ||
6a1d27ea MV |
1233 | ** Backtraces will now highlight the value that caused the error. |
1234 | ||
1235 | By default, these values are enclosed in "{...}", such as in this | |
1236 | example: | |
1237 | ||
1238 | guile> (car 'a) | |
1239 | ||
1240 | Backtrace: | |
1241 | In current input: | |
1242 | 1: 0* [car {a}] | |
1243 | ||
1244 | <unnamed port>:1:1: In procedure car in expression (car (quote a)): | |
1245 | <unnamed port>:1:1: Wrong type (expecting pair): a | |
1246 | ABORT: (wrong-type-arg) | |
1247 | ||
1248 | The prefix and suffix used for highlighting can be set via the two new | |
1249 | printer options 'highlight-prefix' and 'highlight-suffix'. For | |
1250 | example, putting this into ~/.guile will output the bad value in bold | |
1251 | on an ANSI terminal: | |
1252 | ||
1253 | (print-set! highlight-prefix "\x1b[1m") | |
1254 | (print-set! highlight-suffix "\x1b[22m") | |
1255 | ||
1256 | ||
8dbafacd MV |
1257 | ** 'gettext' support for internationalization has been added. |
1258 | ||
1259 | See the manual for details. | |
1260 | ||
aff7e166 MV |
1261 | ** New syntax '@' and '@@': |
1262 | ||
1263 | You can now directly refer to variables exported from a module by | |
1264 | writing | |
1265 | ||
1266 | (@ MODULE-NAME VARIABLE-NAME) | |
1267 | ||
1268 | For example (@ (ice-9 pretty-print) pretty-print) will directly access | |
1269 | the pretty-print variable exported from the (ice-9 pretty-print) | |
1270 | module. You don't need to 'use' that module first. You can also use | |
b0d10ba6 | 1271 | '@' as a target of 'set!', as in (set! (@ mod var) val). |
aff7e166 MV |
1272 | |
1273 | The related syntax (@@ MODULE-NAME VARIABLE-NAME) works just like '@', | |
1274 | but it can also access variables that have not been exported. It is | |
1275 | intended only for kluges and temporary fixes and for debugging, not | |
1276 | for ordinary code. | |
1277 | ||
aef0bdb4 MV |
1278 | ** Keyword syntax has been made more disciplined. |
1279 | ||
1280 | Previously, the name of a keyword was read as a 'token' but printed as | |
1281 | a symbol. Now, it is read as a general Scheme datum which must be a | |
1282 | symbol. | |
1283 | ||
1284 | Previously: | |
1285 | ||
1286 | guile> #:12 | |
1287 | #:#{12}# | |
1288 | guile> #:#{12}# | |
1289 | #:#{\#{12}\#}# | |
1290 | guile> #:(a b c) | |
1291 | #:#{}# | |
1292 | ERROR: In expression (a b c): | |
1293 | Unbound variable: a | |
1294 | guile> #: foo | |
1295 | #:#{}# | |
1296 | ERROR: Unbound variable: foo | |
1297 | ||
1298 | Now: | |
1299 | ||
1300 | guile> #:12 | |
1301 | ERROR: Wrong type (expecting symbol): 12 | |
1302 | guile> #:#{12}# | |
1303 | #:#{12}# | |
1304 | guile> #:(a b c) | |
1305 | ERROR: Wrong type (expecting symbol): (a b c) | |
1306 | guile> #: foo | |
1307 | #:foo | |
1308 | ||
227eafdb MV |
1309 | ** The printing of symbols that might look like keywords can be |
1310 | controlled. | |
1311 | ||
1312 | The new printer option 'quote-keywordish-symbols' controls how symbols | |
1313 | are printed that have a colon as their first or last character. The | |
1314 | default now is to only quote a symbol with #{...}# when the read | |
1315 | option 'keywords' is not '#f'. Thus: | |
1316 | ||
1317 | guile> (define foo (string->symbol ":foo")) | |
1318 | guile> (read-set! keywords #f) | |
1319 | guile> foo | |
1320 | :foo | |
1321 | guile> (read-set! keywords 'prefix) | |
1322 | guile> foo | |
1323 | #{:foo}# | |
1324 | guile> (print-set! quote-keywordish-symbols #f) | |
1325 | guile> foo | |
1326 | :foo | |
1327 | ||
1363e3e7 KR |
1328 | ** 'while' now provides 'break' and 'continue' |
1329 | ||
1330 | break and continue were previously bound in a while loop, but not | |
1331 | documented, and continue didn't quite work properly. The undocumented | |
1332 | parameter to break which gave a return value for the while has been | |
1333 | dropped. | |
1334 | ||
570b5b14 MV |
1335 | ** 'call-with-current-continuation' is now also available under the name |
1336 | 'call/cc'. | |
1337 | ||
b0d10ba6 | 1338 | ** The module system now checks for duplicate bindings. |
7b07e5ef | 1339 | |
fe6ee052 MD |
1340 | The module system now can check for name conflicts among imported |
1341 | bindings. | |
f595ccfe | 1342 | |
b0d10ba6 | 1343 | The behavior can be controlled by specifying one or more 'duplicates' |
fe6ee052 MD |
1344 | handlers. For example, to make Guile return an error for every name |
1345 | collision, write: | |
7b07e5ef MD |
1346 | |
1347 | (define-module (foo) | |
1348 | :use-module (bar) | |
1349 | :use-module (baz) | |
fe6ee052 | 1350 | :duplicates check) |
f595ccfe | 1351 | |
fe6ee052 MD |
1352 | The new default behavior of the module system when a name collision |
1353 | has been detected is to | |
1354 | ||
1355 | 1. Give priority to bindings marked as a replacement. | |
6496a663 | 1356 | 2. Issue a warning (different warning if overriding core binding). |
fe6ee052 MD |
1357 | 3. Give priority to the last encountered binding (this corresponds to |
1358 | the old behavior). | |
1359 | ||
1360 | If you want the old behavior back without replacements or warnings you | |
1361 | can add the line: | |
f595ccfe | 1362 | |
70a9dc9c | 1363 | (default-duplicate-binding-handler 'last) |
7b07e5ef | 1364 | |
fe6ee052 | 1365 | to your .guile init file. |
7b07e5ef | 1366 | |
f595ccfe MD |
1367 | ** New define-module option: :replace |
1368 | ||
1369 | :replace works as :export, but, in addition, marks the binding as a | |
1370 | replacement. | |
1371 | ||
1372 | A typical example is `format' in (ice-9 format) which is a replacement | |
1373 | for the core binding `format'. | |
7b07e5ef | 1374 | |
70da0033 MD |
1375 | ** Adding prefixes to imported bindings in the module system |
1376 | ||
1377 | There is now a new :use-module option :prefix. It can be used to add | |
1378 | a prefix to all imported bindings. | |
1379 | ||
1380 | (define-module (foo) | |
1381 | :use-module ((bar) :prefix bar:)) | |
1382 | ||
1383 | will import all bindings exported from bar, but rename them by adding | |
1384 | the prefix `bar:'. | |
1385 | ||
b0d10ba6 MV |
1386 | ** Conflicting generic functions can be automatically merged. |
1387 | ||
1388 | When two imported bindings conflict and they are both generic | |
1389 | functions, the two functions can now be merged automatically. This is | |
1390 | activated with the 'duplicates' handler 'merge-generics'. | |
1391 | ||
b2cbe8d8 RB |
1392 | ** New function: effective-version |
1393 | ||
1394 | Returns the "effective" version number. This is just the normal full | |
1395 | version string without the final micro-version number. See "Changes | |
1396 | to the distribution" above. | |
1397 | ||
382053e9 | 1398 | ** New threading functions: parallel, letpar, par-map, and friends |
dbe30084 | 1399 | |
382053e9 KR |
1400 | These are convenient ways to run calculations in parallel in new |
1401 | threads. See "Parallel forms" in the manual for details. | |
359aab24 | 1402 | |
e2d820a1 MV |
1403 | ** New function 'try-mutex'. |
1404 | ||
1405 | This function will attempt to lock a mutex but will return immediately | |
0f24e75b | 1406 | instead of blocking and indicate failure. |
e2d820a1 MV |
1407 | |
1408 | ** Waiting on a condition variable can have a timeout. | |
1409 | ||
0f24e75b | 1410 | The function 'wait-condition-variable' now takes a third, optional |
e2d820a1 MV |
1411 | argument that specifies the point in time where the waiting should be |
1412 | aborted. | |
1413 | ||
1414 | ** New function 'broadcast-condition-variable'. | |
1415 | ||
5e405a60 MV |
1416 | ** New functions 'all-threads' and 'current-thread'. |
1417 | ||
1418 | ** Signals and system asyncs work better with threads. | |
1419 | ||
1420 | The function 'sigaction' now takes a fourth, optional, argument that | |
1421 | specifies the thread that the handler should run in. When the | |
1422 | argument is omitted, the handler will run in the thread that called | |
1423 | 'sigaction'. | |
1424 | ||
1425 | Likewise, 'system-async-mark' takes a second, optional, argument that | |
1426 | specifies the thread that the async should run in. When it is | |
1427 | omitted, the async will run in the thread that called | |
1428 | 'system-async-mark'. | |
1429 | ||
1430 | C code can use the new functions scm_sigaction_for_thread and | |
1431 | scm_system_async_mark_for_thread to pass the new thread argument. | |
1432 | ||
a558cc63 MV |
1433 | When a thread blocks on a mutex, a condition variable or is waiting |
1434 | for IO to be possible, it will still execute system asyncs. This can | |
1435 | be used to interrupt such a thread by making it execute a 'throw', for | |
1436 | example. | |
1437 | ||
5e405a60 MV |
1438 | ** The function 'system-async' is deprecated. |
1439 | ||
1440 | You can now pass any zero-argument procedure to 'system-async-mark'. | |
1441 | The function 'system-async' will just return its argument unchanged | |
1442 | now. | |
1443 | ||
acfa1f52 MV |
1444 | ** New functions 'call-with-blocked-asyncs' and |
1445 | 'call-with-unblocked-asyncs' | |
1446 | ||
1447 | The expression (call-with-blocked-asyncs PROC) will call PROC and will | |
1448 | block execution of system asyncs for the current thread by one level | |
1449 | while PROC runs. Likewise, call-with-unblocked-asyncs will call a | |
1450 | procedure and will unblock the execution of system asyncs by one | |
1451 | level for the current thread. | |
1452 | ||
1453 | Only system asyncs are affected by these functions. | |
1454 | ||
1455 | ** The functions 'mask-signals' and 'unmask-signals' are deprecated. | |
1456 | ||
1457 | Use 'call-with-blocked-asyncs' or 'call-with-unblocked-asyncs' | |
1458 | instead. Those functions are easier to use correctly and can be | |
1459 | nested. | |
1460 | ||
7b232758 MV |
1461 | ** New function 'unsetenv'. |
1462 | ||
f30482f3 MV |
1463 | ** New macro 'define-syntax-public'. |
1464 | ||
1465 | It works like 'define-syntax' and also exports the defined macro (but | |
1466 | only on top-level). | |
1467 | ||
1ee34062 MV |
1468 | ** There is support for Infinity and NaNs. |
1469 | ||
1470 | Following PLT Scheme, Guile can now work with infinite numbers, and | |
1471 | 'not-a-numbers'. | |
1472 | ||
1473 | There is new syntax for numbers: "+inf.0" (infinity), "-inf.0" | |
1474 | (negative infinity), "+nan.0" (not-a-number), and "-nan.0" (same as | |
1475 | "+nan.0"). These numbers are inexact and have no exact counterpart. | |
1476 | ||
1477 | Dividing by an inexact zero returns +inf.0 or -inf.0, depending on the | |
1478 | sign of the dividend. The infinities are integers, and they answer #t | |
1479 | for both 'even?' and 'odd?'. The +nan.0 value is not an integer and is | |
1480 | not '=' to itself, but '+nan.0' is 'eqv?' to itself. | |
1481 | ||
1482 | For example | |
1483 | ||
1484 | (/ 1 0.0) | |
1485 | => +inf.0 | |
1486 | ||
1487 | (/ 0 0.0) | |
1488 | => +nan.0 | |
1489 | ||
1490 | (/ 0) | |
1491 | ERROR: Numerical overflow | |
1492 | ||
7b232758 MV |
1493 | Two new predicates 'inf?' and 'nan?' can be used to test for the |
1494 | special values. | |
1495 | ||
ba1b077b MV |
1496 | ** Inexact zero can have a sign. |
1497 | ||
1498 | Guile can now distinguish between plus and minus inexact zero, if your | |
1499 | platform supports this, too. The two zeros are equal according to | |
1500 | '=', but not according to 'eqv?'. For example | |
1501 | ||
1502 | (- 0.0) | |
1503 | => -0.0 | |
1504 | ||
1505 | (= 0.0 (- 0.0)) | |
1506 | => #t | |
1507 | ||
1508 | (eqv? 0.0 (- 0.0)) | |
1509 | => #f | |
1510 | ||
bdf26b60 MV |
1511 | ** Guile now has exact rationals. |
1512 | ||
1513 | Guile can now represent fractions such as 1/3 exactly. Computing with | |
1514 | them is also done exactly, of course: | |
1515 | ||
1516 | (* 1/3 3/2) | |
1517 | => 1/2 | |
1518 | ||
1519 | ** 'floor', 'ceiling', 'round' and 'truncate' now return exact numbers | |
1520 | for exact arguments. | |
1521 | ||
1522 | For example: (floor 2) now returns an exact 2 where in the past it | |
1523 | returned an inexact 2.0. Likewise, (floor 5/4) returns an exact 1. | |
1524 | ||
1525 | ** inexact->exact no longer returns only integers. | |
1526 | ||
1527 | Without exact rationals, the closest exact number was always an | |
1528 | integer, but now inexact->exact returns the fraction that is exactly | |
1529 | equal to a floating point number. For example: | |
1530 | ||
1531 | (inexact->exact 1.234) | |
1532 | => 694680242521899/562949953421312 | |
1533 | ||
e299cee2 | 1534 | When you want the old behavior, use 'round' explicitly: |
bdf26b60 MV |
1535 | |
1536 | (inexact->exact (round 1.234)) | |
1537 | => 1 | |
1538 | ||
1539 | ** New function 'rationalize'. | |
1540 | ||
1541 | This function finds a simple fraction that is close to a given real | |
1542 | number. For example (and compare with inexact->exact above): | |
1543 | ||
fb16d26e | 1544 | (rationalize (inexact->exact 1.234) 1/2000) |
bdf26b60 MV |
1545 | => 58/47 |
1546 | ||
fb16d26e MV |
1547 | Note that, as required by R5RS, rationalize returns only then an exact |
1548 | result when both its arguments are exact. | |
1549 | ||
bdf26b60 MV |
1550 | ** 'odd?' and 'even?' work also for inexact integers. |
1551 | ||
1552 | Previously, (odd? 1.0) would signal an error since only exact integers | |
1553 | were recognized as integers. Now (odd? 1.0) returns #t, (odd? 2.0) | |
1554 | returns #f and (odd? 1.5) signals an error. | |
1555 | ||
b0d10ba6 | 1556 | ** Guile now has uninterned symbols. |
610922b2 | 1557 | |
b0d10ba6 | 1558 | The new function 'make-symbol' will return an uninterned symbol. This |
610922b2 MV |
1559 | is a symbol that is unique and is guaranteed to remain unique. |
1560 | However, uninterned symbols can not yet be read back in. | |
1561 | ||
1562 | Use the new function 'symbol-interned?' to check whether a symbol is | |
1563 | interned or not. | |
1564 | ||
0e6f7775 MV |
1565 | ** pretty-print has more options. |
1566 | ||
1567 | The function pretty-print from the (ice-9 pretty-print) module can now | |
1568 | also be invoked with keyword arguments that control things like | |
71f271b2 | 1569 | maximum output width. See the manual for details. |
0e6f7775 | 1570 | |
8c84b81e | 1571 | ** Variables have no longer a special behavior for `equal?'. |
ee0c7345 MV |
1572 | |
1573 | Previously, comparing two variables with `equal?' would recursivly | |
1574 | compare their values. This is no longer done. Variables are now only | |
1575 | `equal?' if they are `eq?'. | |
1576 | ||
4e21fa60 MV |
1577 | ** `(begin)' is now valid. |
1578 | ||
1579 | You can now use an empty `begin' form. It will yield #<unspecified> | |
1580 | when evaluated and simply be ignored in a definition context. | |
1581 | ||
3063e30a DH |
1582 | ** Deprecated: procedure->macro |
1583 | ||
b0d10ba6 MV |
1584 | Change your code to use 'define-macro' or r5rs macros. Also, be aware |
1585 | that macro expansion will not be done during evaluation, but prior to | |
1586 | evaluation. | |
3063e30a | 1587 | |
0a50eeaa NJ |
1588 | ** Soft ports now allow a `char-ready?' procedure |
1589 | ||
1590 | The vector argument to `make-soft-port' can now have a length of | |
1591 | either 5 or 6. (Previously the length had to be 5.) The optional 6th | |
1592 | element is interpreted as an `input-waiting' thunk -- i.e. a thunk | |
1593 | that returns the number of characters that can be read immediately | |
1594 | without the soft port blocking. | |
1595 | ||
63dd3413 DH |
1596 | ** Deprecated: undefine |
1597 | ||
1598 | There is no replacement for undefine. | |
1599 | ||
9abd541e NJ |
1600 | ** The functions make-keyword-from-dash-symbol and keyword-dash-symbol |
1601 | have been discouraged. | |
aef0bdb4 MV |
1602 | |
1603 | They are relics from a time where a keyword like #:foo was used | |
1604 | directly as a Tcl option "-foo" and thus keywords were internally | |
1605 | stored as a symbol with a starting dash. We now store a symbol | |
1606 | without the dash. | |
1607 | ||
1608 | Use symbol->keyword and keyword->symbol instead. | |
1609 | ||
9abd541e NJ |
1610 | ** The `cheap' debug option is now obsolete |
1611 | ||
1612 | Evaluator trap calls are now unconditionally "cheap" - in other words, | |
1613 | they pass a debug object to the trap handler rather than a full | |
1614 | continuation. The trap handler code can capture a full continuation | |
1615 | by using `call-with-current-continuation' in the usual way, if it so | |
1616 | desires. | |
1617 | ||
1618 | The `cheap' option is retained for now so as not to break existing | |
1619 | code which gets or sets it, but setting it now has no effect. It will | |
1620 | be removed in the next major Guile release. | |
1621 | ||
1622 | ** Evaluator trap calls now support `tweaking' | |
1623 | ||
1624 | `Tweaking' means that the trap handler code can modify the Scheme | |
1625 | expression that is about to be evaluated (in the case of an | |
1626 | enter-frame trap) or the value that is being returned (in the case of | |
1627 | an exit-frame trap). The trap handler code indicates that it wants to | |
1628 | do this by returning a pair whose car is the symbol 'instead and whose | |
1629 | cdr is the modified expression or return value. | |
36a9b236 | 1630 | |
b00418df DH |
1631 | * Changes to the C interface |
1632 | ||
87bdbdbc MV |
1633 | ** The functions scm_hash_fn_remove_x and scm_hashx_remove_x no longer |
1634 | take a 'delete' function argument. | |
1635 | ||
1636 | This argument makes no sense since the delete function is used to | |
1637 | remove a pair from an alist, and this must not be configurable. | |
1638 | ||
1639 | This is an incompatible change. | |
1640 | ||
1cf1bb95 MV |
1641 | ** The GH interface is now subject to the deprecation mechanism |
1642 | ||
1643 | The GH interface has been deprecated for quite some time but now it is | |
1644 | actually removed from Guile when it is configured with | |
1645 | --disable-deprecated. | |
1646 | ||
1647 | See the manual "Transitioning away from GH" for more information. | |
1648 | ||
f7f3964e MV |
1649 | ** A new family of functions for converting between C values and |
1650 | Scheme values has been added. | |
1651 | ||
1652 | These functions follow a common naming scheme and are designed to be | |
1653 | easier to use, thread-safe and more future-proof than the older | |
1654 | alternatives. | |
1655 | ||
1656 | - int scm_is_* (...) | |
1657 | ||
1658 | These are predicates that return a C boolean: 1 or 0. Instead of | |
1659 | SCM_NFALSEP, you can now use scm_is_true, for example. | |
1660 | ||
1661 | - <type> scm_to_<type> (SCM val, ...) | |
1662 | ||
1663 | These are functions that convert a Scheme value into an appropriate | |
1664 | C value. For example, you can use scm_to_int to safely convert from | |
1665 | a SCM to an int. | |
1666 | ||
a2b6a0e7 | 1667 | - SCM scm_from_<type> (<type> val, ...) |
f7f3964e MV |
1668 | |
1669 | These functions convert from a C type to a SCM value; for example, | |
1670 | scm_from_int for ints. | |
1671 | ||
1672 | There is a huge number of these functions, for numbers, strings, | |
1673 | symbols, vectors, etc. They are documented in the reference manual in | |
1674 | the API section together with the types that they apply to. | |
1675 | ||
96d8c217 MV |
1676 | ** New functions for dealing with complex numbers in C have been added. |
1677 | ||
1678 | The new functions are scm_c_make_rectangular, scm_c_make_polar, | |
1679 | scm_c_real_part, scm_c_imag_part, scm_c_magnitude and scm_c_angle. | |
1680 | They work like scm_make_rectangular etc but take or return doubles | |
1681 | directly. | |
1682 | ||
1683 | ** The function scm_make_complex has been discouraged. | |
1684 | ||
1685 | Use scm_c_make_rectangular instead. | |
1686 | ||
f7f3964e MV |
1687 | ** The INUM macros have been deprecated. |
1688 | ||
1689 | A lot of code uses these macros to do general integer conversions, | |
b0d10ba6 MV |
1690 | although the macros only work correctly with fixnums. Use the |
1691 | following alternatives. | |
f7f3964e MV |
1692 | |
1693 | SCM_INUMP -> scm_is_integer or similar | |
1694 | SCM_NINUMP -> !scm_is_integer or similar | |
1695 | SCM_MAKINUM -> scm_from_int or similar | |
1696 | SCM_INUM -> scm_to_int or similar | |
1697 | ||
b0d10ba6 | 1698 | SCM_VALIDATE_INUM_* -> Do not use these; scm_to_int, etc. will |
f7f3964e MV |
1699 | do the validating for you. |
1700 | ||
f9656a9f MV |
1701 | ** The scm_num2<type> and scm_<type>2num functions and scm_make_real |
1702 | have been discouraged. | |
f7f3964e MV |
1703 | |
1704 | Use the newer scm_to_<type> and scm_from_<type> functions instead for | |
1705 | new code. The functions have been discouraged since they don't fit | |
1706 | the naming scheme. | |
1707 | ||
1708 | ** The 'boolean' macros SCM_FALSEP etc have been discouraged. | |
1709 | ||
1710 | They have strange names, especially SCM_NFALSEP, and SCM_BOOLP | |
1711 | evaluates its argument twice. Use scm_is_true, etc. instead for new | |
1712 | code. | |
1713 | ||
1714 | ** The macro SCM_EQ_P has been discouraged. | |
1715 | ||
1716 | Use scm_is_eq for new code, which fits better into the naming | |
1717 | conventions. | |
d5b203a6 | 1718 | |
d5ac9b2a MV |
1719 | ** The macros SCM_CONSP, SCM_NCONSP, SCM_NULLP, and SCM_NNULLP have |
1720 | been discouraged. | |
1721 | ||
1722 | Use the function scm_is_pair or scm_is_null instead. | |
1723 | ||
409eb4e5 MV |
1724 | ** The functions scm_round and scm_truncate have been deprecated and |
1725 | are now available as scm_c_round and scm_c_truncate, respectively. | |
1726 | ||
1727 | These functions occupy the names that scm_round_number and | |
1728 | scm_truncate_number should have. | |
1729 | ||
3ff9283d MV |
1730 | ** The functions scm_c_string2str, scm_c_substring2str, and |
1731 | scm_c_symbol2str have been deprecated. | |
c41acab3 MV |
1732 | |
1733 | Use scm_to_locale_stringbuf or similar instead, maybe together with | |
1734 | scm_substring. | |
1735 | ||
3ff9283d MV |
1736 | ** New functions scm_c_make_string, scm_c_string_length, |
1737 | scm_c_string_ref, scm_c_string_set_x, scm_c_substring, | |
1738 | scm_c_substring_shared, scm_c_substring_copy. | |
1739 | ||
1740 | These are like scm_make_string, scm_length, etc. but are slightly | |
1741 | easier to use from C. | |
1742 | ||
1743 | ** The macros SCM_STRINGP, SCM_STRING_CHARS, SCM_STRING_LENGTH, | |
1744 | SCM_SYMBOL_CHARS, and SCM_SYMBOL_LENGTH have been deprecated. | |
1745 | ||
1746 | They export too many assumptions about the implementation of strings | |
1747 | and symbols that are no longer true in the presence of | |
b0d10ba6 MV |
1748 | mutation-sharing substrings and when Guile switches to some form of |
1749 | Unicode. | |
3ff9283d MV |
1750 | |
1751 | When working with strings, it is often best to use the normal string | |
1752 | functions provided by Guile, such as scm_c_string_ref, | |
b0d10ba6 MV |
1753 | scm_c_string_set_x, scm_string_append, etc. Be sure to look in the |
1754 | manual since many more such functions are now provided than | |
1755 | previously. | |
3ff9283d MV |
1756 | |
1757 | When you want to convert a SCM string to a C string, use the | |
1758 | scm_to_locale_string function or similar instead. For symbols, use | |
1759 | scm_symbol_to_string and then work with that string. Because of the | |
1760 | new string representation, scm_symbol_to_string does not need to copy | |
1761 | and is thus quite efficient. | |
1762 | ||
aef0bdb4 | 1763 | ** Some string, symbol and keyword functions have been discouraged. |
3ff9283d | 1764 | |
b0d10ba6 | 1765 | They don't fit into the uniform naming scheme and are not explicit |
3ff9283d MV |
1766 | about the character encoding. |
1767 | ||
1768 | Replace according to the following table: | |
1769 | ||
1770 | scm_allocate_string -> scm_c_make_string | |
1771 | scm_take_str -> scm_take_locale_stringn | |
1772 | scm_take0str -> scm_take_locale_string | |
1773 | scm_mem2string -> scm_from_locale_stringn | |
1774 | scm_str2string -> scm_from_locale_string | |
1775 | scm_makfrom0str -> scm_from_locale_string | |
1776 | scm_mem2symbol -> scm_from_locale_symboln | |
b0d10ba6 | 1777 | scm_mem2uninterned_symbol -> scm_from_locale_stringn + scm_make_symbol |
3ff9283d MV |
1778 | scm_str2symbol -> scm_from_locale_symbol |
1779 | ||
1780 | SCM_SYMBOL_HASH -> scm_hashq | |
1781 | SCM_SYMBOL_INTERNED_P -> scm_symbol_interned_p | |
1782 | ||
aef0bdb4 MV |
1783 | scm_c_make_keyword -> scm_from_locale_keyword |
1784 | ||
1785 | ** The functions scm_keyword_to_symbol and sym_symbol_to_keyword are | |
1786 | now also available to C code. | |
1787 | ||
1788 | ** SCM_KEYWORDP and SCM_KEYWORDSYM have been deprecated. | |
1789 | ||
1790 | Use scm_is_keyword and scm_keyword_to_symbol instead, but note that | |
1791 | the latter returns the true name of the keyword, not the 'dash name', | |
1792 | as SCM_KEYWORDSYM used to do. | |
1793 | ||
dc91d8de MV |
1794 | ** A new way to access arrays in a thread-safe and efficient way has |
1795 | been added. | |
1796 | ||
1797 | See the manual, node "Accessing Arrays From C". | |
1798 | ||
3167d5e4 MV |
1799 | ** The old uniform vector and bitvector implementations have been |
1800 | unceremoniously removed. | |
d4ea47c8 | 1801 | |
a558cc63 | 1802 | This implementation exposed the details of the tagging system of |
d4ea47c8 | 1803 | Guile. Use the new C API explained in the manual in node "Uniform |
c34e5780 | 1804 | Numeric Vectors" and "Bit Vectors", respectively. |
d4ea47c8 MV |
1805 | |
1806 | The following macros are gone: SCM_UVECTOR_BASE, SCM_SET_UVECTOR_BASE, | |
1807 | SCM_UVECTOR_MAXLENGTH, SCM_UVECTOR_LENGTH, SCM_MAKE_UVECTOR_TAG, | |
3167d5e4 MV |
1808 | SCM_SET_UVECTOR_LENGTH, SCM_BITVECTOR_P, SCM_BITVECTOR_BASE, |
1809 | SCM_SET_BITVECTOR_BASE, SCM_BITVECTOR_MAX_LENGTH, | |
1810 | SCM_BITVECTOR_LENGTH, SCM_MAKE_BITVECTOR_TAG, | |
0b63c1ee MV |
1811 | SCM_SET_BITVECTOR_LENGTH, SCM_BITVEC_REF, SCM_BITVEC_SET, |
1812 | SCM_BITVEC_CLR. | |
d4ea47c8 | 1813 | |
c34e5780 MV |
1814 | ** The macros dealing with vectors have been deprecated. |
1815 | ||
1816 | Use the new functions scm_is_vector, scm_vector_elements, | |
0b63c1ee MV |
1817 | scm_vector_writable_elements, etc, or scm_is_simple_vector, |
1818 | SCM_SIMPLE_VECTOR_REF, SCM_SIMPLE_VECTOR_SET, etc instead. See the | |
1819 | manual for more details. | |
c34e5780 MV |
1820 | |
1821 | Deprecated are SCM_VECTORP, SCM_VELTS, SCM_VECTOR_MAX_LENGTH, | |
1822 | SCM_VECTOR_LENGTH, SCM_VECTOR_REF, SCM_VECTOR_SET, SCM_WRITABLE_VELTS. | |
1823 | ||
1824 | The following macros have been removed: SCM_VECTOR_BASE, | |
1825 | SCM_SET_VECTOR_BASE, SCM_MAKE_VECTOR_TAG, SCM_SET_VECTOR_LENGTH, | |
1826 | SCM_VELTS_AS_STACKITEMS, SCM_SETVELTS, SCM_GC_WRITABLE_VELTS. | |
1827 | ||
0c7a5cab | 1828 | ** Some C functions and macros related to arrays have been deprecated. |
dc91d8de MV |
1829 | |
1830 | Migrate according to the following table: | |
1831 | ||
e94d0be2 | 1832 | scm_make_uve -> scm_make_typed_array, scm_make_u8vector etc. |
dc91d8de MV |
1833 | scm_make_ra -> scm_make_array |
1834 | scm_shap2ra -> scm_make_array | |
1835 | scm_cvref -> scm_c_generalized_vector_ref | |
1836 | scm_ra_set_contp -> do not use | |
1837 | scm_aind -> scm_array_handle_pos | |
1838 | scm_raprin1 -> scm_display or scm_write | |
1839 | ||
0c7a5cab MV |
1840 | SCM_ARRAYP -> scm_is_array |
1841 | SCM_ARRAY_NDIM -> scm_c_array_rank | |
1842 | SCM_ARRAY_DIMS -> scm_array_handle_dims | |
1843 | SCM_ARRAY_CONTP -> do not use | |
1844 | SCM_ARRAY_MEM -> do not use | |
1845 | SCM_ARRAY_V -> scm_array_handle_elements or similar | |
1846 | SCM_ARRAY_BASE -> do not use | |
1847 | ||
c1e7caf7 MV |
1848 | ** SCM_CELL_WORD_LOC has been deprecated. |
1849 | ||
b0d10ba6 | 1850 | Use the new macro SCM_CELL_OBJECT_LOC instead, which returns a pointer |
c1e7caf7 MV |
1851 | to a SCM, as opposed to a pointer to a scm_t_bits. |
1852 | ||
1853 | This was done to allow the correct use of pointers into the Scheme | |
1854 | heap. Previously, the heap words were of type scm_t_bits and local | |
1855 | variables and function arguments were of type SCM, making it | |
1856 | non-standards-conformant to have a pointer that can point to both. | |
1857 | ||
3ff9283d | 1858 | ** New macros SCM_SMOB_DATA_2, SCM_SMOB_DATA_3, etc. |
27968825 MV |
1859 | |
1860 | These macros should be used instead of SCM_CELL_WORD_2/3 to access the | |
1861 | second and third words of double smobs. Likewise for | |
1862 | SCM_SET_SMOB_DATA_2 and SCM_SET_SMOB_DATA_3. | |
1863 | ||
1864 | Also, there is SCM_SMOB_FLAGS and SCM_SET_SMOB_FLAGS that should be | |
1865 | used to get and set the 16 exra bits in the zeroth word of a smob. | |
1866 | ||
1867 | And finally, there is SCM_SMOB_OBJECT and SCM_SMOB_SET_OBJECT for | |
1868 | accesing the first immediate word of a smob as a SCM value, and there | |
1869 | is SCM_SMOB_OBJECT_LOC for getting a pointer to the first immediate | |
b0d10ba6 | 1870 | smob word. Like wise for SCM_SMOB_OBJECT_2, etc. |
27968825 | 1871 | |
b0d10ba6 | 1872 | ** New way to deal with non-local exits and re-entries. |
9879d390 MV |
1873 | |
1874 | There is a new set of functions that essentially do what | |
fc6bb283 MV |
1875 | scm_internal_dynamic_wind does, but in a way that is more convenient |
1876 | for C code in some situations. Here is a quick example of how to | |
1877 | prevent a potential memory leak: | |
9879d390 MV |
1878 | |
1879 | void | |
1880 | foo () | |
1881 | { | |
1882 | char *mem; | |
1883 | ||
661ae7ab | 1884 | scm_dynwind_begin (0); |
9879d390 MV |
1885 | |
1886 | mem = scm_malloc (100); | |
661ae7ab | 1887 | scm_dynwind_unwind_handler (free, mem, SCM_F_WIND_EXPLICITLY); |
f1da8e4e MV |
1888 | |
1889 | /* MEM would leak if BAR throws an error. | |
661ae7ab | 1890 | SCM_DYNWIND_UNWIND_HANDLER frees it nevertheless. |
c41acab3 | 1891 | */ |
9879d390 | 1892 | |
9879d390 MV |
1893 | bar (); |
1894 | ||
661ae7ab | 1895 | scm_dynwind_end (); |
9879d390 | 1896 | |
e299cee2 | 1897 | /* Because of SCM_F_WIND_EXPLICITLY, MEM will be freed by |
661ae7ab | 1898 | SCM_DYNWIND_END as well. |
9879d390 MV |
1899 | */ |
1900 | } | |
1901 | ||
661ae7ab | 1902 | For full documentation, see the node "Dynamic Wind" in the manual. |
9879d390 | 1903 | |
661ae7ab | 1904 | ** New function scm_dynwind_free |
c41acab3 | 1905 | |
661ae7ab MV |
1906 | This function calls 'free' on a given pointer when a dynwind context |
1907 | is left. Thus the call to scm_dynwind_unwind_handler above could be | |
1908 | replaced with simply scm_dynwind_free (mem). | |
c41acab3 | 1909 | |
a6d75e53 MV |
1910 | ** New functions scm_c_call_with_blocked_asyncs and |
1911 | scm_c_call_with_unblocked_asyncs | |
1912 | ||
1913 | Like scm_call_with_blocked_asyncs etc. but for C functions. | |
1914 | ||
661ae7ab | 1915 | ** New functions scm_dynwind_block_asyncs and scm_dynwind_unblock_asyncs |
49c00ecc MV |
1916 | |
1917 | In addition to scm_c_call_with_blocked_asyncs you can now also use | |
661ae7ab MV |
1918 | scm_dynwind_block_asyncs in a 'dynwind context' (see above). Likewise for |
1919 | scm_c_call_with_unblocked_asyncs and scm_dynwind_unblock_asyncs. | |
49c00ecc | 1920 | |
a558cc63 MV |
1921 | ** The macros SCM_DEFER_INTS, SCM_ALLOW_INTS, SCM_REDEFER_INTS, |
1922 | SCM_REALLOW_INTS have been deprecated. | |
1923 | ||
1924 | They do no longer fulfill their original role of blocking signal | |
1925 | delivery. Depending on what you want to achieve, replace a pair of | |
661ae7ab MV |
1926 | SCM_DEFER_INTS and SCM_ALLOW_INTS with a dynwind context that locks a |
1927 | mutex, blocks asyncs, or both. See node "Critical Sections" in the | |
1928 | manual. | |
a6d75e53 MV |
1929 | |
1930 | ** The value 'scm_mask_ints' is no longer writable. | |
1931 | ||
1932 | Previously, you could set scm_mask_ints directly. This is no longer | |
1933 | possible. Use scm_c_call_with_blocked_asyncs and | |
1934 | scm_c_call_with_unblocked_asyncs instead. | |
a558cc63 | 1935 | |
49c00ecc MV |
1936 | ** New way to temporarily set the current input, output or error ports |
1937 | ||
661ae7ab | 1938 | C code can now use scm_dynwind_current_<foo>_port in a 'dynwind |
0f24e75b | 1939 | context' (see above). <foo> is one of "input", "output" or "error". |
49c00ecc | 1940 | |
fc6bb283 MV |
1941 | ** New way to temporarily set fluids |
1942 | ||
661ae7ab | 1943 | C code can now use scm_dynwind_fluid in a 'dynwind context' (see |
fc6bb283 MV |
1944 | above) to temporarily set the value of a fluid. |
1945 | ||
89fcf1b4 MV |
1946 | ** New types scm_t_intmax and scm_t_uintmax. |
1947 | ||
1948 | On platforms that have them, these types are identical to intmax_t and | |
1949 | uintmax_t, respectively. On other platforms, they are identical to | |
1950 | the largest integer types that Guile knows about. | |
1951 | ||
b0d10ba6 | 1952 | ** The functions scm_unmemocopy and scm_unmemoize have been removed. |
9fcf3cbb | 1953 | |
b0d10ba6 | 1954 | You should not have used them. |
9fcf3cbb | 1955 | |
5ebbe4ef RB |
1956 | ** Many public #defines with generic names have been made private. |
1957 | ||
1958 | #defines with generic names like HAVE_FOO or SIZEOF_FOO have been made | |
b0d10ba6 | 1959 | private or renamed with a more suitable public name. |
f03314f9 DH |
1960 | |
1961 | ** The macro SCM_TYP16S has been deprecated. | |
1962 | ||
b0d10ba6 | 1963 | This macro is not intended for public use. |
f03314f9 | 1964 | |
0d5e3480 DH |
1965 | ** The macro SCM_SLOPPY_INEXACTP has been deprecated. |
1966 | ||
b0d10ba6 | 1967 | Use scm_is_true (scm_inexact_p (...)) instead. |
0d5e3480 DH |
1968 | |
1969 | ** The macro SCM_SLOPPY_REALP has been deprecated. | |
1970 | ||
b0d10ba6 | 1971 | Use scm_is_real instead. |
0d5e3480 DH |
1972 | |
1973 | ** The macro SCM_SLOPPY_COMPLEXP has been deprecated. | |
1974 | ||
b0d10ba6 | 1975 | Use scm_is_complex instead. |
5ebbe4ef | 1976 | |
b0d10ba6 | 1977 | ** Some preprocessor defines have been deprecated. |
5ebbe4ef | 1978 | |
b0d10ba6 MV |
1979 | These defines indicated whether a certain feature was present in Guile |
1980 | or not. Going forward, assume that the features are always present. | |
5ebbe4ef | 1981 | |
b0d10ba6 MV |
1982 | The macros are: USE_THREADS, GUILE_ISELECT, READER_EXTENSIONS, |
1983 | DEBUG_EXTENSIONS, DYNAMIC_LINKING. | |
5ebbe4ef | 1984 | |
b0d10ba6 MV |
1985 | The following macros have been removed completely: MEMOIZE_LOCALS, |
1986 | SCM_RECKLESS, SCM_CAUTIOUS. | |
5ebbe4ef RB |
1987 | |
1988 | ** The preprocessor define STACK_DIRECTION has been deprecated. | |
1989 | ||
1990 | There should be no need to know about the stack direction for ordinary | |
b0d10ba6 | 1991 | programs. |
5ebbe4ef | 1992 | |
b2cbe8d8 RB |
1993 | ** New function: scm_effective_version |
1994 | ||
1995 | Returns the "effective" version number. This is just the normal full | |
1996 | version string without the final micro-version number. See "Changes | |
1997 | to the distribution" above. | |
1998 | ||
2902a459 MV |
1999 | ** The function scm_call_with_new_thread has a new prototype. |
2000 | ||
2001 | Instead of taking a list with the thunk and handler, these two | |
2002 | arguments are now passed directly: | |
2003 | ||
2004 | SCM scm_call_with_new_thread (SCM thunk, SCM handler); | |
2005 | ||
2006 | This is an incompatible change. | |
2007 | ||
ffd0ef3b MV |
2008 | ** New snarfer macro SCM_DEFINE_PUBLIC. |
2009 | ||
2010 | This is like SCM_DEFINE, but also calls scm_c_export for the defined | |
2011 | function in the init section. | |
2012 | ||
8734ce02 MV |
2013 | ** The snarfer macro SCM_SNARF_INIT is now officially supported. |
2014 | ||
39e8f371 HWN |
2015 | ** Garbage collector rewrite. |
2016 | ||
2017 | The garbage collector is cleaned up a lot, and now uses lazy | |
2018 | sweeping. This is reflected in the output of (gc-stats); since cells | |
2019 | are being freed when they are allocated, the cells-allocated field | |
2020 | stays roughly constant. | |
2021 | ||
2022 | For malloc related triggers, the behavior is changed. It uses the same | |
2023 | heuristic as the cell-triggered collections. It may be tuned with the | |
2024 | environment variables GUILE_MIN_YIELD_MALLOC. This is the percentage | |
2025 | for minimum yield of malloc related triggers. The default is 40. | |
2026 | GUILE_INIT_MALLOC_LIMIT sets the initial trigger for doing a GC. The | |
2027 | default is 200 kb. | |
2028 | ||
2029 | Debugging operations for the freelist have been deprecated, along with | |
2030 | the C variables that control garbage collection. The environment | |
2031 | variables GUILE_MAX_SEGMENT_SIZE, GUILE_INIT_SEGMENT_SIZE_2, | |
2032 | GUILE_INIT_SEGMENT_SIZE_1, and GUILE_MIN_YIELD_2 should be used. | |
2033 | ||
1367aa5e HWN |
2034 | For understanding the memory usage of a GUILE program, the routine |
2035 | gc-live-object-stats returns an alist containing the number of live | |
2036 | objects for every type. | |
2037 | ||
2038 | ||
5ec1d2c8 DH |
2039 | ** The function scm_definedp has been renamed to scm_defined_p |
2040 | ||
2041 | The name scm_definedp is deprecated. | |
2042 | ||
b0d10ba6 | 2043 | ** The struct scm_cell type has been renamed to scm_t_cell |
228a24ef DH |
2044 | |
2045 | This is in accordance to Guile's naming scheme for types. Note that | |
2046 | the name scm_cell is now used for a function that allocates and | |
2047 | initializes a new cell (see below). | |
2048 | ||
0906625f MV |
2049 | ** New functions for memory management |
2050 | ||
2051 | A new set of functions for memory management has been added since the | |
2052 | old way (scm_must_malloc, scm_must_free, etc) was error prone and | |
2053 | indeed, Guile itself contained some long standing bugs that could | |
2054 | cause aborts in long running programs. | |
2055 | ||
2056 | The new functions are more symmetrical and do not need cooperation | |
2057 | from smob free routines, among other improvements. | |
2058 | ||
eab1b259 HWN |
2059 | The new functions are scm_malloc, scm_realloc, scm_calloc, scm_strdup, |
2060 | scm_strndup, scm_gc_malloc, scm_gc_calloc, scm_gc_realloc, | |
2061 | scm_gc_free, scm_gc_register_collectable_memory, and | |
0906625f MV |
2062 | scm_gc_unregister_collectable_memory. Refer to the manual for more |
2063 | details and for upgrading instructions. | |
2064 | ||
2065 | The old functions for memory management have been deprecated. They | |
2066 | are: scm_must_malloc, scm_must_realloc, scm_must_free, | |
2067 | scm_must_strdup, scm_must_strndup, scm_done_malloc, scm_done_free. | |
2068 | ||
4aa104a4 MV |
2069 | ** Declarations of exported features are marked with SCM_API. |
2070 | ||
2071 | Every declaration of a feature that belongs to the exported Guile API | |
2072 | has been marked by adding the macro "SCM_API" to the start of the | |
2073 | declaration. This macro can expand into different things, the most | |
2074 | common of which is just "extern" for Unix platforms. On Win32, it can | |
2075 | be used to control which symbols are exported from a DLL. | |
2076 | ||
8f99e3f3 | 2077 | If you `#define SCM_IMPORT' before including <libguile.h>, SCM_API |
4aa104a4 MV |
2078 | will expand into "__declspec (dllimport) extern", which is needed for |
2079 | linking to the Guile DLL in Windows. | |
2080 | ||
b0d10ba6 | 2081 | There are also SCM_RL_IMPORT, SCM_SRFI1314_IMPORT, and |
8f99e3f3 | 2082 | SCM_SRFI4_IMPORT, for the corresponding libraries. |
4aa104a4 | 2083 | |
a9930d22 MV |
2084 | ** SCM_NEWCELL and SCM_NEWCELL2 have been deprecated. |
2085 | ||
b0d10ba6 MV |
2086 | Use the new functions scm_cell and scm_double_cell instead. The old |
2087 | macros had problems because with them allocation and initialization | |
2088 | was separated and the GC could sometimes observe half initialized | |
2089 | cells. Only careful coding by the user of SCM_NEWCELL and | |
2090 | SCM_NEWCELL2 could make this safe and efficient. | |
a9930d22 | 2091 | |
5132eef0 DH |
2092 | ** CHECK_ENTRY, CHECK_APPLY and CHECK_EXIT have been deprecated. |
2093 | ||
2094 | Use the variables scm_check_entry_p, scm_check_apply_p and scm_check_exit_p | |
2095 | instead. | |
2096 | ||
bc76d628 DH |
2097 | ** SRCBRKP has been deprecated. |
2098 | ||
2099 | Use scm_c_source_property_breakpoint_p instead. | |
2100 | ||
3063e30a DH |
2101 | ** Deprecated: scm_makmacro |
2102 | ||
b0d10ba6 MV |
2103 | Change your code to use either scm_makmmacro or to define macros in |
2104 | Scheme, using 'define-macro'. | |
1e5f92ce | 2105 | |
1a61d41b MV |
2106 | ** New function scm_c_port_for_each. |
2107 | ||
2108 | This function is like scm_port_for_each but takes a pointer to a C | |
2109 | function as the callback instead of a SCM value. | |
2110 | ||
1f834c95 MV |
2111 | ** The names scm_internal_select, scm_thread_sleep, and |
2112 | scm_thread_usleep have been discouraged. | |
2113 | ||
2114 | Use scm_std_select, scm_std_sleep, scm_std_usleep instead. | |
2115 | ||
aa9200e5 MV |
2116 | ** The GC can no longer be blocked. |
2117 | ||
2118 | The global flags scm_gc_heap_lock and scm_block_gc have been removed. | |
2119 | The GC can now run (partially) concurrently with other code and thus | |
2120 | blocking it is not well defined. | |
2121 | ||
b0d10ba6 MV |
2122 | ** Many definitions have been removed that were previously deprecated. |
2123 | ||
2124 | scm_lisp_nil, scm_lisp_t, s_nil_ify, scm_m_nil_ify, s_t_ify, | |
2125 | scm_m_t_ify, s_0_cond, scm_m_0_cond, s_0_ify, scm_m_0_ify, s_1_ify, | |
2126 | scm_m_1_ify, scm_debug_newcell, scm_debug_newcell2, | |
2127 | scm_tc16_allocated, SCM_SET_SYMBOL_HASH, SCM_IM_NIL_IFY, SCM_IM_T_IFY, | |
2128 | SCM_IM_0_COND, SCM_IM_0_IFY, SCM_IM_1_IFY, SCM_GC_SET_ALLOCATED, | |
2129 | scm_debug_newcell, scm_debug_newcell2, SCM_HUP_SIGNAL, SCM_INT_SIGNAL, | |
2130 | SCM_FPE_SIGNAL, SCM_BUS_SIGNAL, SCM_SEGV_SIGNAL, SCM_ALRM_SIGNAL, | |
2131 | SCM_GC_SIGNAL, SCM_TICK_SIGNAL, SCM_SIG_ORD, SCM_ORD_SIG, | |
2132 | SCM_NUM_SIGS, scm_top_level_lookup_closure_var, | |
2133 | *top-level-lookup-closure*, scm_system_transformer, scm_eval_3, | |
2134 | scm_eval2, root_module_lookup_closure, SCM_SLOPPY_STRINGP, | |
2135 | SCM_RWSTRINGP, scm_read_only_string_p, scm_make_shared_substring, | |
2136 | scm_tc7_substring, sym_huh, SCM_VARVCELL, SCM_UDVARIABLEP, | |
2137 | SCM_DEFVARIABLEP, scm_mkbig, scm_big2inum, scm_adjbig, scm_normbig, | |
2138 | scm_copybig, scm_2ulong2big, scm_dbl2big, scm_big2dbl, SCM_FIXNUM_BIT, | |
2139 | SCM_SETCHARS, SCM_SLOPPY_SUBSTRP, SCM_SUBSTR_STR, SCM_SUBSTR_OFFSET, | |
2140 | SCM_LENGTH_MAX, SCM_SETLENGTH, SCM_ROSTRINGP, SCM_ROLENGTH, | |
2141 | SCM_ROCHARS, SCM_ROUCHARS, SCM_SUBSTRP, SCM_COERCE_SUBSTR, | |
2142 | scm_sym2vcell, scm_intern, scm_intern0, scm_sysintern, scm_sysintern0, | |
66c8ded2 | 2143 | scm_sysintern0_no_module_lookup, scm_init_symbols_deprecated, |
2109da78 | 2144 | scm_vector_set_length_x, scm_contregs, scm_debug_info, |
983e697d MV |
2145 | scm_debug_frame, SCM_DSIDEVAL, SCM_CONST_LONG, SCM_VCELL, |
2146 | SCM_GLOBAL_VCELL, SCM_VCELL_INIT, SCM_GLOBAL_VCELL_INIT, | |
2147 | SCM_HUGE_LENGTH, SCM_VALIDATE_STRINGORSUBSTR, SCM_VALIDATE_ROSTRING, | |
2148 | SCM_VALIDATE_ROSTRING_COPY, SCM_VALIDATE_NULLORROSTRING_COPY, | |
2149 | SCM_VALIDATE_RWSTRING, DIGITS, scm_small_istr2int, scm_istr2int, | |
2109da78 MV |
2150 | scm_istr2flo, scm_istring2number, scm_istr2int, scm_istr2flo, |
2151 | scm_istring2number, scm_vtable_index_vcell, scm_si_vcell, SCM_ECONSP, | |
2152 | SCM_NECONSP, SCM_GLOC_VAR, SCM_GLOC_VAL, SCM_GLOC_SET_VAL, | |
c41acab3 MV |
2153 | SCM_GLOC_VAL_LOC, scm_make_gloc, scm_gloc_p, scm_tc16_variable, |
2154 | SCM_CHARS, SCM_LENGTH, SCM_SET_STRING_CHARS, SCM_SET_STRING_LENGTH. | |
b51bad08 | 2155 | |
09172f9c NJ |
2156 | * Changes to bundled modules |
2157 | ||
2158 | ** (ice-9 debug) | |
2159 | ||
2160 | Using the (ice-9 debug) module no longer automatically switches Guile | |
2161 | to use the debugging evaluator. If you want to switch to the | |
2162 | debugging evaluator (which is needed for backtrace information if you | |
2163 | hit an error), please add an explicit "(debug-enable 'debug)" to your | |
2164 | code just after the code to use (ice-9 debug). | |
2165 | ||
328dc9a3 | 2166 | \f |
c299f186 MD |
2167 | Changes since Guile 1.4: |
2168 | ||
2169 | * Changes to the distribution | |
2170 | ||
32d6f999 TTN |
2171 | ** A top-level TODO file is included. |
2172 | ||
311b6a3c | 2173 | ** Guile now uses a versioning scheme similar to that of the Linux kernel. |
c81ea65d RB |
2174 | |
2175 | Guile now always uses three numbers to represent the version, | |
2176 | i.e. "1.6.5". The first number, 1, is the major version number, the | |
2177 | second number, 6, is the minor version number, and the third number, | |
2178 | 5, is the micro version number. Changes in major version number | |
2179 | indicate major changes in Guile. | |
2180 | ||
2181 | Minor version numbers that are even denote stable releases, and odd | |
2182 | minor version numbers denote development versions (which may be | |
2183 | unstable). The micro version number indicates a minor sub-revision of | |
2184 | a given MAJOR.MINOR release. | |
2185 | ||
2186 | In keeping with the new scheme, (minor-version) and scm_minor_version | |
2187 | no longer return everything but the major version number. They now | |
2188 | just return the minor version number. Two new functions | |
2189 | (micro-version) and scm_micro_version have been added to report the | |
2190 | micro version number. | |
2191 | ||
2192 | In addition, ./GUILE-VERSION now defines GUILE_MICRO_VERSION. | |
2193 | ||
5c790b44 RB |
2194 | ** New preprocessor definitions are available for checking versions. |
2195 | ||
2196 | version.h now #defines SCM_MAJOR_VERSION, SCM_MINOR_VERSION, and | |
2197 | SCM_MICRO_VERSION to the appropriate integer values. | |
2198 | ||
311b6a3c MV |
2199 | ** Guile now actively warns about deprecated features. |
2200 | ||
2201 | The new configure option `--enable-deprecated=LEVEL' and the | |
2202 | environment variable GUILE_WARN_DEPRECATED control this mechanism. | |
2203 | See INSTALL and README for more information. | |
2204 | ||
0b073f0f RB |
2205 | ** Guile is much more likely to work on 64-bit architectures. |
2206 | ||
2207 | Guile now compiles and passes "make check" with only two UNRESOLVED GC | |
5e137c65 RB |
2208 | cases on Alpha and ia64 based machines now. Thanks to John Goerzen |
2209 | for the use of a test machine, and thanks to Stefan Jahn for ia64 | |
2210 | patches. | |
0b073f0f | 2211 | |
e658215a RB |
2212 | ** New functions: setitimer and getitimer. |
2213 | ||
2214 | These implement a fairly direct interface to the libc functions of the | |
2215 | same name. | |
2216 | ||
8630fdfc RB |
2217 | ** The #. reader extension is now disabled by default. |
2218 | ||
2219 | For safety reasons, #. evaluation is disabled by default. To | |
2220 | re-enable it, set the fluid read-eval? to #t. For example: | |
2221 | ||
67b7dd9e | 2222 | (fluid-set! read-eval? #t) |
8630fdfc RB |
2223 | |
2224 | but make sure you realize the potential security risks involved. With | |
2225 | read-eval? enabled, reading a data file from an untrusted source can | |
2226 | be dangerous. | |
2227 | ||
f2a75d81 | 2228 | ** New SRFI modules have been added: |
4df36934 | 2229 | |
dfdf5826 MG |
2230 | SRFI-0 `cond-expand' is now supported in Guile, without requiring |
2231 | using a module. | |
2232 | ||
e8bb0476 MG |
2233 | (srfi srfi-1) is a library containing many useful pair- and list-processing |
2234 | procedures. | |
2235 | ||
7adc2c58 | 2236 | (srfi srfi-2) exports and-let*. |
4df36934 | 2237 | |
b74a7ec8 MG |
2238 | (srfi srfi-4) implements homogeneous numeric vector datatypes. |
2239 | ||
7adc2c58 RB |
2240 | (srfi srfi-6) is a dummy module for now, since guile already provides |
2241 | all of the srfi-6 procedures by default: open-input-string, | |
2242 | open-output-string, get-output-string. | |
4df36934 | 2243 | |
7adc2c58 | 2244 | (srfi srfi-8) exports receive. |
4df36934 | 2245 | |
7adc2c58 | 2246 | (srfi srfi-9) exports define-record-type. |
4df36934 | 2247 | |
dfdf5826 MG |
2248 | (srfi srfi-10) exports define-reader-ctor and implements the reader |
2249 | extension #,(). | |
2250 | ||
7adc2c58 | 2251 | (srfi srfi-11) exports let-values and let*-values. |
4df36934 | 2252 | |
7adc2c58 | 2253 | (srfi srfi-13) implements the SRFI String Library. |
53e29a1e | 2254 | |
7adc2c58 | 2255 | (srfi srfi-14) implements the SRFI Character-Set Library. |
53e29a1e | 2256 | |
dfdf5826 MG |
2257 | (srfi srfi-17) implements setter and getter-with-setter and redefines |
2258 | some accessor procedures as procedures with getters. (such as car, | |
2259 | cdr, vector-ref etc.) | |
2260 | ||
2261 | (srfi srfi-19) implements the SRFI Time/Date Library. | |
2b60bc95 | 2262 | |
466bb4b3 TTN |
2263 | ** New scripts / "executable modules" |
2264 | ||
2265 | Subdirectory "scripts" contains Scheme modules that are packaged to | |
2266 | also be executable as scripts. At this time, these scripts are available: | |
2267 | ||
2268 | display-commentary | |
2269 | doc-snarf | |
2270 | generate-autoload | |
2271 | punify | |
58e5b910 | 2272 | read-scheme-source |
466bb4b3 TTN |
2273 | use2dot |
2274 | ||
2275 | See README there for more info. | |
2276 | ||
54c17ccb TTN |
2277 | These scripts can be invoked from the shell with the new program |
2278 | "guile-tools", which keeps track of installation directory for you. | |
2279 | For example: | |
2280 | ||
2281 | $ guile-tools display-commentary srfi/*.scm | |
2282 | ||
2283 | guile-tools is copied to the standard $bindir on "make install". | |
2284 | ||
0109c4bf MD |
2285 | ** New module (ice-9 stack-catch): |
2286 | ||
2287 | stack-catch is like catch, but saves the current state of the stack in | |
3c1d1301 RB |
2288 | the fluid the-last-stack. This fluid can be useful when using the |
2289 | debugger and when re-throwing an error. | |
0109c4bf | 2290 | |
fbf0c8c7 MV |
2291 | ** The module (ice-9 and-let*) has been renamed to (ice-9 and-let-star) |
2292 | ||
2293 | This has been done to prevent problems on lesser operating systems | |
2294 | that can't tolerate `*'s in file names. The exported macro continues | |
2295 | to be named `and-let*', of course. | |
2296 | ||
4f60cc33 | 2297 | On systems that support it, there is also a compatibility module named |
fbf0c8c7 | 2298 | (ice-9 and-let*). It will go away in the next release. |
6c0201ad | 2299 | |
9d774814 | 2300 | ** New modules (oop goops) etc.: |
14f1d9fe MD |
2301 | |
2302 | (oop goops) | |
2303 | (oop goops describe) | |
2304 | (oop goops save) | |
2305 | (oop goops active-slot) | |
2306 | (oop goops composite-slot) | |
2307 | ||
9d774814 | 2308 | The Guile Object Oriented Programming System (GOOPS) has been |
311b6a3c MV |
2309 | integrated into Guile. For further information, consult the GOOPS |
2310 | manual and tutorial in the `doc' directory. | |
14f1d9fe | 2311 | |
9d774814 GH |
2312 | ** New module (ice-9 rdelim). |
2313 | ||
2314 | This exports the following procedures which were previously defined | |
1c8cbd62 | 2315 | in the default environment: |
9d774814 | 2316 | |
1c8cbd62 GH |
2317 | read-line read-line! read-delimited read-delimited! %read-delimited! |
2318 | %read-line write-line | |
9d774814 | 2319 | |
1c8cbd62 GH |
2320 | For backwards compatibility the definitions are still imported into the |
2321 | default environment in this version of Guile. However you should add: | |
9d774814 GH |
2322 | |
2323 | (use-modules (ice-9 rdelim)) | |
2324 | ||
1c8cbd62 GH |
2325 | to any program which uses the definitions, since this may change in |
2326 | future. | |
9d774814 GH |
2327 | |
2328 | Alternatively, if guile-scsh is installed, the (scsh rdelim) module | |
2329 | can be used for similar functionality. | |
2330 | ||
7e267da1 GH |
2331 | ** New module (ice-9 rw) |
2332 | ||
2333 | This is a subset of the (scsh rw) module from guile-scsh. Currently | |
373f4948 | 2334 | it defines two procedures: |
7e267da1 | 2335 | |
311b6a3c | 2336 | *** New function: read-string!/partial str [port_or_fdes [start [end]]] |
7e267da1 | 2337 | |
4bcdfe46 GH |
2338 | Read characters from a port or file descriptor into a string STR. |
2339 | A port must have an underlying file descriptor -- a so-called | |
2340 | fport. This procedure is scsh-compatible and can efficiently read | |
311b6a3c | 2341 | large strings. |
7e267da1 | 2342 | |
4bcdfe46 GH |
2343 | *** New function: write-string/partial str [port_or_fdes [start [end]]] |
2344 | ||
2345 | Write characters from a string STR to a port or file descriptor. | |
2346 | A port must have an underlying file descriptor -- a so-called | |
2347 | fport. This procedure is mostly compatible and can efficiently | |
2348 | write large strings. | |
2349 | ||
e5005373 KN |
2350 | ** New module (ice-9 match) |
2351 | ||
311b6a3c MV |
2352 | This module includes Andrew K. Wright's pattern matcher. See |
2353 | ice-9/match.scm for brief description or | |
e5005373 | 2354 | |
311b6a3c | 2355 | http://www.star-lab.com/wright/code.html |
e5005373 | 2356 | |
311b6a3c | 2357 | for complete documentation. |
e5005373 | 2358 | |
4f60cc33 NJ |
2359 | ** New module (ice-9 buffered-input) |
2360 | ||
2361 | This module provides procedures to construct an input port from an | |
2362 | underlying source of input that reads and returns its input in chunks. | |
2363 | The underlying input source is a Scheme procedure, specified by the | |
2364 | caller, which the port invokes whenever it needs more input. | |
2365 | ||
2366 | This is useful when building an input port whose back end is Readline | |
2367 | or a UI element such as the GtkEntry widget. | |
2368 | ||
2369 | ** Documentation | |
2370 | ||
2371 | The reference and tutorial documentation that was previously | |
2372 | distributed separately, as `guile-doc', is now included in the core | |
2373 | Guile distribution. The documentation consists of the following | |
2374 | manuals. | |
2375 | ||
2376 | - The Guile Tutorial (guile-tut.texi) contains a tutorial introduction | |
2377 | to using Guile. | |
2378 | ||
2379 | - The Guile Reference Manual (guile.texi) contains (or is intended to | |
2380 | contain) reference documentation on all aspects of Guile. | |
2381 | ||
2382 | - The GOOPS Manual (goops.texi) contains both tutorial-style and | |
2383 | reference documentation for using GOOPS, Guile's Object Oriented | |
2384 | Programming System. | |
2385 | ||
c3e62877 NJ |
2386 | - The Revised^5 Report on the Algorithmic Language Scheme |
2387 | (r5rs.texi). | |
4f60cc33 NJ |
2388 | |
2389 | See the README file in the `doc' directory for more details. | |
2390 | ||
094a67bb MV |
2391 | ** There are a couple of examples in the examples/ directory now. |
2392 | ||
9d774814 GH |
2393 | * Changes to the stand-alone interpreter |
2394 | ||
e7e58018 MG |
2395 | ** New command line option `--use-srfi' |
2396 | ||
2397 | Using this option, SRFI modules can be loaded on startup and be | |
2398 | available right from the beginning. This makes programming portable | |
2399 | Scheme programs easier. | |
2400 | ||
2401 | The option `--use-srfi' expects a comma-separated list of numbers, | |
2402 | each representing a SRFI number to be loaded into the interpreter | |
2403 | before starting evaluating a script file or the REPL. Additionally, | |
2404 | the feature identifier for the loaded SRFIs is recognized by | |
2405 | `cond-expand' when using this option. | |
2406 | ||
2407 | Example: | |
2408 | $ guile --use-srfi=8,13 | |
2409 | guile> (receive (x z) (values 1 2) (+ 1 2)) | |
2410 | 3 | |
58e5b910 | 2411 | guile> (string-pad "bla" 20) |
e7e58018 MG |
2412 | " bla" |
2413 | ||
094a67bb MV |
2414 | ** Guile now always starts up in the `(guile-user)' module. |
2415 | ||
6e9382f1 | 2416 | Previously, scripts executed via the `-s' option would run in the |
094a67bb MV |
2417 | `(guile)' module and the repl would run in the `(guile-user)' module. |
2418 | Now every user action takes place in the `(guile-user)' module by | |
2419 | default. | |
e7e58018 | 2420 | |
c299f186 MD |
2421 | * Changes to Scheme functions and syntax |
2422 | ||
720e1c30 MV |
2423 | ** Character classifiers work for non-ASCII characters. |
2424 | ||
2425 | The predicates `char-alphabetic?', `char-numeric?', | |
2426 | `char-whitespace?', `char-lower?', `char-upper?' and `char-is-both?' | |
2427 | no longer check whether their arguments are ASCII characters. | |
2428 | Previously, a character would only be considered alphabetic when it | |
2429 | was also ASCII, for example. | |
2430 | ||
311b6a3c MV |
2431 | ** Previously deprecated Scheme functions have been removed: |
2432 | ||
2433 | tag - no replacement. | |
2434 | fseek - replaced by seek. | |
2435 | list* - replaced by cons*. | |
2436 | ||
2437 | ** It's now possible to create modules with controlled environments | |
2438 | ||
2439 | Example: | |
2440 | ||
2441 | (use-modules (ice-9 safe)) | |
2442 | (define m (make-safe-module)) | |
2443 | ;;; m will now be a module containing only a safe subset of R5RS | |
2444 | (eval '(+ 1 2) m) --> 3 | |
2445 | (eval 'load m) --> ERROR: Unbound variable: load | |
2446 | ||
2447 | ** Evaluation of "()", the empty list, is now an error. | |
8c2c9967 MV |
2448 | |
2449 | Previously, the expression "()" evaluated to the empty list. This has | |
2450 | been changed to signal a "missing expression" error. The correct way | |
2451 | to write the empty list as a literal constant is to use quote: "'()". | |
2452 | ||
311b6a3c MV |
2453 | ** New concept of `Guile Extensions'. |
2454 | ||
2455 | A Guile Extension is just a ordinary shared library that can be linked | |
2456 | at run-time. We found it advantageous to give this simple concept a | |
2457 | dedicated name to distinguish the issues related to shared libraries | |
2458 | from the issues related to the module system. | |
2459 | ||
2460 | *** New function: load-extension | |
2461 | ||
2462 | Executing (load-extension lib init) is mostly equivalent to | |
2463 | ||
2464 | (dynamic-call init (dynamic-link lib)) | |
2465 | ||
2466 | except when scm_register_extension has been called previously. | |
2467 | Whenever appropriate, you should use `load-extension' instead of | |
2468 | dynamic-link and dynamic-call. | |
2469 | ||
2470 | *** New C function: scm_c_register_extension | |
2471 | ||
2472 | This function registers a initialization function for use by | |
2473 | `load-extension'. Use it when you don't want specific extensions to | |
2474 | be loaded as shared libraries (for example on platforms that don't | |
2475 | support dynamic linking). | |
2476 | ||
8c2c9967 MV |
2477 | ** Auto-loading of compiled-code modules is deprecated. |
2478 | ||
2479 | Guile used to be able to automatically find and link a shared | |
c10ecc4c | 2480 | library to satisfy requests for a module. For example, the module |
8c2c9967 MV |
2481 | `(foo bar)' could be implemented by placing a shared library named |
2482 | "foo/libbar.so" (or with a different extension) in a directory on the | |
2483 | load path of Guile. | |
2484 | ||
311b6a3c MV |
2485 | This has been found to be too tricky, and is no longer supported. The |
2486 | shared libraries are now called "extensions". You should now write a | |
2487 | small Scheme file that calls `load-extension' to load the shared | |
e299cee2 | 2488 | library and initialize it explicitly. |
8c2c9967 MV |
2489 | |
2490 | The shared libraries themselves should be installed in the usual | |
2491 | places for shared libraries, with names like "libguile-foo-bar". | |
2492 | ||
2493 | For example, place this into a file "foo/bar.scm" | |
2494 | ||
2495 | (define-module (foo bar)) | |
2496 | ||
311b6a3c MV |
2497 | (load-extension "libguile-foo-bar" "foobar_init") |
2498 | ||
2499 | ** Backward incompatible change: eval EXP ENVIRONMENT-SPECIFIER | |
2500 | ||
2501 | `eval' is now R5RS, that is it takes two arguments. | |
2502 | The second argument is an environment specifier, i.e. either | |
2503 | ||
2504 | (scheme-report-environment 5) | |
2505 | (null-environment 5) | |
2506 | (interaction-environment) | |
2507 | ||
2508 | or | |
8c2c9967 | 2509 | |
311b6a3c | 2510 | any module. |
8c2c9967 | 2511 | |
6f76852b MV |
2512 | ** The module system has been made more disciplined. |
2513 | ||
311b6a3c MV |
2514 | The function `eval' will save and restore the current module around |
2515 | the evaluation of the specified expression. While this expression is | |
2516 | evaluated, `(current-module)' will now return the right module, which | |
2517 | is the module specified as the second argument to `eval'. | |
6f76852b | 2518 | |
311b6a3c | 2519 | A consequence of this change is that `eval' is not particularly |
6f76852b MV |
2520 | useful when you want allow the evaluated code to change what module is |
2521 | designated as the current module and have this change persist from one | |
2522 | call to `eval' to the next. The read-eval-print-loop is an example | |
2523 | where `eval' is now inadequate. To compensate, there is a new | |
2524 | function `primitive-eval' that does not take a module specifier and | |
2525 | that does not save/restore the current module. You should use this | |
2526 | function together with `set-current-module', `current-module', etc | |
2527 | when you want to have more control over the state that is carried from | |
2528 | one eval to the next. | |
2529 | ||
2530 | Additionally, it has been made sure that forms that are evaluated at | |
2531 | the top level are always evaluated with respect to the current module. | |
2532 | Previously, subforms of top-level forms such as `begin', `case', | |
2533 | etc. did not respect changes to the current module although these | |
2534 | subforms are at the top-level as well. | |
2535 | ||
311b6a3c | 2536 | To prevent strange behavior, the forms `define-module', |
6f76852b MV |
2537 | `use-modules', `use-syntax', and `export' have been restricted to only |
2538 | work on the top level. The forms `define-public' and | |
2539 | `defmacro-public' only export the new binding on the top level. They | |
2540 | behave just like `define' and `defmacro', respectively, when they are | |
2541 | used in a lexical environment. | |
2542 | ||
0a892a2c MV |
2543 | Also, `export' will no longer silently re-export bindings imported |
2544 | from a used module. It will emit a `deprecation' warning and will | |
2545 | cease to perform any re-export in the next version. If you actually | |
2546 | want to re-export bindings, use the new `re-export' in place of | |
2547 | `export'. The new `re-export' will not make copies of variables when | |
2548 | rexporting them, as `export' did wrongly. | |
2549 | ||
047dc3ae TTN |
2550 | ** Module system now allows selection and renaming of imported bindings |
2551 | ||
2552 | Previously, when using `use-modules' or the `#:use-module' clause in | |
2553 | the `define-module' form, all the bindings (association of symbols to | |
2554 | values) for imported modules were added to the "current module" on an | |
2555 | as-is basis. This has been changed to allow finer control through two | |
2556 | new facilities: selection and renaming. | |
2557 | ||
2558 | You can now select which of the imported module's bindings are to be | |
2559 | visible in the current module by using the `:select' clause. This | |
2560 | clause also can be used to rename individual bindings. For example: | |
2561 | ||
2562 | ;; import all bindings no questions asked | |
2563 | (use-modules (ice-9 common-list)) | |
2564 | ||
2565 | ;; import four bindings, renaming two of them; | |
2566 | ;; the current module sees: every some zonk-y zonk-n | |
2567 | (use-modules ((ice-9 common-list) | |
2568 | :select (every some | |
2569 | (remove-if . zonk-y) | |
2570 | (remove-if-not . zonk-n)))) | |
2571 | ||
2572 | You can also programmatically rename all selected bindings using the | |
2573 | `:renamer' clause, which specifies a proc that takes a symbol and | |
2574 | returns another symbol. Because it is common practice to use a prefix, | |
2575 | we now provide the convenience procedure `symbol-prefix-proc'. For | |
2576 | example: | |
2577 | ||
2578 | ;; import four bindings, renaming two of them specifically, | |
2579 | ;; and all four w/ prefix "CL:"; | |
2580 | ;; the current module sees: CL:every CL:some CL:zonk-y CL:zonk-n | |
2581 | (use-modules ((ice-9 common-list) | |
2582 | :select (every some | |
2583 | (remove-if . zonk-y) | |
2584 | (remove-if-not . zonk-n)) | |
2585 | :renamer (symbol-prefix-proc 'CL:))) | |
2586 | ||
2587 | ;; import four bindings, renaming two of them specifically, | |
2588 | ;; and all four by upcasing. | |
2589 | ;; the current module sees: EVERY SOME ZONK-Y ZONK-N | |
2590 | (define (upcase-symbol sym) | |
2591 | (string->symbol (string-upcase (symbol->string sym)))) | |
2592 | ||
2593 | (use-modules ((ice-9 common-list) | |
2594 | :select (every some | |
2595 | (remove-if . zonk-y) | |
2596 | (remove-if-not . zonk-n)) | |
2597 | :renamer upcase-symbol)) | |
2598 | ||
2599 | Note that programmatic renaming is done *after* individual renaming. | |
2600 | Also, the above examples show `use-modules', but the same facilities are | |
2601 | available for the `#:use-module' clause of `define-module'. | |
2602 | ||
2603 | See manual for more info. | |
2604 | ||
b7d69200 | 2605 | ** The semantics of guardians have changed. |
56495472 | 2606 | |
b7d69200 | 2607 | The changes are for the most part compatible. An important criterion |
6c0201ad | 2608 | was to keep the typical usage of guardians as simple as before, but to |
c0a5d888 | 2609 | make the semantics safer and (as a result) more useful. |
56495472 | 2610 | |
c0a5d888 | 2611 | *** All objects returned from guardians are now properly alive. |
56495472 | 2612 | |
c0a5d888 ML |
2613 | It is now guaranteed that any object referenced by an object returned |
2614 | from a guardian is alive. It's now impossible for a guardian to | |
2615 | return a "contained" object before its "containing" object. | |
56495472 ML |
2616 | |
2617 | One incompatible (but probably not very important) change resulting | |
2618 | from this is that it is no longer possible to guard objects that | |
2619 | indirectly reference themselves (i.e. are parts of cycles). If you do | |
2620 | so accidentally, you'll get a warning. | |
2621 | ||
c0a5d888 ML |
2622 | *** There are now two types of guardians: greedy and sharing. |
2623 | ||
2624 | If you call (make-guardian #t) or just (make-guardian), you'll get a | |
2625 | greedy guardian, and for (make-guardian #f) a sharing guardian. | |
2626 | ||
2627 | Greedy guardians are the default because they are more "defensive". | |
2628 | You can only greedily guard an object once. If you guard an object | |
2629 | more than once, once in a greedy guardian and the rest of times in | |
2630 | sharing guardians, then it is guaranteed that the object won't be | |
2631 | returned from sharing guardians as long as it is greedily guarded | |
2632 | and/or alive. | |
2633 | ||
2634 | Guardians returned by calls to `make-guardian' can now take one more | |
2635 | optional parameter, which says whether to throw an error in case an | |
2636 | attempt is made to greedily guard an object that is already greedily | |
2637 | guarded. The default is true, i.e. throw an error. If the parameter | |
2638 | is false, the guardian invocation returns #t if guarding was | |
2639 | successful and #f if it wasn't. | |
2640 | ||
2641 | Also, since greedy guarding is, in effect, a side-effecting operation | |
2642 | on objects, a new function is introduced: `destroy-guardian!'. | |
2643 | Invoking this function on a guardian renders it unoperative and, if | |
2644 | the guardian is greedy, clears the "greedily guarded" property of the | |
2645 | objects that were guarded by it, thus undoing the side effect. | |
2646 | ||
2647 | Note that all this hair is hardly very important, since guardian | |
2648 | objects are usually permanent. | |
2649 | ||
311b6a3c MV |
2650 | ** Continuations created by call-with-current-continuation now accept |
2651 | any number of arguments, as required by R5RS. | |
818febc0 | 2652 | |
c10ecc4c | 2653 | ** New function `issue-deprecation-warning' |
56426fdb | 2654 | |
311b6a3c | 2655 | This function is used to display the deprecation messages that are |
c10ecc4c | 2656 | controlled by GUILE_WARN_DEPRECATION as explained in the README. |
56426fdb KN |
2657 | |
2658 | (define (id x) | |
c10ecc4c MV |
2659 | (issue-deprecation-warning "`id' is deprecated. Use `identity' instead.") |
2660 | (identity x)) | |
56426fdb KN |
2661 | |
2662 | guile> (id 1) | |
2663 | ;; `id' is deprecated. Use `identity' instead. | |
2664 | 1 | |
2665 | guile> (id 1) | |
2666 | 1 | |
2667 | ||
c10ecc4c MV |
2668 | ** New syntax `begin-deprecated' |
2669 | ||
2670 | When deprecated features are included (as determined by the configure | |
2671 | option --enable-deprecated), `begin-deprecated' is identical to | |
2672 | `begin'. When deprecated features are excluded, it always evaluates | |
2673 | to `#f', ignoring the body forms. | |
2674 | ||
17f367e0 MV |
2675 | ** New function `make-object-property' |
2676 | ||
2677 | This function returns a new `procedure with setter' P that can be used | |
2678 | to attach a property to objects. When calling P as | |
2679 | ||
2680 | (set! (P obj) val) | |
2681 | ||
2682 | where `obj' is any kind of object, it attaches `val' to `obj' in such | |
2683 | a way that it can be retrieved by calling P as | |
2684 | ||
2685 | (P obj) | |
2686 | ||
2687 | This function will replace procedure properties, symbol properties and | |
2688 | source properties eventually. | |
2689 | ||
76ef92f3 MV |
2690 | ** Module (ice-9 optargs) now uses keywords instead of `#&'. |
2691 | ||
2692 | Instead of #&optional, #&key, etc you should now use #:optional, | |
2693 | #:key, etc. Since #:optional is a keyword, you can write it as just | |
2694 | :optional when (read-set! keywords 'prefix) is active. | |
2695 | ||
2696 | The old reader syntax `#&' is still supported, but deprecated. It | |
2697 | will be removed in the next release. | |
2698 | ||
c0997079 MD |
2699 | ** New define-module option: pure |
2700 | ||
2701 | Tells the module system not to include any bindings from the root | |
2702 | module. | |
2703 | ||
2704 | Example: | |
2705 | ||
2706 | (define-module (totally-empty-module) | |
2707 | :pure) | |
2708 | ||
2709 | ** New define-module option: export NAME1 ... | |
2710 | ||
2711 | Export names NAME1 ... | |
2712 | ||
2713 | This option is required if you want to be able to export bindings from | |
2714 | a module which doesn't import one of `define-public' or `export'. | |
2715 | ||
2716 | Example: | |
2717 | ||
311b6a3c MV |
2718 | (define-module (foo) |
2719 | :pure | |
2720 | :use-module (ice-9 r5rs) | |
2721 | :export (bar)) | |
69b5f65a | 2722 | |
311b6a3c | 2723 | ;;; Note that we're pure R5RS below this point! |
69b5f65a | 2724 | |
311b6a3c MV |
2725 | (define (bar) |
2726 | ...) | |
daa6ba18 | 2727 | |
1f3908c4 KN |
2728 | ** New function: object->string OBJ |
2729 | ||
2730 | Return a Scheme string obtained by printing a given object. | |
2731 | ||
eb5c0a2a GH |
2732 | ** New function: port? X |
2733 | ||
2734 | Returns a boolean indicating whether X is a port. Equivalent to | |
2735 | `(or (input-port? X) (output-port? X))'. | |
2736 | ||
efa40607 DH |
2737 | ** New function: file-port? |
2738 | ||
2739 | Determines whether a given object is a port that is related to a file. | |
2740 | ||
34b56ec4 GH |
2741 | ** New function: port-for-each proc |
2742 | ||
311b6a3c MV |
2743 | Apply PROC to each port in the Guile port table in turn. The return |
2744 | value is unspecified. More specifically, PROC is applied exactly once | |
2745 | to every port that exists in the system at the time PORT-FOR-EACH is | |
2746 | invoked. Changes to the port table while PORT-FOR-EACH is running | |
2747 | have no effect as far as PORT-FOR-EACH is concerned. | |
34b56ec4 GH |
2748 | |
2749 | ** New function: dup2 oldfd newfd | |
2750 | ||
2751 | A simple wrapper for the `dup2' system call. Copies the file | |
2752 | descriptor OLDFD to descriptor number NEWFD, replacing the | |
2753 | previous meaning of NEWFD. Both OLDFD and NEWFD must be integers. | |
2754 | Unlike for dup->fdes or primitive-move->fdes, no attempt is made | |
264e9cbc | 2755 | to move away ports which are using NEWFD. The return value is |
34b56ec4 GH |
2756 | unspecified. |
2757 | ||
2758 | ** New function: close-fdes fd | |
2759 | ||
2760 | A simple wrapper for the `close' system call. Close file | |
2761 | descriptor FD, which must be an integer. Unlike close (*note | |
2762 | close: Ports and File Descriptors.), the file descriptor will be | |
2763 | closed even if a port is using it. The return value is | |
2764 | unspecified. | |
2765 | ||
94e6d793 MG |
2766 | ** New function: crypt password salt |
2767 | ||
2768 | Encrypts `password' using the standard unix password encryption | |
2769 | algorithm. | |
2770 | ||
2771 | ** New function: chroot path | |
2772 | ||
2773 | Change the root directory of the running process to `path'. | |
2774 | ||
2775 | ** New functions: getlogin, cuserid | |
2776 | ||
2777 | Return the login name or the user name of the current effective user | |
2778 | id, respectively. | |
2779 | ||
2780 | ** New functions: getpriority which who, setpriority which who prio | |
2781 | ||
2782 | Get or set the priority of the running process. | |
2783 | ||
2784 | ** New function: getpass prompt | |
2785 | ||
2786 | Read a password from the terminal, first displaying `prompt' and | |
2787 | disabling echoing. | |
2788 | ||
2789 | ** New function: flock file operation | |
2790 | ||
2791 | Set/remove an advisory shared or exclusive lock on `file'. | |
2792 | ||
2793 | ** New functions: sethostname name, gethostname | |
2794 | ||
2795 | Set or get the hostname of the machine the current process is running | |
2796 | on. | |
2797 | ||
6d163216 | 2798 | ** New function: mkstemp! tmpl |
4f60cc33 | 2799 | |
6d163216 GH |
2800 | mkstemp creates a new unique file in the file system and returns a |
2801 | new buffered port open for reading and writing to the file. TMPL | |
2802 | is a string specifying where the file should be created: it must | |
2803 | end with `XXXXXX' and will be changed in place to return the name | |
2804 | of the temporary file. | |
2805 | ||
62e63ba9 MG |
2806 | ** New function: open-input-string string |
2807 | ||
2808 | Return an input string port which delivers the characters from | |
4f60cc33 | 2809 | `string'. This procedure, together with `open-output-string' and |
62e63ba9 MG |
2810 | `get-output-string' implements SRFI-6. |
2811 | ||
2812 | ** New function: open-output-string | |
2813 | ||
2814 | Return an output string port which collects all data written to it. | |
2815 | The data can then be retrieved by `get-output-string'. | |
2816 | ||
2817 | ** New function: get-output-string | |
2818 | ||
2819 | Return the contents of an output string port. | |
2820 | ||
56426fdb KN |
2821 | ** New function: identity |
2822 | ||
2823 | Return the argument. | |
2824 | ||
5bef627d GH |
2825 | ** socket, connect, accept etc., now have support for IPv6. IPv6 addresses |
2826 | are represented in Scheme as integers with normal host byte ordering. | |
2827 | ||
2828 | ** New function: inet-pton family address | |
2829 | ||
311b6a3c MV |
2830 | Convert a printable string network address into an integer. Note that |
2831 | unlike the C version of this function, the result is an integer with | |
2832 | normal host byte ordering. FAMILY can be `AF_INET' or `AF_INET6'. | |
2833 | e.g., | |
2834 | ||
2835 | (inet-pton AF_INET "127.0.0.1") => 2130706433 | |
2836 | (inet-pton AF_INET6 "::1") => 1 | |
5bef627d GH |
2837 | |
2838 | ** New function: inet-ntop family address | |
2839 | ||
311b6a3c MV |
2840 | Convert an integer network address into a printable string. Note that |
2841 | unlike the C version of this function, the input is an integer with | |
2842 | normal host byte ordering. FAMILY can be `AF_INET' or `AF_INET6'. | |
2843 | e.g., | |
2844 | ||
2845 | (inet-ntop AF_INET 2130706433) => "127.0.0.1" | |
2846 | (inet-ntop AF_INET6 (- (expt 2 128) 1)) => | |
5bef627d GH |
2847 | ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff |
2848 | ||
56426fdb KN |
2849 | ** Deprecated: id |
2850 | ||
2851 | Use `identity' instead. | |
2852 | ||
5cd06d5e DH |
2853 | ** Deprecated: -1+ |
2854 | ||
2855 | Use `1-' instead. | |
2856 | ||
2857 | ** Deprecated: return-it | |
2858 | ||
311b6a3c | 2859 | Do without it. |
5cd06d5e DH |
2860 | |
2861 | ** Deprecated: string-character-length | |
2862 | ||
2863 | Use `string-length' instead. | |
2864 | ||
2865 | ** Deprecated: flags | |
2866 | ||
2867 | Use `logior' instead. | |
2868 | ||
4f60cc33 NJ |
2869 | ** Deprecated: close-all-ports-except. |
2870 | ||
2871 | This was intended for closing ports in a child process after a fork, | |
2872 | but it has the undesirable side effect of flushing buffers. | |
2873 | port-for-each is more flexible. | |
34b56ec4 GH |
2874 | |
2875 | ** The (ice-9 popen) module now attempts to set up file descriptors in | |
2876 | the child process from the current Scheme ports, instead of using the | |
2877 | current values of file descriptors 0, 1, and 2 in the parent process. | |
2878 | ||
b52e071b DH |
2879 | ** Removed function: builtin-weak-bindings |
2880 | ||
2881 | There is no such concept as a weak binding any more. | |
2882 | ||
9d774814 | 2883 | ** Removed constants: bignum-radix, scm-line-incrementors |
0f979f3f | 2884 | |
7d435120 MD |
2885 | ** define-method: New syntax mandatory. |
2886 | ||
2887 | The new method syntax is now mandatory: | |
2888 | ||
2889 | (define-method (NAME ARG-SPEC ...) BODY ...) | |
2890 | (define-method (NAME ARG-SPEC ... . REST-ARG) BODY ...) | |
2891 | ||
2892 | ARG-SPEC ::= ARG-NAME | (ARG-NAME TYPE) | |
2893 | REST-ARG ::= ARG-NAME | |
2894 | ||
2895 | If you have old code using the old syntax, import | |
2896 | (oop goops old-define-method) before (oop goops) as in: | |
2897 | ||
2898 | (use-modules (oop goops old-define-method) (oop goops)) | |
2899 | ||
f3f9dcbc MV |
2900 | ** Deprecated function: builtin-variable |
2901 | Removed function: builtin-bindings | |
2902 | ||
2903 | There is no longer a distinction between builtin or other variables. | |
2904 | Use module system operations for all variables. | |
2905 | ||
311b6a3c MV |
2906 | ** Lazy-catch handlers are no longer allowed to return. |
2907 | ||
2908 | That is, a call to `throw', `error', etc is now guaranteed to not | |
2909 | return. | |
2910 | ||
a583bf1e | 2911 | ** Bugfixes for (ice-9 getopt-long) |
8c84b81e | 2912 | |
a583bf1e TTN |
2913 | This module is now tested using test-suite/tests/getopt-long.test. |
2914 | The following bugs have been fixed: | |
2915 | ||
2916 | *** Parsing for options that are specified to have `optional' args now checks | |
2917 | if the next element is an option instead of unconditionally taking it as the | |
8c84b81e TTN |
2918 | option arg. |
2919 | ||
a583bf1e TTN |
2920 | *** An error is now thrown for `--opt=val' when the option description |
2921 | does not specify `(value #t)' or `(value optional)'. This condition used to | |
2922 | be accepted w/o error, contrary to the documentation. | |
2923 | ||
2924 | *** The error message for unrecognized options is now more informative. | |
2925 | It used to be "not a record", an artifact of the implementation. | |
2926 | ||
2927 | *** The error message for `--opt' terminating the arg list (no value), when | |
2928 | `(value #t)' is specified, is now more informative. It used to be "not enough | |
2929 | args". | |
2930 | ||
2931 | *** "Clumped" single-char args now preserve trailing string, use it as arg. | |
2932 | The expansion used to be like so: | |
2933 | ||
2934 | ("-abc5d" "--xyz") => ("-a" "-b" "-c" "--xyz") | |
2935 | ||
2936 | Note that the "5d" is dropped. Now it is like so: | |
2937 | ||
2938 | ("-abc5d" "--xyz") => ("-a" "-b" "-c" "5d" "--xyz") | |
2939 | ||
2940 | This enables single-char options to have adjoining arguments as long as their | |
2941 | constituent characters are not potential single-char options. | |
8c84b81e | 2942 | |
998bfc70 TTN |
2943 | ** (ice-9 session) procedure `arity' now works with (ice-9 optargs) `lambda*' |
2944 | ||
2945 | The `lambda*' and derivative forms in (ice-9 optargs) now set a procedure | |
2946 | property `arglist', which can be retrieved by `arity'. The result is that | |
2947 | `arity' can give more detailed information than before: | |
2948 | ||
2949 | Before: | |
2950 | ||
2951 | guile> (use-modules (ice-9 optargs)) | |
2952 | guile> (define* (foo #:optional a b c) a) | |
2953 | guile> (arity foo) | |
2954 | 0 or more arguments in `lambda*:G0'. | |
2955 | ||
2956 | After: | |
2957 | ||
2958 | guile> (arity foo) | |
2959 | 3 optional arguments: `a', `b' and `c'. | |
2960 | guile> (define* (bar a b #:key c d #:allow-other-keys) a) | |
2961 | guile> (arity bar) | |
2962 | 2 required arguments: `a' and `b', 2 keyword arguments: `c' | |
2963 | and `d', other keywords allowed. | |
2964 | guile> (define* (baz a b #:optional c #:rest r) a) | |
2965 | guile> (arity baz) | |
2966 | 2 required arguments: `a' and `b', 1 optional argument: `c', | |
2967 | the rest in `r'. | |
2968 | ||
311b6a3c MV |
2969 | * Changes to the C interface |
2970 | ||
c81c130e MV |
2971 | ** Types have been renamed from scm_*_t to scm_t_*. |
2972 | ||
2973 | This has been done for POSIX sake. It reserves identifiers ending | |
2974 | with "_t". What a concept. | |
2975 | ||
2976 | The old names are still available with status `deprecated'. | |
2977 | ||
2978 | ** scm_t_bits (former scm_bits_t) is now a unsigned type. | |
2979 | ||
6e9382f1 | 2980 | ** Deprecated features have been removed. |
e6c9e497 MV |
2981 | |
2982 | *** Macros removed | |
2983 | ||
2984 | SCM_INPORTP, SCM_OUTPORTP SCM_ICHRP, SCM_ICHR, SCM_MAKICHR | |
2985 | SCM_SETJMPBUF SCM_NSTRINGP SCM_NRWSTRINGP SCM_NVECTORP SCM_DOUBLE_CELLP | |
2986 | ||
2987 | *** C Functions removed | |
2988 | ||
2989 | scm_sysmissing scm_tag scm_tc16_flo scm_tc_flo | |
2990 | scm_fseek - replaced by scm_seek. | |
2991 | gc-thunk - replaced by after-gc-hook. | |
2992 | gh_int2scmb - replaced by gh_bool2scm. | |
2993 | scm_tc_dblr - replaced by scm_tc16_real. | |
2994 | scm_tc_dblc - replaced by scm_tc16_complex. | |
2995 | scm_list_star - replaced by scm_cons_star. | |
2996 | ||
36284627 DH |
2997 | ** Deprecated: scm_makfromstr |
2998 | ||
2999 | Use scm_mem2string instead. | |
3000 | ||
311b6a3c MV |
3001 | ** Deprecated: scm_make_shared_substring |
3002 | ||
3003 | Explicit shared substrings will disappear from Guile. | |
3004 | ||
3005 | Instead, "normal" strings will be implemented using sharing | |
3006 | internally, combined with a copy-on-write strategy. | |
3007 | ||
3008 | ** Deprecated: scm_read_only_string_p | |
3009 | ||
3010 | The concept of read-only strings will disappear in next release of | |
3011 | Guile. | |
3012 | ||
3013 | ** Deprecated: scm_sloppy_memq, scm_sloppy_memv, scm_sloppy_member | |
c299f186 | 3014 | |
311b6a3c | 3015 | Instead, use scm_c_memq or scm_memq, scm_memv, scm_member. |
c299f186 | 3016 | |
dd0e04ed KN |
3017 | ** New functions: scm_call_0, scm_call_1, scm_call_2, scm_call_3 |
3018 | ||
83dbedcc KR |
3019 | Call a procedure with the indicated number of arguments. See "Fly |
3020 | Evaluation" in the manual. | |
dd0e04ed KN |
3021 | |
3022 | ** New functions: scm_apply_0, scm_apply_1, scm_apply_2, scm_apply_3 | |
3023 | ||
83dbedcc KR |
3024 | Call a procedure with the indicated number of arguments and a list of |
3025 | further arguments. See "Fly Evaluation" in the manual. | |
dd0e04ed | 3026 | |
e235f2a6 KN |
3027 | ** New functions: scm_list_1, scm_list_2, scm_list_3, scm_list_4, scm_list_5 |
3028 | ||
83dbedcc KR |
3029 | Create a list of the given number of elements. See "List |
3030 | Constructors" in the manual. | |
e235f2a6 KN |
3031 | |
3032 | ** Renamed function: scm_listify has been replaced by scm_list_n. | |
3033 | ||
3034 | ** Deprecated macros: SCM_LIST0, SCM_LIST1, SCM_LIST2, SCM_LIST3, SCM_LIST4, | |
3035 | SCM_LIST5, SCM_LIST6, SCM_LIST7, SCM_LIST8, SCM_LIST9. | |
3036 | ||
3037 | Use functions scm_list_N instead. | |
3038 | ||
6fe692e9 MD |
3039 | ** New function: scm_c_read (SCM port, void *buffer, scm_sizet size) |
3040 | ||
3041 | Used by an application to read arbitrary number of bytes from a port. | |
3042 | Same semantics as libc read, except that scm_c_read only returns less | |
3043 | than SIZE bytes if at end-of-file. | |
3044 | ||
3045 | Warning: Doesn't update port line and column counts! | |
3046 | ||
3047 | ** New function: scm_c_write (SCM port, const void *ptr, scm_sizet size) | |
3048 | ||
3049 | Used by an application to write arbitrary number of bytes to an SCM | |
3050 | port. Similar semantics as libc write. However, unlike libc | |
3051 | write, scm_c_write writes the requested number of bytes and has no | |
3052 | return value. | |
3053 | ||
3054 | Warning: Doesn't update port line and column counts! | |
3055 | ||
17f367e0 MV |
3056 | ** New function: scm_init_guile () |
3057 | ||
3058 | In contrast to scm_boot_guile, scm_init_guile will return normally | |
3059 | after initializing Guile. It is not available on all systems, tho. | |
3060 | ||
23ade5e7 DH |
3061 | ** New functions: scm_str2symbol, scm_mem2symbol |
3062 | ||
3063 | The function scm_str2symbol takes a const char* pointing to a zero-terminated | |
3064 | field of characters and creates a scheme symbol object from that C string. | |
3065 | The function scm_mem2symbol takes a const char* and a number of characters and | |
3066 | creates a symbol from the characters in that memory area. | |
3067 | ||
17f367e0 MV |
3068 | ** New functions: scm_primitive_make_property |
3069 | scm_primitive_property_ref | |
3070 | scm_primitive_property_set_x | |
3071 | scm_primitive_property_del_x | |
3072 | ||
3073 | These functions implement a new way to deal with object properties. | |
3074 | See libguile/properties.c for their documentation. | |
3075 | ||
9d47a1e6 ML |
3076 | ** New function: scm_done_free (long size) |
3077 | ||
3078 | This function is the inverse of scm_done_malloc. Use it to report the | |
3079 | amount of smob memory you free. The previous method, which involved | |
3080 | calling scm_done_malloc with negative argument, was somewhat | |
3081 | unintuitive (and is still available, of course). | |
3082 | ||
79a3dafe DH |
3083 | ** New function: scm_c_memq (SCM obj, SCM list) |
3084 | ||
3085 | This function provides a fast C level alternative for scm_memq for the case | |
3086 | that the list parameter is known to be a proper list. The function is a | |
3087 | replacement for scm_sloppy_memq, but is stricter in its requirements on its | |
3088 | list input parameter, since for anything else but a proper list the function's | |
3089 | behaviour is undefined - it may even crash or loop endlessly. Further, for | |
3090 | the case that the object is not found in the list, scm_c_memq returns #f which | |
3091 | is similar to scm_memq, but different from scm_sloppy_memq's behaviour. | |
3092 | ||
6c0201ad | 3093 | ** New functions: scm_remember_upto_here_1, scm_remember_upto_here_2, |
5d2b97cd DH |
3094 | scm_remember_upto_here |
3095 | ||
3096 | These functions replace the function scm_remember. | |
3097 | ||
3098 | ** Deprecated function: scm_remember | |
3099 | ||
3100 | Use one of the new functions scm_remember_upto_here_1, | |
3101 | scm_remember_upto_here_2 or scm_remember_upto_here instead. | |
3102 | ||
be54b15d DH |
3103 | ** New function: scm_allocate_string |
3104 | ||
3105 | This function replaces the function scm_makstr. | |
3106 | ||
3107 | ** Deprecated function: scm_makstr | |
3108 | ||
3109 | Use the new function scm_allocate_string instead. | |
3110 | ||
32d0d4b1 DH |
3111 | ** New global variable scm_gc_running_p introduced. |
3112 | ||
3113 | Use this variable to find out if garbage collection is being executed. Up to | |
3114 | now applications have used scm_gc_heap_lock to test if garbage collection was | |
3115 | running, which also works because of the fact that up to know only the garbage | |
3116 | collector has set this variable. But, this is an implementation detail that | |
3117 | may change. Further, scm_gc_heap_lock is not set throughout gc, thus the use | |
3118 | of this variable is (and has been) not fully safe anyway. | |
3119 | ||
5b9eb8ae DH |
3120 | ** New macros: SCM_BITVECTOR_MAX_LENGTH, SCM_UVECTOR_MAX_LENGTH |
3121 | ||
3122 | Use these instead of SCM_LENGTH_MAX. | |
3123 | ||
6c0201ad | 3124 | ** New macros: SCM_CONTINUATION_LENGTH, SCM_CCLO_LENGTH, SCM_STACK_LENGTH, |
a6d9e5ab DH |
3125 | SCM_STRING_LENGTH, SCM_SYMBOL_LENGTH, SCM_UVECTOR_LENGTH, |
3126 | SCM_BITVECTOR_LENGTH, SCM_VECTOR_LENGTH. | |
3127 | ||
3128 | Use these instead of SCM_LENGTH. | |
3129 | ||
6c0201ad | 3130 | ** New macros: SCM_SET_CONTINUATION_LENGTH, SCM_SET_STRING_LENGTH, |
93778877 DH |
3131 | SCM_SET_SYMBOL_LENGTH, SCM_SET_VECTOR_LENGTH, SCM_SET_UVECTOR_LENGTH, |
3132 | SCM_SET_BITVECTOR_LENGTH | |
bc0eaf7b DH |
3133 | |
3134 | Use these instead of SCM_SETLENGTH | |
3135 | ||
6c0201ad | 3136 | ** New macros: SCM_STRING_CHARS, SCM_SYMBOL_CHARS, SCM_CCLO_BASE, |
a6d9e5ab DH |
3137 | SCM_VECTOR_BASE, SCM_UVECTOR_BASE, SCM_BITVECTOR_BASE, SCM_COMPLEX_MEM, |
3138 | SCM_ARRAY_MEM | |
3139 | ||
e51fe79c DH |
3140 | Use these instead of SCM_CHARS, SCM_UCHARS, SCM_ROCHARS, SCM_ROUCHARS or |
3141 | SCM_VELTS. | |
a6d9e5ab | 3142 | |
6c0201ad | 3143 | ** New macros: SCM_SET_BIGNUM_BASE, SCM_SET_STRING_CHARS, |
6a0476fd DH |
3144 | SCM_SET_SYMBOL_CHARS, SCM_SET_UVECTOR_BASE, SCM_SET_BITVECTOR_BASE, |
3145 | SCM_SET_VECTOR_BASE | |
3146 | ||
3147 | Use these instead of SCM_SETCHARS. | |
3148 | ||
a6d9e5ab DH |
3149 | ** New macro: SCM_BITVECTOR_P |
3150 | ||
3151 | ** New macro: SCM_STRING_COERCE_0TERMINATION_X | |
3152 | ||
3153 | Use instead of SCM_COERCE_SUBSTR. | |
3154 | ||
30ea841d DH |
3155 | ** New macros: SCM_DIR_OPEN_P, SCM_DIR_FLAG_OPEN |
3156 | ||
3157 | For directory objects, use these instead of SCM_OPDIRP and SCM_OPN. | |
3158 | ||
6c0201ad TTN |
3159 | ** Deprecated macros: SCM_OUTOFRANGE, SCM_NALLOC, SCM_HUP_SIGNAL, |
3160 | SCM_INT_SIGNAL, SCM_FPE_SIGNAL, SCM_BUS_SIGNAL, SCM_SEGV_SIGNAL, | |
3161 | SCM_ALRM_SIGNAL, SCM_GC_SIGNAL, SCM_TICK_SIGNAL, SCM_SIG_ORD, | |
d1ca2c64 | 3162 | SCM_ORD_SIG, SCM_NUM_SIGS, SCM_SYMBOL_SLOTS, SCM_SLOTS, SCM_SLOPPY_STRINGP, |
a6d9e5ab DH |
3163 | SCM_VALIDATE_STRINGORSUBSTR, SCM_FREEP, SCM_NFREEP, SCM_CHARS, SCM_UCHARS, |
3164 | SCM_VALIDATE_ROSTRING, SCM_VALIDATE_ROSTRING_COPY, | |
3165 | SCM_VALIDATE_NULLORROSTRING_COPY, SCM_ROLENGTH, SCM_LENGTH, SCM_HUGE_LENGTH, | |
b24b5e13 | 3166 | SCM_SUBSTRP, SCM_SUBSTR_STR, SCM_SUBSTR_OFFSET, SCM_COERCE_SUBSTR, |
34f0f2b8 | 3167 | SCM_ROSTRINGP, SCM_RWSTRINGP, SCM_VALIDATE_RWSTRING, SCM_ROCHARS, |
fd336365 | 3168 | SCM_ROUCHARS, SCM_SETLENGTH, SCM_SETCHARS, SCM_LENGTH_MAX, SCM_GC8MARKP, |
30ea841d | 3169 | SCM_SETGC8MARK, SCM_CLRGC8MARK, SCM_GCTYP16, SCM_GCCDR, SCM_SUBR_DOC, |
b3fcac34 DH |
3170 | SCM_OPDIRP, SCM_VALIDATE_OPDIR, SCM_WTA, RETURN_SCM_WTA, SCM_CONST_LONG, |
3171 | SCM_WNA, SCM_FUNC_NAME, SCM_VALIDATE_NUMBER_COPY, | |
61045190 | 3172 | SCM_VALIDATE_NUMBER_DEF_COPY, SCM_SLOPPY_CONSP, SCM_SLOPPY_NCONSP, |
e038c042 | 3173 | SCM_SETAND_CDR, SCM_SETOR_CDR, SCM_SETAND_CAR, SCM_SETOR_CAR |
b63a956d DH |
3174 | |
3175 | Use SCM_ASSERT_RANGE or SCM_VALIDATE_XXX_RANGE instead of SCM_OUTOFRANGE. | |
3176 | Use scm_memory_error instead of SCM_NALLOC. | |
c1aef037 | 3177 | Use SCM_STRINGP instead of SCM_SLOPPY_STRINGP. |
d1ca2c64 DH |
3178 | Use SCM_VALIDATE_STRING instead of SCM_VALIDATE_STRINGORSUBSTR. |
3179 | Use SCM_FREE_CELL_P instead of SCM_FREEP/SCM_NFREEP | |
a6d9e5ab | 3180 | Use a type specific accessor macro instead of SCM_CHARS/SCM_UCHARS. |
6c0201ad | 3181 | Use a type specific accessor instead of SCM(_|_RO|_HUGE_)LENGTH. |
a6d9e5ab DH |
3182 | Use SCM_VALIDATE_(SYMBOL|STRING) instead of SCM_VALIDATE_ROSTRING. |
3183 | Use SCM_STRING_COERCE_0TERMINATION_X instead of SCM_COERCE_SUBSTR. | |
b24b5e13 | 3184 | Use SCM_STRINGP or SCM_SYMBOLP instead of SCM_ROSTRINGP. |
f0942910 DH |
3185 | Use SCM_STRINGP instead of SCM_RWSTRINGP. |
3186 | Use SCM_VALIDATE_STRING instead of SCM_VALIDATE_RWSTRING. | |
34f0f2b8 DH |
3187 | Use SCM_STRING_CHARS instead of SCM_ROCHARS. |
3188 | Use SCM_STRING_UCHARS instead of SCM_ROUCHARS. | |
93778877 | 3189 | Use a type specific setter macro instead of SCM_SETLENGTH. |
6a0476fd | 3190 | Use a type specific setter macro instead of SCM_SETCHARS. |
5b9eb8ae | 3191 | Use a type specific length macro instead of SCM_LENGTH_MAX. |
fd336365 DH |
3192 | Use SCM_GCMARKP instead of SCM_GC8MARKP. |
3193 | Use SCM_SETGCMARK instead of SCM_SETGC8MARK. | |
3194 | Use SCM_CLRGCMARK instead of SCM_CLRGC8MARK. | |
3195 | Use SCM_TYP16 instead of SCM_GCTYP16. | |
3196 | Use SCM_CDR instead of SCM_GCCDR. | |
30ea841d | 3197 | Use SCM_DIR_OPEN_P instead of SCM_OPDIRP. |
276dd677 DH |
3198 | Use SCM_MISC_ERROR or SCM_WRONG_TYPE_ARG instead of SCM_WTA. |
3199 | Use SCM_MISC_ERROR or SCM_WRONG_TYPE_ARG instead of RETURN_SCM_WTA. | |
8dea8611 | 3200 | Use SCM_VCELL_INIT instead of SCM_CONST_LONG. |
b3fcac34 | 3201 | Use SCM_WRONG_NUM_ARGS instead of SCM_WNA. |
ced99e92 DH |
3202 | Use SCM_CONSP instead of SCM_SLOPPY_CONSP. |
3203 | Use !SCM_CONSP instead of SCM_SLOPPY_NCONSP. | |
b63a956d | 3204 | |
f7620510 DH |
3205 | ** Removed function: scm_struct_init |
3206 | ||
93d40df2 DH |
3207 | ** Removed variable: scm_symhash_dim |
3208 | ||
818febc0 GH |
3209 | ** Renamed function: scm_make_cont has been replaced by |
3210 | scm_make_continuation, which has a different interface. | |
3211 | ||
cc4feeca DH |
3212 | ** Deprecated function: scm_call_catching_errors |
3213 | ||
3214 | Use scm_catch or scm_lazy_catch from throw.[ch] instead. | |
3215 | ||
28b06554 DH |
3216 | ** Deprecated function: scm_strhash |
3217 | ||
3218 | Use scm_string_hash instead. | |
3219 | ||
1b9be268 DH |
3220 | ** Deprecated function: scm_vector_set_length_x |
3221 | ||
3222 | Instead, create a fresh vector of the desired size and copy the contents. | |
3223 | ||
302f229e MD |
3224 | ** scm_gensym has changed prototype |
3225 | ||
3226 | scm_gensym now only takes one argument. | |
3227 | ||
1660782e DH |
3228 | ** Deprecated type tags: scm_tc7_ssymbol, scm_tc7_msymbol, scm_tcs_symbols, |
3229 | scm_tc7_lvector | |
28b06554 DH |
3230 | |
3231 | There is now only a single symbol type scm_tc7_symbol. | |
1660782e | 3232 | The tag scm_tc7_lvector was not used anyway. |
28b06554 | 3233 | |
2f6fb7c5 KN |
3234 | ** Deprecated function: scm_make_smob_type_mfpe, scm_set_smob_mfpe. |
3235 | ||
3236 | Use scm_make_smob_type and scm_set_smob_XXX instead. | |
3237 | ||
3238 | ** New function scm_set_smob_apply. | |
3239 | ||
3240 | This can be used to set an apply function to a smob type. | |
3241 | ||
1f3908c4 KN |
3242 | ** Deprecated function: scm_strprint_obj |
3243 | ||
3244 | Use scm_object_to_string instead. | |
3245 | ||
b3fcac34 DH |
3246 | ** Deprecated function: scm_wta |
3247 | ||
3248 | Use scm_wrong_type_arg, or another appropriate error signalling function | |
3249 | instead. | |
3250 | ||
f3f9dcbc MV |
3251 | ** Explicit support for obarrays has been deprecated. |
3252 | ||
3253 | Use `scm_str2symbol' and the generic hashtable functions instead. | |
3254 | ||
3255 | ** The concept of `vcells' has been deprecated. | |
3256 | ||
3257 | The data type `variable' is now used exclusively. `Vcells' have been | |
3258 | a low-level concept so you are likely not affected by this change. | |
3259 | ||
3260 | *** Deprecated functions: scm_sym2vcell, scm_sysintern, | |
3261 | scm_sysintern0, scm_symbol_value0, scm_intern, scm_intern0. | |
3262 | ||
3263 | Use scm_c_define or scm_c_lookup instead, as appropriate. | |
3264 | ||
3265 | *** New functions: scm_c_module_lookup, scm_c_lookup, | |
3266 | scm_c_module_define, scm_c_define, scm_module_lookup, scm_lookup, | |
3267 | scm_module_define, scm_define. | |
3268 | ||
3269 | These functions work with variables instead of with vcells. | |
3270 | ||
311b6a3c MV |
3271 | ** New functions for creating and defining `subr's and `gsubr's. |
3272 | ||
3273 | The new functions more clearly distinguish between creating a subr (or | |
3274 | gsubr) object and adding it to the current module. | |
3275 | ||
3276 | These new functions are available: scm_c_make_subr, scm_c_define_subr, | |
3277 | scm_c_make_subr_with_generic, scm_c_define_subr_with_generic, | |
3278 | scm_c_make_gsubr, scm_c_define_gsubr, scm_c_make_gsubr_with_generic, | |
3279 | scm_c_define_gsubr_with_generic. | |
3280 | ||
3281 | ** Deprecated functions: scm_make_subr, scm_make_subr_opt, | |
3282 | scm_make_subr_with_generic, scm_make_gsubr, | |
3283 | scm_make_gsubr_with_generic. | |
3284 | ||
3285 | Use the new ones from above instead. | |
3286 | ||
3287 | ** C interface to the module system has changed. | |
3288 | ||
3289 | While we suggest that you avoid as many explicit module system | |
3290 | operations from C as possible for the time being, the C interface has | |
3291 | been made more similar to the high-level Scheme module system. | |
3292 | ||
3293 | *** New functions: scm_c_define_module, scm_c_use_module, | |
3294 | scm_c_export, scm_c_resolve_module. | |
3295 | ||
3296 | They mostly work like their Scheme namesakes. scm_c_define_module | |
3297 | takes a function that is called a context where the new module is | |
3298 | current. | |
3299 | ||
3300 | *** Deprecated functions: scm_the_root_module, scm_make_module, | |
3301 | scm_ensure_user_module, scm_load_scheme_module. | |
3302 | ||
3303 | Use the new functions instead. | |
3304 | ||
3305 | ** Renamed function: scm_internal_with_fluids becomes | |
3306 | scm_c_with_fluids. | |
3307 | ||
3308 | scm_internal_with_fluids is available as a deprecated function. | |
3309 | ||
3310 | ** New function: scm_c_with_fluid. | |
3311 | ||
3312 | Just like scm_c_with_fluids, but takes one fluid and one value instead | |
3313 | of lists of same. | |
3314 | ||
1be6b49c ML |
3315 | ** Deprecated typedefs: long_long, ulong_long. |
3316 | ||
3317 | They are of questionable utility and they pollute the global | |
3318 | namespace. | |
3319 | ||
1be6b49c ML |
3320 | ** Deprecated typedef: scm_sizet |
3321 | ||
3322 | It is of questionable utility now that Guile requires ANSI C, and is | |
3323 | oddly named. | |
3324 | ||
3325 | ** Deprecated typedefs: scm_port_rw_active, scm_port, | |
3326 | scm_ptob_descriptor, scm_debug_info, scm_debug_frame, scm_fport, | |
3327 | scm_option, scm_rstate, scm_rng, scm_array, scm_array_dim. | |
3328 | ||
3329 | Made more compliant with the naming policy by adding a _t at the end. | |
3330 | ||
3331 | ** Deprecated functions: scm_mkbig, scm_big2num, scm_adjbig, | |
3332 | scm_normbig, scm_copybig, scm_2ulong2big, scm_dbl2big, scm_big2dbl | |
3333 | ||
373f4948 | 3334 | With the exception of the mysterious scm_2ulong2big, they are still |
1be6b49c ML |
3335 | available under new names (scm_i_mkbig etc). These functions are not |
3336 | intended to be used in user code. You should avoid dealing with | |
3337 | bignums directly, and should deal with numbers in general (which can | |
3338 | be bignums). | |
3339 | ||
147c18a0 MD |
3340 | ** Change in behavior: scm_num2long, scm_num2ulong |
3341 | ||
3342 | The scm_num2[u]long functions don't any longer accept an inexact | |
3343 | argument. This change in behavior is motivated by concordance with | |
3344 | R5RS: It is more common that a primitive doesn't want to accept an | |
3345 | inexact for an exact. | |
3346 | ||
1be6b49c | 3347 | ** New functions: scm_short2num, scm_ushort2num, scm_int2num, |
f3f70257 ML |
3348 | scm_uint2num, scm_size2num, scm_ptrdiff2num, scm_num2short, |
3349 | scm_num2ushort, scm_num2int, scm_num2uint, scm_num2ptrdiff, | |
1be6b49c ML |
3350 | scm_num2size. |
3351 | ||
3352 | These are conversion functions between the various ANSI C integral | |
147c18a0 MD |
3353 | types and Scheme numbers. NOTE: The scm_num2xxx functions don't |
3354 | accept an inexact argument. | |
1be6b49c | 3355 | |
5437598b MD |
3356 | ** New functions: scm_float2num, scm_double2num, |
3357 | scm_num2float, scm_num2double. | |
3358 | ||
3359 | These are conversion functions between the two ANSI C float types and | |
3360 | Scheme numbers. | |
3361 | ||
1be6b49c | 3362 | ** New number validation macros: |
f3f70257 | 3363 | SCM_NUM2{SIZE,PTRDIFF,SHORT,USHORT,INT,UINT}[_DEF] |
1be6b49c ML |
3364 | |
3365 | See above. | |
3366 | ||
fc62c86a ML |
3367 | ** New functions: scm_gc_protect_object, scm_gc_unprotect_object |
3368 | ||
3369 | These are just nicer-named old scm_protect_object and | |
3370 | scm_unprotect_object. | |
3371 | ||
3372 | ** Deprecated functions: scm_protect_object, scm_unprotect_object | |
3373 | ||
3374 | ** New functions: scm_gc_[un]register_root, scm_gc_[un]register_roots | |
3375 | ||
3376 | These functions can be used to register pointers to locations that | |
3377 | hold SCM values. | |
3378 | ||
5b2ad23b ML |
3379 | ** Deprecated function: scm_create_hook. |
3380 | ||
3381 | Its sins are: misleading name, non-modularity and lack of general | |
3382 | usefulness. | |
3383 | ||
c299f186 | 3384 | \f |
cc36e791 JB |
3385 | Changes since Guile 1.3.4: |
3386 | ||
80f27102 JB |
3387 | * Changes to the distribution |
3388 | ||
ce358662 JB |
3389 | ** Trees from nightly snapshots and CVS now require you to run autogen.sh. |
3390 | ||
3391 | We've changed the way we handle generated files in the Guile source | |
3392 | repository. As a result, the procedure for building trees obtained | |
3393 | from the nightly FTP snapshots or via CVS has changed: | |
3394 | - You must have appropriate versions of autoconf, automake, and | |
3395 | libtool installed on your system. See README for info on how to | |
3396 | obtain these programs. | |
3397 | - Before configuring the tree, you must first run the script | |
3398 | `autogen.sh' at the top of the source tree. | |
3399 | ||
3400 | The Guile repository used to contain not only source files, written by | |
3401 | humans, but also some generated files, like configure scripts and | |
3402 | Makefile.in files. Even though the contents of these files could be | |
3403 | derived mechanically from other files present, we thought it would | |
3404 | make the tree easier to build if we checked them into CVS. | |
3405 | ||
3406 | However, this approach means that minor differences between | |
3407 | developer's installed tools and habits affected the whole team. | |
3408 | So we have removed the generated files from the repository, and | |
3409 | added the autogen.sh script, which will reconstruct them | |
3410 | appropriately. | |
3411 | ||
3412 | ||
dc914156 GH |
3413 | ** configure now has experimental options to remove support for certain |
3414 | features: | |
52cfc69b | 3415 | |
dc914156 GH |
3416 | --disable-arrays omit array and uniform array support |
3417 | --disable-posix omit posix interfaces | |
3418 | --disable-networking omit networking interfaces | |
3419 | --disable-regex omit regular expression interfaces | |
52cfc69b GH |
3420 | |
3421 | These are likely to become separate modules some day. | |
3422 | ||
9764c29b | 3423 | ** New configure option --enable-debug-freelist |
e1b0d0ac | 3424 | |
38a15cfd GB |
3425 | This enables a debugging version of SCM_NEWCELL(), and also registers |
3426 | an extra primitive, the setter `gc-set-debug-check-freelist!'. | |
3427 | ||
3428 | Configure with the --enable-debug-freelist option to enable | |
3429 | the gc-set-debug-check-freelist! primitive, and then use: | |
3430 | ||
3431 | (gc-set-debug-check-freelist! #t) # turn on checking of the freelist | |
3432 | (gc-set-debug-check-freelist! #f) # turn off checking | |
3433 | ||
3434 | Checking of the freelist forces a traversal of the freelist and | |
3435 | a garbage collection before each allocation of a cell. This can | |
3436 | slow down the interpreter dramatically, so the setter should be used to | |
3437 | turn on this extra processing only when necessary. | |
e1b0d0ac | 3438 | |
9764c29b MD |
3439 | ** New configure option --enable-debug-malloc |
3440 | ||
3441 | Include code for debugging of calls to scm_must_malloc/realloc/free. | |
3442 | ||
3443 | Checks that | |
3444 | ||
3445 | 1. objects freed by scm_must_free has been mallocated by scm_must_malloc | |
3446 | 2. objects reallocated by scm_must_realloc has been allocated by | |
3447 | scm_must_malloc | |
3448 | 3. reallocated objects are reallocated with the same what string | |
3449 | ||
3450 | But, most importantly, it records the number of allocated objects of | |
3451 | each kind. This is useful when searching for memory leaks. | |
3452 | ||
3453 | A Guile compiled with this option provides the primitive | |
3454 | `malloc-stats' which returns an alist with pairs of kind and the | |
3455 | number of objects of that kind. | |
3456 | ||
e415cb06 MD |
3457 | ** All includes are now referenced relative to the root directory |
3458 | ||
3459 | Since some users have had problems with mixups between Guile and | |
3460 | system headers, we have decided to always refer to Guile headers via | |
3461 | their parent directories. This essentially creates a "private name | |
3462 | space" for Guile headers. This means that the compiler only is given | |
3463 | -I options for the root build and root source directory. | |
3464 | ||
341f78c9 MD |
3465 | ** Header files kw.h and genio.h have been removed. |
3466 | ||
3467 | ** The module (ice-9 getopt-gnu-style) has been removed. | |
3468 | ||
e8855f8d MD |
3469 | ** New module (ice-9 documentation) |
3470 | ||
3471 | Implements the interface to documentation strings associated with | |
3472 | objects. | |
3473 | ||
0c0ffe09 KN |
3474 | ** New module (ice-9 time) |
3475 | ||
3476 | Provides a macro `time', which displays execution time of a given form. | |
3477 | ||
cf7a5ee5 KN |
3478 | ** New module (ice-9 history) |
3479 | ||
3480 | Loading this module enables value history in the repl. | |
3481 | ||
0af43c4a | 3482 | * Changes to the stand-alone interpreter |
bd9e24b3 | 3483 | |
67ef2dca MD |
3484 | ** New command line option --debug |
3485 | ||
3486 | Start Guile with debugging evaluator and backtraces enabled. | |
3487 | ||
3488 | This is useful when debugging your .guile init file or scripts. | |
3489 | ||
aa4bb95d MD |
3490 | ** New help facility |
3491 | ||
341f78c9 MD |
3492 | Usage: (help NAME) gives documentation about objects named NAME (a symbol) |
3493 | (help REGEXP) ditto for objects with names matching REGEXP (a string) | |
58e5b910 | 3494 | (help 'NAME) gives documentation for NAME, even if it is not an object |
341f78c9 | 3495 | (help ,EXPR) gives documentation for object returned by EXPR |
6c0201ad | 3496 | (help (my module)) gives module commentary for `(my module)' |
341f78c9 MD |
3497 | (help) gives this text |
3498 | ||
3499 | `help' searches among bindings exported from loaded modules, while | |
3500 | `apropos' searches among bindings visible from the "current" module. | |
3501 | ||
3502 | Examples: (help help) | |
3503 | (help cons) | |
3504 | (help "output-string") | |
aa4bb95d | 3505 | |
e8855f8d MD |
3506 | ** `help' and `apropos' now prints full module names |
3507 | ||
0af43c4a | 3508 | ** Dynamic linking now uses libltdl from the libtool package. |
bd9e24b3 | 3509 | |
0af43c4a MD |
3510 | The old system dependent code for doing dynamic linking has been |
3511 | replaced with calls to the libltdl functions which do all the hairy | |
3512 | details for us. | |
bd9e24b3 | 3513 | |
0af43c4a MD |
3514 | The major improvement is that you can now directly pass libtool |
3515 | library names like "libfoo.la" to `dynamic-link' and `dynamic-link' | |
3516 | will be able to do the best shared library job you can get, via | |
3517 | libltdl. | |
bd9e24b3 | 3518 | |
0af43c4a MD |
3519 | The way dynamic libraries are found has changed and is not really |
3520 | portable across platforms, probably. It is therefore recommended to | |
3521 | use absolute filenames when possible. | |
3522 | ||
3523 | If you pass a filename without an extension to `dynamic-link', it will | |
3524 | try a few appropriate ones. Thus, the most platform ignorant way is | |
3525 | to specify a name like "libfoo", without any directories and | |
3526 | extensions. | |
0573ddae | 3527 | |
91163914 MD |
3528 | ** Guile COOP threads are now compatible with LinuxThreads |
3529 | ||
3530 | Previously, COOP threading wasn't possible in applications linked with | |
3531 | Linux POSIX threads due to their use of the stack pointer to find the | |
3532 | thread context. This has now been fixed with a workaround which uses | |
3533 | the pthreads to allocate the stack. | |
3534 | ||
6c0201ad | 3535 | ** New primitives: `pkgdata-dir', `site-dir', `library-dir' |
62b82274 | 3536 | |
9770d235 MD |
3537 | ** Positions of erring expression in scripts |
3538 | ||
3539 | With version 1.3.4, the location of the erring expression in Guile | |
3540 | scipts is no longer automatically reported. (This should have been | |
3541 | documented before the 1.3.4 release.) | |
3542 | ||
3543 | You can get this information by enabling recording of positions of | |
3544 | source expressions and running the debugging evaluator. Put this at | |
3545 | the top of your script (or in your "site" file): | |
3546 | ||
3547 | (read-enable 'positions) | |
3548 | (debug-enable 'debug) | |
3549 | ||
0573ddae MD |
3550 | ** Backtraces in scripts |
3551 | ||
3552 | It is now possible to get backtraces in scripts. | |
3553 | ||
3554 | Put | |
3555 | ||
3556 | (debug-enable 'debug 'backtrace) | |
3557 | ||
3558 | at the top of the script. | |
3559 | ||
3560 | (The first options enables the debugging evaluator. | |
3561 | The second enables backtraces.) | |
3562 | ||
e8855f8d MD |
3563 | ** Part of module system symbol lookup now implemented in C |
3564 | ||
3565 | The eval closure of most modules is now implemented in C. Since this | |
3566 | was one of the bottlenecks for loading speed, Guile now loads code | |
3567 | substantially faster than before. | |
3568 | ||
f25f761d GH |
3569 | ** Attempting to get the value of an unbound variable now produces |
3570 | an exception with a key of 'unbound-variable instead of 'misc-error. | |
3571 | ||
1a35eadc GH |
3572 | ** The initial default output port is now unbuffered if it's using a |
3573 | tty device. Previously in this situation it was line-buffered. | |
3574 | ||
820920e6 MD |
3575 | ** New hook: after-gc-hook |
3576 | ||
3577 | after-gc-hook takes over the role of gc-thunk. This hook is run at | |
3578 | the first SCM_TICK after a GC. (Thus, the code is run at the same | |
3579 | point during evaluation as signal handlers.) | |
3580 | ||
3581 | Note that this hook should be used only for diagnostic and debugging | |
3582 | purposes. It is not certain that it will continue to be well-defined | |
3583 | when this hook is run in the future. | |
3584 | ||
3585 | C programmers: Note the new C level hooks scm_before_gc_c_hook, | |
3586 | scm_before_sweep_c_hook, scm_after_gc_c_hook. | |
3587 | ||
b5074b23 MD |
3588 | ** Improvements to garbage collector |
3589 | ||
3590 | Guile 1.4 has a new policy for triggering heap allocation and | |
3591 | determining the sizes of heap segments. It fixes a number of problems | |
3592 | in the old GC. | |
3593 | ||
3594 | 1. The new policy can handle two separate pools of cells | |
3595 | (2-word/4-word) better. (The old policy would run wild, allocating | |
3596 | more and more memory for certain programs.) | |
3597 | ||
3598 | 2. The old code would sometimes allocate far too much heap so that the | |
3599 | Guile process became gigantic. The new code avoids this. | |
3600 | ||
3601 | 3. The old code would sometimes allocate too little so that few cells | |
3602 | were freed at GC so that, in turn, too much time was spent in GC. | |
3603 | ||
3604 | 4. The old code would often trigger heap allocation several times in a | |
3605 | row. (The new scheme predicts how large the segments needs to be | |
3606 | in order not to need further allocation.) | |
3607 | ||
e8855f8d MD |
3608 | All in all, the new GC policy will make larger applications more |
3609 | efficient. | |
3610 | ||
b5074b23 MD |
3611 | The new GC scheme also is prepared for POSIX threading. Threads can |
3612 | allocate private pools of cells ("clusters") with just a single | |
3613 | function call. Allocation of single cells from such a cluster can | |
3614 | then proceed without any need of inter-thread synchronization. | |
3615 | ||
3616 | ** New environment variables controlling GC parameters | |
3617 | ||
3618 | GUILE_MAX_SEGMENT_SIZE Maximal segment size | |
3619 | (default = 2097000) | |
3620 | ||
3621 | Allocation of 2-word cell heaps: | |
3622 | ||
3623 | GUILE_INIT_SEGMENT_SIZE_1 Size of initial heap segment in bytes | |
3624 | (default = 360000) | |
3625 | ||
3626 | GUILE_MIN_YIELD_1 Minimum number of freed cells at each | |
3627 | GC in percent of total heap size | |
3628 | (default = 40) | |
3629 | ||
3630 | Allocation of 4-word cell heaps | |
3631 | (used for real numbers and misc other objects): | |
3632 | ||
3633 | GUILE_INIT_SEGMENT_SIZE_2, GUILE_MIN_YIELD_2 | |
3634 | ||
3635 | (See entry "Way for application to customize GC parameters" under | |
3636 | section "Changes to the scm_ interface" below.) | |
3637 | ||
67ef2dca MD |
3638 | ** Guile now implements reals using 4-word cells |
3639 | ||
3640 | This speeds up computation with reals. (They were earlier allocated | |
3641 | with `malloc'.) There is still some room for optimizations, however. | |
3642 | ||
3643 | ** Some further steps toward POSIX thread support have been taken | |
3644 | ||
3645 | *** Guile's critical sections (SCM_DEFER/ALLOW_INTS) | |
3646 | don't have much effect any longer, and many of them will be removed in | |
3647 | next release. | |
3648 | ||
3649 | *** Signals | |
3650 | are only handled at the top of the evaluator loop, immediately after | |
3651 | I/O, and in scm_equalp. | |
3652 | ||
3653 | *** The GC can allocate thread private pools of pairs. | |
3654 | ||
0af43c4a MD |
3655 | * Changes to Scheme functions and syntax |
3656 | ||
a0128ebe | 3657 | ** close-input-port and close-output-port are now R5RS |
7c1e0b12 | 3658 | |
a0128ebe | 3659 | These procedures have been turned into primitives and have R5RS behaviour. |
7c1e0b12 | 3660 | |
0af43c4a MD |
3661 | ** New procedure: simple-format PORT MESSAGE ARG1 ... |
3662 | ||
3663 | (ice-9 boot) makes `format' an alias for `simple-format' until possibly | |
3664 | extended by the more sophisticated version in (ice-9 format) | |
3665 | ||
3666 | (simple-format port message . args) | |
3667 | Write MESSAGE to DESTINATION, defaulting to `current-output-port'. | |
3668 | MESSAGE can contain ~A (was %s) and ~S (was %S) escapes. When printed, | |
3669 | the escapes are replaced with corresponding members of ARGS: | |
3670 | ~A formats using `display' and ~S formats using `write'. | |
3671 | If DESTINATION is #t, then use the `current-output-port', | |
3672 | if DESTINATION is #f, then return a string containing the formatted text. | |
3673 | Does not add a trailing newline." | |
3674 | ||
3675 | ** string-ref: the second argument is no longer optional. | |
3676 | ||
3677 | ** string, list->string: no longer accept strings in their arguments, | |
3678 | only characters, for compatibility with R5RS. | |
3679 | ||
3680 | ** New procedure: port-closed? PORT | |
3681 | Returns #t if PORT is closed or #f if it is open. | |
3682 | ||
0a9e521f MD |
3683 | ** Deprecated: list* |
3684 | ||
3685 | The list* functionality is now provided by cons* (SRFI-1 compliant) | |
3686 | ||
b5074b23 MD |
3687 | ** New procedure: cons* ARG1 ARG2 ... ARGn |
3688 | ||
3689 | Like `list', but the last arg provides the tail of the constructed list, | |
3690 | returning (cons ARG1 (cons ARG2 (cons ... ARGn))). | |
3691 | ||
3692 | Requires at least one argument. If given one argument, that argument | |
3693 | is returned as result. | |
3694 | ||
3695 | This function is called `list*' in some other Schemes and in Common LISP. | |
3696 | ||
341f78c9 MD |
3697 | ** Removed deprecated: serial-map, serial-array-copy!, serial-array-map! |
3698 | ||
e8855f8d MD |
3699 | ** New procedure: object-documentation OBJECT |
3700 | ||
3701 | Returns the documentation string associated with OBJECT. The | |
3702 | procedure uses a caching mechanism so that subsequent lookups are | |
3703 | faster. | |
3704 | ||
3705 | Exported by (ice-9 documentation). | |
3706 | ||
3707 | ** module-name now returns full names of modules | |
3708 | ||
3709 | Previously, only the last part of the name was returned (`session' for | |
3710 | `(ice-9 session)'). Ex: `(ice-9 session)'. | |
3711 | ||
894a712b DH |
3712 | * Changes to the gh_ interface |
3713 | ||
3714 | ** Deprecated: gh_int2scmb | |
3715 | ||
3716 | Use gh_bool2scm instead. | |
3717 | ||
a2349a28 GH |
3718 | * Changes to the scm_ interface |
3719 | ||
810e1aec MD |
3720 | ** Guile primitives now carry docstrings! |
3721 | ||
3722 | Thanks to Greg Badros! | |
3723 | ||
0a9e521f | 3724 | ** Guile primitives are defined in a new way: SCM_DEFINE/SCM_DEFINE1/SCM_PROC |
0af43c4a | 3725 | |
0a9e521f MD |
3726 | Now Guile primitives are defined using the SCM_DEFINE/SCM_DEFINE1/SCM_PROC |
3727 | macros and must contain a docstring that is extracted into foo.doc using a new | |
0af43c4a MD |
3728 | guile-doc-snarf script (that uses guile-doc-snarf.awk). |
3729 | ||
0a9e521f MD |
3730 | However, a major overhaul of these macros is scheduled for the next release of |
3731 | guile. | |
3732 | ||
0af43c4a MD |
3733 | ** Guile primitives use a new technique for validation of arguments |
3734 | ||
3735 | SCM_VALIDATE_* macros are defined to ease the redundancy and improve | |
3736 | the readability of argument checking. | |
3737 | ||
3738 | ** All (nearly?) K&R prototypes for functions replaced with ANSI C equivalents. | |
3739 | ||
894a712b | 3740 | ** New macros: SCM_PACK, SCM_UNPACK |
f8a72ca4 MD |
3741 | |
3742 | Compose/decompose an SCM value. | |
3743 | ||
894a712b DH |
3744 | The SCM type is now treated as an abstract data type and may be defined as a |
3745 | long, a void* or as a struct, depending on the architecture and compile time | |
3746 | options. This makes it easier to find several types of bugs, for example when | |
3747 | SCM values are treated as integers without conversion. Values of the SCM type | |
3748 | should be treated as "atomic" values. These macros are used when | |
f8a72ca4 MD |
3749 | composing/decomposing an SCM value, either because you want to access |
3750 | individual bits, or because you want to treat it as an integer value. | |
3751 | ||
3752 | E.g., in order to set bit 7 in an SCM value x, use the expression | |
3753 | ||
3754 | SCM_PACK (SCM_UNPACK (x) | 0x80) | |
3755 | ||
e11f8b42 DH |
3756 | ** The name property of hooks is deprecated. |
3757 | Thus, the use of SCM_HOOK_NAME and scm_make_hook_with_name is deprecated. | |
3758 | ||
3759 | You can emulate this feature by using object properties. | |
3760 | ||
6c0201ad | 3761 | ** Deprecated macros: SCM_INPORTP, SCM_OUTPORTP, SCM_CRDY, SCM_ICHRP, |
894a712b DH |
3762 | SCM_ICHR, SCM_MAKICHR, SCM_SETJMPBUF, SCM_NSTRINGP, SCM_NRWSTRINGP, |
3763 | SCM_NVECTORP | |
f8a72ca4 | 3764 | |
894a712b | 3765 | These macros will be removed in a future release of Guile. |
7c1e0b12 | 3766 | |
6c0201ad | 3767 | ** The following types, functions and macros from numbers.h are deprecated: |
0a9e521f MD |
3768 | scm_dblproc, SCM_UNEGFIXABLE, SCM_FLOBUFLEN, SCM_INEXP, SCM_CPLXP, SCM_REAL, |
3769 | SCM_IMAG, SCM_REALPART, scm_makdbl, SCM_SINGP, SCM_NUM2DBL, SCM_NO_BIGDIG | |
3770 | ||
a2349a28 GH |
3771 | ** Port internals: the rw_random variable in the scm_port structure |
3772 | must be set to non-zero in any random access port. In recent Guile | |
3773 | releases it was only set for bidirectional random-access ports. | |
3774 | ||
7dcb364d GH |
3775 | ** Port internals: the seek ptob procedure is now responsible for |
3776 | resetting the buffers if required. The change was made so that in the | |
3777 | special case of reading the current position (i.e., seek p 0 SEEK_CUR) | |
3778 | the fport and strport ptobs can avoid resetting the buffers, | |
3779 | in particular to avoid discarding unread chars. An existing port | |
3780 | type can be fixed by adding something like the following to the | |
3781 | beginning of the ptob seek procedure: | |
3782 | ||
3783 | if (pt->rw_active == SCM_PORT_READ) | |
3784 | scm_end_input (object); | |
3785 | else if (pt->rw_active == SCM_PORT_WRITE) | |
3786 | ptob->flush (object); | |
3787 | ||
3788 | although to actually avoid resetting the buffers and discard unread | |
3789 | chars requires further hacking that depends on the characteristics | |
3790 | of the ptob. | |
3791 | ||
894a712b DH |
3792 | ** Deprecated functions: scm_fseek, scm_tag |
3793 | ||
3794 | These functions are no longer used and will be removed in a future version. | |
3795 | ||
f25f761d GH |
3796 | ** The scm_sysmissing procedure is no longer used in libguile. |
3797 | Unless it turns out to be unexpectedly useful to somebody, it will be | |
3798 | removed in a future version. | |
3799 | ||
0af43c4a MD |
3800 | ** The format of error message strings has changed |
3801 | ||
3802 | The two C procedures: scm_display_error and scm_error, as well as the | |
3803 | primitive `scm-error', now use scm_simple_format to do their work. | |
3804 | This means that the message strings of all code must be updated to use | |
3805 | ~A where %s was used before, and ~S where %S was used before. | |
3806 | ||
3807 | During the period when there still are a lot of old Guiles out there, | |
3808 | you might want to support both old and new versions of Guile. | |
3809 | ||
3810 | There are basically two methods to achieve this. Both methods use | |
3811 | autoconf. Put | |
3812 | ||
3813 | AC_CHECK_FUNCS(scm_simple_format) | |
3814 | ||
3815 | in your configure.in. | |
3816 | ||
3817 | Method 1: Use the string concatenation features of ANSI C's | |
3818 | preprocessor. | |
3819 | ||
3820 | In C: | |
3821 | ||
3822 | #ifdef HAVE_SCM_SIMPLE_FORMAT | |
3823 | #define FMT_S "~S" | |
3824 | #else | |
3825 | #define FMT_S "%S" | |
3826 | #endif | |
3827 | ||
3828 | Then represent each of your error messages using a preprocessor macro: | |
3829 | ||
3830 | #define E_SPIDER_ERROR "There's a spider in your " ## FMT_S ## "!!!" | |
3831 | ||
3832 | In Scheme: | |
3833 | ||
3834 | (define fmt-s (if (defined? 'simple-format) "~S" "%S")) | |
3835 | (define make-message string-append) | |
3836 | ||
3837 | (define e-spider-error (make-message "There's a spider in your " fmt-s "!!!")) | |
3838 | ||
3839 | Method 2: Use the oldfmt function found in doc/oldfmt.c. | |
3840 | ||
3841 | In C: | |
3842 | ||
3843 | scm_misc_error ("picnic", scm_c_oldfmt0 ("There's a spider in your ~S!!!"), | |
3844 | ...); | |
3845 | ||
3846 | In Scheme: | |
3847 | ||
3848 | (scm-error 'misc-error "picnic" (oldfmt "There's a spider in your ~S!!!") | |
3849 | ...) | |
3850 | ||
3851 | ||
f3b5e185 MD |
3852 | ** Deprecated: coop_mutex_init, coop_condition_variable_init |
3853 | ||
3854 | Don't use the functions coop_mutex_init and | |
3855 | coop_condition_variable_init. They will change. | |
3856 | ||
3857 | Use scm_mutex_init and scm_cond_init instead. | |
3858 | ||
f3b5e185 MD |
3859 | ** New function: int scm_cond_timedwait (scm_cond_t *COND, scm_mutex_t *MUTEX, const struct timespec *ABSTIME) |
3860 | `scm_cond_timedwait' atomically unlocks MUTEX and waits on | |
3861 | COND, as `scm_cond_wait' does, but it also bounds the duration | |
3862 | of the wait. If COND has not been signaled before time ABSTIME, | |
3863 | the mutex MUTEX is re-acquired and `scm_cond_timedwait' | |
3864 | returns the error code `ETIMEDOUT'. | |
3865 | ||
3866 | The ABSTIME parameter specifies an absolute time, with the same | |
3867 | origin as `time' and `gettimeofday': an ABSTIME of 0 corresponds | |
3868 | to 00:00:00 GMT, January 1, 1970. | |
3869 | ||
3870 | ** New function: scm_cond_broadcast (scm_cond_t *COND) | |
3871 | `scm_cond_broadcast' restarts all the threads that are waiting | |
3872 | on the condition variable COND. Nothing happens if no threads are | |
3873 | waiting on COND. | |
3874 | ||
3875 | ** New function: scm_key_create (scm_key_t *KEY, void (*destr_function) (void *)) | |
3876 | `scm_key_create' allocates a new TSD key. The key is stored in | |
3877 | the location pointed to by KEY. There is no limit on the number | |
3878 | of keys allocated at a given time. The value initially associated | |
3879 | with the returned key is `NULL' in all currently executing threads. | |
3880 | ||
3881 | The DESTR_FUNCTION argument, if not `NULL', specifies a destructor | |
3882 | function associated with the key. When a thread terminates, | |
3883 | DESTR_FUNCTION is called on the value associated with the key in | |
3884 | that thread. The DESTR_FUNCTION is not called if a key is deleted | |
3885 | with `scm_key_delete' or a value is changed with | |
3886 | `scm_setspecific'. The order in which destructor functions are | |
3887 | called at thread termination time is unspecified. | |
3888 | ||
3889 | Destructors are not yet implemented. | |
3890 | ||
3891 | ** New function: scm_setspecific (scm_key_t KEY, const void *POINTER) | |
3892 | `scm_setspecific' changes the value associated with KEY in the | |
3893 | calling thread, storing the given POINTER instead. | |
3894 | ||
3895 | ** New function: scm_getspecific (scm_key_t KEY) | |
3896 | `scm_getspecific' returns the value currently associated with | |
3897 | KEY in the calling thread. | |
3898 | ||
3899 | ** New function: scm_key_delete (scm_key_t KEY) | |
3900 | `scm_key_delete' deallocates a TSD key. It does not check | |
3901 | whether non-`NULL' values are associated with that key in the | |
3902 | currently executing threads, nor call the destructor function | |
3903 | associated with the key. | |
3904 | ||
820920e6 MD |
3905 | ** New function: scm_c_hook_init (scm_c_hook_t *HOOK, void *HOOK_DATA, scm_c_hook_type_t TYPE) |
3906 | ||
3907 | Initialize a C level hook HOOK with associated HOOK_DATA and type | |
3908 | TYPE. (See scm_c_hook_run ().) | |
3909 | ||
3910 | ** New function: scm_c_hook_add (scm_c_hook_t *HOOK, scm_c_hook_function_t FUNC, void *FUNC_DATA, int APPENDP) | |
3911 | ||
3912 | Add hook function FUNC with associated FUNC_DATA to HOOK. If APPENDP | |
3913 | is true, add it last, otherwise first. The same FUNC can be added | |
3914 | multiple times if FUNC_DATA differ and vice versa. | |
3915 | ||
3916 | ** New function: scm_c_hook_remove (scm_c_hook_t *HOOK, scm_c_hook_function_t FUNC, void *FUNC_DATA) | |
3917 | ||
3918 | Remove hook function FUNC with associated FUNC_DATA from HOOK. A | |
3919 | function is only removed if both FUNC and FUNC_DATA matches. | |
3920 | ||
3921 | ** New function: void *scm_c_hook_run (scm_c_hook_t *HOOK, void *DATA) | |
3922 | ||
3923 | Run hook HOOK passing DATA to the hook functions. | |
3924 | ||
3925 | If TYPE is SCM_C_HOOK_NORMAL, all hook functions are run. The value | |
3926 | returned is undefined. | |
3927 | ||
3928 | If TYPE is SCM_C_HOOK_OR, hook functions are run until a function | |
3929 | returns a non-NULL value. This value is returned as the result of | |
3930 | scm_c_hook_run. If all functions return NULL, NULL is returned. | |
3931 | ||
3932 | If TYPE is SCM_C_HOOK_AND, hook functions are run until a function | |
3933 | returns a NULL value, and NULL is returned. If all functions returns | |
3934 | a non-NULL value, the last value is returned. | |
3935 | ||
3936 | ** New C level GC hooks | |
3937 | ||
3938 | Five new C level hooks has been added to the garbage collector. | |
3939 | ||
3940 | scm_before_gc_c_hook | |
3941 | scm_after_gc_c_hook | |
3942 | ||
3943 | are run before locking and after unlocking the heap. The system is | |
3944 | thus in a mode where evaluation can take place. (Except that | |
3945 | scm_before_gc_c_hook must not allocate new cells.) | |
3946 | ||
3947 | scm_before_mark_c_hook | |
3948 | scm_before_sweep_c_hook | |
3949 | scm_after_sweep_c_hook | |
3950 | ||
3951 | are run when the heap is locked. These are intended for extension of | |
3952 | the GC in a modular fashion. Examples are the weaks and guardians | |
3953 | modules. | |
3954 | ||
b5074b23 MD |
3955 | ** Way for application to customize GC parameters |
3956 | ||
3957 | The application can set up other default values for the GC heap | |
3958 | allocation parameters | |
3959 | ||
3960 | GUILE_INIT_HEAP_SIZE_1, GUILE_MIN_YIELD_1, | |
3961 | GUILE_INIT_HEAP_SIZE_2, GUILE_MIN_YIELD_2, | |
3962 | GUILE_MAX_SEGMENT_SIZE, | |
3963 | ||
3964 | by setting | |
3965 | ||
3966 | scm_default_init_heap_size_1, scm_default_min_yield_1, | |
3967 | scm_default_init_heap_size_2, scm_default_min_yield_2, | |
3968 | scm_default_max_segment_size | |
3969 | ||
3970 | respectively before callong scm_boot_guile. | |
3971 | ||
3972 | (See entry "New environment variables ..." in section | |
3973 | "Changes to the stand-alone interpreter" above.) | |
3974 | ||
9704841c MD |
3975 | ** scm_protect_object/scm_unprotect_object now nest |
3976 | ||
67ef2dca MD |
3977 | This means that you can call scm_protect_object multiple times on an |
3978 | object and count on the object being protected until | |
3979 | scm_unprotect_object has been call the same number of times. | |
3980 | ||
3981 | The functions also have better time complexity. | |
3982 | ||
3983 | Still, it is usually possible to structure the application in a way | |
3984 | that you don't need to use these functions. For example, if you use a | |
3985 | protected standard Guile list to keep track of live objects rather | |
3986 | than some custom data type, objects will die a natural death when they | |
3987 | are no longer needed. | |
3988 | ||
0a9e521f MD |
3989 | ** Deprecated type tags: scm_tc16_flo, scm_tc_flo, scm_tc_dblr, scm_tc_dblc |
3990 | ||
3991 | Guile does not provide the float representation for inexact real numbers any | |
3992 | more. Now, only doubles are used to represent inexact real numbers. Further, | |
3993 | the tag names scm_tc_dblr and scm_tc_dblc have been changed to scm_tc16_real | |
3994 | and scm_tc16_complex, respectively. | |
3995 | ||
341f78c9 MD |
3996 | ** Removed deprecated type scm_smobfuns |
3997 | ||
3998 | ** Removed deprecated function scm_newsmob | |
3999 | ||
b5074b23 MD |
4000 | ** Warning: scm_make_smob_type_mfpe might become deprecated in a future release |
4001 | ||
4002 | There is an ongoing discussion among the developers whether to | |
4003 | deprecate `scm_make_smob_type_mfpe' or not. Please use the current | |
4004 | standard interface (scm_make_smob_type, scm_set_smob_XXX) in new code | |
4005 | until this issue has been settled. | |
4006 | ||
341f78c9 MD |
4007 | ** Removed deprecated type tag scm_tc16_kw |
4008 | ||
2728d7f4 MD |
4009 | ** Added type tag scm_tc16_keyword |
4010 | ||
4011 | (This was introduced already in release 1.3.4 but was not documented | |
4012 | until now.) | |
4013 | ||
67ef2dca MD |
4014 | ** gdb_print now prints "*** Guile not initialized ***" until Guile initialized |
4015 | ||
f25f761d GH |
4016 | * Changes to system call interfaces: |
4017 | ||
28d77376 GH |
4018 | ** The "select" procedure now tests port buffers for the ability to |
4019 | provide input or accept output. Previously only the underlying file | |
4020 | descriptors were checked. | |
4021 | ||
bd9e24b3 GH |
4022 | ** New variable PIPE_BUF: the maximum number of bytes that can be |
4023 | atomically written to a pipe. | |
4024 | ||
f25f761d GH |
4025 | ** If a facility is not available on the system when Guile is |
4026 | compiled, the corresponding primitive procedure will not be defined. | |
4027 | Previously it would have been defined but would throw a system-error | |
4028 | exception if called. Exception handlers which catch this case may | |
4029 | need minor modification: an error will be thrown with key | |
4030 | 'unbound-variable instead of 'system-error. Alternatively it's | |
4031 | now possible to use `defined?' to check whether the facility is | |
4032 | available. | |
4033 | ||
38c1d3c4 | 4034 | ** Procedures which depend on the timezone should now give the correct |
6c0201ad | 4035 | result on systems which cache the TZ environment variable, even if TZ |
38c1d3c4 GH |
4036 | is changed without calling tzset. |
4037 | ||
5c11cc9d GH |
4038 | * Changes to the networking interfaces: |
4039 | ||
4040 | ** New functions: htons, ntohs, htonl, ntohl: for converting short and | |
4041 | long integers between network and host format. For now, it's not | |
4042 | particularly convenient to do this kind of thing, but consider: | |
4043 | ||
4044 | (define write-network-long | |
4045 | (lambda (value port) | |
4046 | (let ((v (make-uniform-vector 1 1 0))) | |
4047 | (uniform-vector-set! v 0 (htonl value)) | |
4048 | (uniform-vector-write v port)))) | |
4049 | ||
4050 | (define read-network-long | |
4051 | (lambda (port) | |
4052 | (let ((v (make-uniform-vector 1 1 0))) | |
4053 | (uniform-vector-read! v port) | |
4054 | (ntohl (uniform-vector-ref v 0))))) | |
4055 | ||
4056 | ** If inet-aton fails, it now throws an error with key 'misc-error | |
4057 | instead of 'system-error, since errno is not relevant. | |
4058 | ||
4059 | ** Certain gethostbyname/gethostbyaddr failures now throw errors with | |
4060 | specific keys instead of 'system-error. The latter is inappropriate | |
4061 | since errno will not have been set. The keys are: | |
afe5177e | 4062 | 'host-not-found, 'try-again, 'no-recovery and 'no-data. |
5c11cc9d GH |
4063 | |
4064 | ** sethostent, setnetent, setprotoent, setservent: now take an | |
4065 | optional argument STAYOPEN, which specifies whether the database | |
4066 | remains open after a database entry is accessed randomly (e.g., using | |
4067 | gethostbyname for the hosts database.) The default is #f. Previously | |
4068 | #t was always used. | |
4069 | ||
cc36e791 | 4070 | \f |
43fa9a05 JB |
4071 | Changes since Guile 1.3.2: |
4072 | ||
0fdcbcaa MD |
4073 | * Changes to the stand-alone interpreter |
4074 | ||
4075 | ** Debugger | |
4076 | ||
4077 | An initial version of the Guile debugger written by Chris Hanson has | |
4078 | been added. The debugger is still under development but is included | |
4079 | in the distribution anyway since it is already quite useful. | |
4080 | ||
4081 | Type | |
4082 | ||
4083 | (debug) | |
4084 | ||
4085 | after an error to enter the debugger. Type `help' inside the debugger | |
4086 | for a description of available commands. | |
4087 | ||
4088 | If you prefer to have stack frames numbered and printed in | |
4089 | anti-chronological order and prefer up in the stack to be down on the | |
4090 | screen as is the case in gdb, you can put | |
4091 | ||
4092 | (debug-enable 'backwards) | |
4093 | ||
4094 | in your .guile startup file. (However, this means that Guile can't | |
4095 | use indentation to indicate stack level.) | |
4096 | ||
4097 | The debugger is autoloaded into Guile at the first use. | |
4098 | ||
4099 | ** Further enhancements to backtraces | |
4100 | ||
4101 | There is a new debug option `width' which controls the maximum width | |
4102 | on the screen of printed stack frames. Fancy printing parameters | |
4103 | ("level" and "length" as in Common LISP) are adaptively adjusted for | |
4104 | each stack frame to give maximum information while still fitting | |
4105 | within the bounds. If the stack frame can't be made to fit by | |
4106 | adjusting parameters, it is simply cut off at the end. This is marked | |
4107 | with a `$'. | |
4108 | ||
4109 | ** Some modules are now only loaded when the repl is started | |
4110 | ||
4111 | The modules (ice-9 debug), (ice-9 session), (ice-9 threads) and (ice-9 | |
4112 | regex) are now loaded into (guile-user) only if the repl has been | |
4113 | started. The effect is that the startup time for scripts has been | |
4114 | reduced to 30% of what it was previously. | |
4115 | ||
4116 | Correctly written scripts load the modules they require at the top of | |
4117 | the file and should not be affected by this change. | |
4118 | ||
ece41168 MD |
4119 | ** Hooks are now represented as smobs |
4120 | ||
6822fe53 MD |
4121 | * Changes to Scheme functions and syntax |
4122 | ||
0ce204b0 MV |
4123 | ** Readline support has changed again. |
4124 | ||
4125 | The old (readline-activator) module is gone. Use (ice-9 readline) | |
4126 | instead, which now contains all readline functionality. So the code | |
4127 | to activate readline is now | |
4128 | ||
4129 | (use-modules (ice-9 readline)) | |
4130 | (activate-readline) | |
4131 | ||
4132 | This should work at any time, including from the guile prompt. | |
4133 | ||
5d195868 JB |
4134 | To avoid confusion about the terms of Guile's license, please only |
4135 | enable readline for your personal use; please don't make it the | |
4136 | default for others. Here is why we make this rather odd-sounding | |
4137 | request: | |
4138 | ||
4139 | Guile is normally licensed under a weakened form of the GNU General | |
4140 | Public License, which allows you to link code with Guile without | |
4141 | placing that code under the GPL. This exception is important to some | |
4142 | people. | |
4143 | ||
4144 | However, since readline is distributed under the GNU General Public | |
4145 | License, when you link Guile with readline, either statically or | |
4146 | dynamically, you effectively change Guile's license to the strict GPL. | |
4147 | Whenever you link any strictly GPL'd code into Guile, uses of Guile | |
4148 | which are normally permitted become forbidden. This is a rather | |
4149 | non-obvious consequence of the licensing terms. | |
4150 | ||
4151 | So, to make sure things remain clear, please let people choose for | |
4152 | themselves whether to link GPL'd libraries like readline with Guile. | |
4153 | ||
25b0654e JB |
4154 | ** regexp-substitute/global has changed slightly, but incompatibly. |
4155 | ||
4156 | If you include a function in the item list, the string of the match | |
4157 | object it receives is the same string passed to | |
4158 | regexp-substitute/global, not some suffix of that string. | |
4159 | Correspondingly, the match's positions are relative to the entire | |
4160 | string, not the suffix. | |
4161 | ||
4162 | If the regexp can match the empty string, the way matches are chosen | |
4163 | from the string has changed. regexp-substitute/global recognizes the | |
4164 | same set of matches that list-matches does; see below. | |
4165 | ||
4166 | ** New function: list-matches REGEXP STRING [FLAGS] | |
4167 | ||
4168 | Return a list of match objects, one for every non-overlapping, maximal | |
4169 | match of REGEXP in STRING. The matches appear in left-to-right order. | |
4170 | list-matches only reports matches of the empty string if there are no | |
4171 | other matches which begin on, end at, or include the empty match's | |
4172 | position. | |
4173 | ||
4174 | If present, FLAGS is passed as the FLAGS argument to regexp-exec. | |
4175 | ||
4176 | ** New function: fold-matches REGEXP STRING INIT PROC [FLAGS] | |
4177 | ||
4178 | For each match of REGEXP in STRING, apply PROC to the match object, | |
4179 | and the last value PROC returned, or INIT for the first call. Return | |
4180 | the last value returned by PROC. We apply PROC to the matches as they | |
4181 | appear from left to right. | |
4182 | ||
4183 | This function recognizes matches according to the same criteria as | |
4184 | list-matches. | |
4185 | ||
4186 | Thus, you could define list-matches like this: | |
4187 | ||
4188 | (define (list-matches regexp string . flags) | |
4189 | (reverse! (apply fold-matches regexp string '() cons flags))) | |
4190 | ||
4191 | If present, FLAGS is passed as the FLAGS argument to regexp-exec. | |
4192 | ||
bc848f7f MD |
4193 | ** Hooks |
4194 | ||
4195 | *** New function: hook? OBJ | |
4196 | ||
4197 | Return #t if OBJ is a hook, otherwise #f. | |
4198 | ||
ece41168 MD |
4199 | *** New function: make-hook-with-name NAME [ARITY] |
4200 | ||
4201 | Return a hook with name NAME and arity ARITY. The default value for | |
4202 | ARITY is 0. The only effect of NAME is that it will appear when the | |
4203 | hook object is printed to ease debugging. | |
4204 | ||
bc848f7f MD |
4205 | *** New function: hook-empty? HOOK |
4206 | ||
4207 | Return #t if HOOK doesn't contain any procedures, otherwise #f. | |
4208 | ||
4209 | *** New function: hook->list HOOK | |
4210 | ||
4211 | Return a list of the procedures that are called when run-hook is | |
4212 | applied to HOOK. | |
4213 | ||
b074884f JB |
4214 | ** `map' signals an error if its argument lists are not all the same length. |
4215 | ||
4216 | This is the behavior required by R5RS, so this change is really a bug | |
4217 | fix. But it seems to affect a lot of people's code, so we're | |
4218 | mentioning it here anyway. | |
4219 | ||
6822fe53 MD |
4220 | ** Print-state handling has been made more transparent |
4221 | ||
4222 | Under certain circumstances, ports are represented as a port with an | |
4223 | associated print state. Earlier, this pair was represented as a pair | |
4224 | (see "Some magic has been added to the printer" below). It is now | |
4225 | indistinguishable (almost; see `get-print-state') from a port on the | |
4226 | user level. | |
4227 | ||
4228 | *** New function: port-with-print-state OUTPUT-PORT PRINT-STATE | |
4229 | ||
4230 | Return a new port with the associated print state PRINT-STATE. | |
4231 | ||
4232 | *** New function: get-print-state OUTPUT-PORT | |
4233 | ||
4234 | Return the print state associated with this port if it exists, | |
4235 | otherwise return #f. | |
4236 | ||
340a8770 | 4237 | *** New function: directory-stream? OBJECT |
77242ff9 | 4238 | |
340a8770 | 4239 | Returns true iff OBJECT is a directory stream --- the sort of object |
77242ff9 GH |
4240 | returned by `opendir'. |
4241 | ||
0fdcbcaa MD |
4242 | ** New function: using-readline? |
4243 | ||
4244 | Return #t if readline is in use in the current repl. | |
4245 | ||
26405bc1 MD |
4246 | ** structs will be removed in 1.4 |
4247 | ||
4248 | Structs will be replaced in Guile 1.4. We will merge GOOPS into Guile | |
4249 | and use GOOPS objects as the fundamental record type. | |
4250 | ||
49199eaa MD |
4251 | * Changes to the scm_ interface |
4252 | ||
26405bc1 MD |
4253 | ** structs will be removed in 1.4 |
4254 | ||
4255 | The entire current struct interface (struct.c, struct.h) will be | |
4256 | replaced in Guile 1.4. We will merge GOOPS into libguile and use | |
4257 | GOOPS objects as the fundamental record type. | |
4258 | ||
49199eaa MD |
4259 | ** The internal representation of subr's has changed |
4260 | ||
4261 | Instead of giving a hint to the subr name, the CAR field of the subr | |
4262 | now contains an index to a subr entry in scm_subr_table. | |
4263 | ||
4264 | *** New variable: scm_subr_table | |
4265 | ||
4266 | An array of subr entries. A subr entry contains the name, properties | |
4267 | and documentation associated with the subr. The properties and | |
4268 | documentation slots are not yet used. | |
4269 | ||
4270 | ** A new scheme for "forwarding" calls to a builtin to a generic function | |
4271 | ||
4272 | It is now possible to extend the functionality of some Guile | |
4273 | primitives by letting them defer a call to a GOOPS generic function on | |
240ed66f | 4274 | argument mismatch. This means that there is no loss of efficiency in |
daf516d6 | 4275 | normal evaluation. |
49199eaa MD |
4276 | |
4277 | Example: | |
4278 | ||
daf516d6 | 4279 | (use-modules (oop goops)) ; Must be GOOPS version 0.2. |
49199eaa MD |
4280 | (define-method + ((x <string>) (y <string>)) |
4281 | (string-append x y)) | |
4282 | ||
86a4d62e MD |
4283 | + will still be as efficient as usual in numerical calculations, but |
4284 | can also be used for concatenating strings. | |
49199eaa | 4285 | |
86a4d62e | 4286 | Who will be the first one to extend Guile's numerical tower to |
daf516d6 MD |
4287 | rationals? :) [OK, there a few other things to fix before this can |
4288 | be made in a clean way.] | |
49199eaa MD |
4289 | |
4290 | *** New snarf macros for defining primitives: SCM_GPROC, SCM_GPROC1 | |
4291 | ||
4292 | New macro: SCM_GPROC (CNAME, SNAME, REQ, OPT, VAR, CFUNC, GENERIC) | |
4293 | ||
4294 | New macro: SCM_GPROC1 (CNAME, SNAME, TYPE, CFUNC, GENERIC) | |
4295 | ||
d02cafe7 | 4296 | These do the same job as SCM_PROC and SCM_PROC1, but they also define |
49199eaa MD |
4297 | a variable GENERIC which can be used by the dispatch macros below. |
4298 | ||
4299 | [This is experimental code which may change soon.] | |
4300 | ||
4301 | *** New macros for forwarding control to a generic on arg type error | |
4302 | ||
4303 | New macro: SCM_WTA_DISPATCH_1 (GENERIC, ARG1, POS, SUBR) | |
4304 | ||
4305 | New macro: SCM_WTA_DISPATCH_2 (GENERIC, ARG1, ARG2, POS, SUBR) | |
4306 | ||
4307 | These correspond to the scm_wta function call, and have the same | |
4308 | behaviour until the user has called the GOOPS primitive | |
4309 | `enable-primitive-generic!'. After that, these macros will apply the | |
4310 | generic function GENERIC to the argument(s) instead of calling | |
4311 | scm_wta. | |
4312 | ||
4313 | [This is experimental code which may change soon.] | |
4314 | ||
4315 | *** New macros for argument testing with generic dispatch | |
4316 | ||
4317 | New macro: SCM_GASSERT1 (COND, GENERIC, ARG1, POS, SUBR) | |
4318 | ||
4319 | New macro: SCM_GASSERT2 (COND, GENERIC, ARG1, ARG2, POS, SUBR) | |
4320 | ||
4321 | These correspond to the SCM_ASSERT macro, but will defer control to | |
4322 | GENERIC on error after `enable-primitive-generic!' has been called. | |
4323 | ||
4324 | [This is experimental code which may change soon.] | |
4325 | ||
4326 | ** New function: SCM scm_eval_body (SCM body, SCM env) | |
4327 | ||
4328 | Evaluates the body of a special form. | |
4329 | ||
4330 | ** The internal representation of struct's has changed | |
4331 | ||
4332 | Previously, four slots were allocated for the procedure(s) of entities | |
4333 | and operators. The motivation for this representation had to do with | |
4334 | the structure of the evaluator, the wish to support tail-recursive | |
4335 | generic functions, and efficiency. Since the generic function | |
4336 | dispatch mechanism has changed, there is no longer a need for such an | |
4337 | expensive representation, and the representation has been simplified. | |
4338 | ||
4339 | This should not make any difference for most users. | |
4340 | ||
4341 | ** GOOPS support has been cleaned up. | |
4342 | ||
4343 | Some code has been moved from eval.c to objects.c and code in both of | |
4344 | these compilation units has been cleaned up and better structured. | |
4345 | ||
4346 | *** New functions for applying generic functions | |
4347 | ||
4348 | New function: SCM scm_apply_generic (GENERIC, ARGS) | |
4349 | New function: SCM scm_call_generic_0 (GENERIC) | |
4350 | New function: SCM scm_call_generic_1 (GENERIC, ARG1) | |
4351 | New function: SCM scm_call_generic_2 (GENERIC, ARG1, ARG2) | |
4352 | New function: SCM scm_call_generic_3 (GENERIC, ARG1, ARG2, ARG3) | |
4353 | ||
ece41168 MD |
4354 | ** Deprecated function: scm_make_named_hook |
4355 | ||
4356 | It is now replaced by: | |
4357 | ||
4358 | ** New function: SCM scm_create_hook (const char *name, int arity) | |
4359 | ||
4360 | Creates a hook in the same way as make-hook above but also | |
4361 | binds a variable named NAME to it. | |
4362 | ||
4363 | This is the typical way of creating a hook from C code. | |
4364 | ||
4365 | Currently, the variable is created in the "current" module. | |
4366 | This might change when we get the new module system. | |
4367 | ||
4368 | [The behaviour is identical to scm_make_named_hook.] | |
4369 | ||
4370 | ||
43fa9a05 | 4371 | \f |
f3227c7a JB |
4372 | Changes since Guile 1.3: |
4373 | ||
6ca345f3 JB |
4374 | * Changes to mailing lists |
4375 | ||
4376 | ** Some of the Guile mailing lists have moved to sourceware.cygnus.com. | |
4377 | ||
4378 | See the README file to find current addresses for all the Guile | |
4379 | mailing lists. | |
4380 | ||
d77fb593 JB |
4381 | * Changes to the distribution |
4382 | ||
1d335863 JB |
4383 | ** Readline support is no longer included with Guile by default. |
4384 | ||
4385 | Based on the different license terms of Guile and Readline, we | |
4386 | concluded that Guile should not *by default* cause the linking of | |
4387 | Readline into an application program. Readline support is now offered | |
4388 | as a separate module, which is linked into an application only when | |
4389 | you explicitly specify it. | |
4390 | ||
4391 | Although Guile is GNU software, its distribution terms add a special | |
4392 | exception to the usual GNU General Public License (GPL). Guile's | |
4393 | license includes a clause that allows you to link Guile with non-free | |
4394 | programs. We add this exception so as not to put Guile at a | |
4395 | disadvantage vis-a-vis other extensibility packages that support other | |
4396 | languages. | |
4397 | ||
4398 | In contrast, the GNU Readline library is distributed under the GNU | |
4399 | General Public License pure and simple. This means that you may not | |
4400 | link Readline, even dynamically, into an application unless it is | |
4401 | distributed under a free software license that is compatible the GPL. | |
4402 | ||
4403 | Because of this difference in distribution terms, an application that | |
4404 | can use Guile may not be able to use Readline. Now users will be | |
4405 | explicitly offered two independent decisions about the use of these | |
4406 | two packages. | |
d77fb593 | 4407 | |
0e8a8468 MV |
4408 | You can activate the readline support by issuing |
4409 | ||
4410 | (use-modules (readline-activator)) | |
4411 | (activate-readline) | |
4412 | ||
4413 | from your ".guile" file, for example. | |
4414 | ||
e4eae9b1 MD |
4415 | * Changes to the stand-alone interpreter |
4416 | ||
67ad463a MD |
4417 | ** All builtins now print as primitives. |
4418 | Previously builtin procedures not belonging to the fundamental subr | |
4419 | types printed as #<compiled closure #<primitive-procedure gsubr-apply>>. | |
4420 | Now, they print as #<primitive-procedure NAME>. | |
4421 | ||
4422 | ** Backtraces slightly more intelligible. | |
4423 | gsubr-apply and macro transformer application frames no longer appear | |
4424 | in backtraces. | |
4425 | ||
69c6acbb JB |
4426 | * Changes to Scheme functions and syntax |
4427 | ||
2a52b429 MD |
4428 | ** Guile now correctly handles internal defines by rewriting them into |
4429 | their equivalent letrec. Previously, internal defines would | |
4430 | incrementally add to the innermost environment, without checking | |
4431 | whether the restrictions specified in RnRS were met. This lead to the | |
4432 | correct behaviour when these restriction actually were met, but didn't | |
4433 | catch all illegal uses. Such an illegal use could lead to crashes of | |
4434 | the Guile interpreter or or other unwanted results. An example of | |
4435 | incorrect internal defines that made Guile behave erratically: | |
4436 | ||
4437 | (let () | |
4438 | (define a 1) | |
4439 | (define (b) a) | |
4440 | (define c (1+ (b))) | |
4441 | (define d 3) | |
4442 | ||
4443 | (b)) | |
4444 | ||
4445 | => 2 | |
4446 | ||
4447 | The problem with this example is that the definition of `c' uses the | |
4448 | value of `b' directly. This confuses the meoization machine of Guile | |
4449 | so that the second call of `b' (this time in a larger environment that | |
4450 | also contains bindings for `c' and `d') refers to the binding of `c' | |
4451 | instead of `a'. You could also make Guile crash with a variation on | |
4452 | this theme: | |
4453 | ||
4454 | (define (foo flag) | |
4455 | (define a 1) | |
4456 | (define (b flag) (if flag a 1)) | |
4457 | (define c (1+ (b flag))) | |
4458 | (define d 3) | |
4459 | ||
4460 | (b #t)) | |
4461 | ||
4462 | (foo #f) | |
4463 | (foo #t) | |
4464 | ||
4465 | From now on, Guile will issue an `Unbound variable: b' error message | |
4466 | for both examples. | |
4467 | ||
36d3d540 MD |
4468 | ** Hooks |
4469 | ||
4470 | A hook contains a list of functions which should be called on | |
4471 | particular occasions in an existing program. Hooks are used for | |
4472 | customization. | |
4473 | ||
4474 | A window manager might have a hook before-window-map-hook. The window | |
4475 | manager uses the function run-hooks to call all functions stored in | |
4476 | before-window-map-hook each time a window is mapped. The user can | |
4477 | store functions in the hook using add-hook!. | |
4478 | ||
4479 | In Guile, hooks are first class objects. | |
4480 | ||
4481 | *** New function: make-hook [N_ARGS] | |
4482 | ||
4483 | Return a hook for hook functions which can take N_ARGS arguments. | |
4484 | The default value for N_ARGS is 0. | |
4485 | ||
ad91d6c3 MD |
4486 | (See also scm_make_named_hook below.) |
4487 | ||
36d3d540 MD |
4488 | *** New function: add-hook! HOOK PROC [APPEND_P] |
4489 | ||
4490 | Put PROC at the beginning of the list of functions stored in HOOK. | |
4491 | If APPEND_P is supplied, and non-false, put PROC at the end instead. | |
4492 | ||
4493 | PROC must be able to take the number of arguments specified when the | |
4494 | hook was created. | |
4495 | ||
4496 | If PROC already exists in HOOK, then remove it first. | |
4497 | ||
4498 | *** New function: remove-hook! HOOK PROC | |
4499 | ||
4500 | Remove PROC from the list of functions in HOOK. | |
4501 | ||
4502 | *** New function: reset-hook! HOOK | |
4503 | ||
4504 | Clear the list of hook functions stored in HOOK. | |
4505 | ||
4506 | *** New function: run-hook HOOK ARG1 ... | |
4507 | ||
4508 | Run all hook functions stored in HOOK with arguments ARG1 ... . | |
4509 | The number of arguments supplied must correspond to the number given | |
4510 | when the hook was created. | |
4511 | ||
56a19408 MV |
4512 | ** The function `dynamic-link' now takes optional keyword arguments. |
4513 | The only keyword argument that is currently defined is `:global | |
4514 | BOOL'. With it, you can control whether the shared library will be | |
4515 | linked in global mode or not. In global mode, the symbols from the | |
4516 | linked library can be used to resolve references from other | |
4517 | dynamically linked libraries. In non-global mode, the linked | |
4518 | library is essentially invisible and can only be accessed via | |
4519 | `dynamic-func', etc. The default is now to link in global mode. | |
4520 | Previously, the default has been non-global mode. | |
4521 | ||
4522 | The `#:global' keyword is only effective on platforms that support | |
4523 | the dlopen family of functions. | |
4524 | ||
ad226f25 | 4525 | ** New function `provided?' |
b7e13f65 JB |
4526 | |
4527 | - Function: provided? FEATURE | |
4528 | Return true iff FEATURE is supported by this installation of | |
4529 | Guile. FEATURE must be a symbol naming a feature; the global | |
4530 | variable `*features*' is a list of available features. | |
4531 | ||
ad226f25 JB |
4532 | ** Changes to the module (ice-9 expect): |
4533 | ||
4534 | *** The expect-strings macro now matches `$' in a regular expression | |
4535 | only at a line-break or end-of-file by default. Previously it would | |
ab711359 JB |
4536 | match the end of the string accumulated so far. The old behaviour |
4537 | can be obtained by setting the variable `expect-strings-exec-flags' | |
4538 | to 0. | |
ad226f25 JB |
4539 | |
4540 | *** The expect-strings macro now uses a variable `expect-strings-exec-flags' | |
4541 | for the regexp-exec flags. If `regexp/noteol' is included, then `$' | |
4542 | in a regular expression will still match before a line-break or | |
4543 | end-of-file. The default is `regexp/noteol'. | |
4544 | ||
6c0201ad | 4545 | *** The expect-strings macro now uses a variable |
ad226f25 JB |
4546 | `expect-strings-compile-flags' for the flags to be supplied to |
4547 | `make-regexp'. The default is `regexp/newline', which was previously | |
4548 | hard-coded. | |
4549 | ||
4550 | *** The expect macro now supplies two arguments to a match procedure: | |
ab711359 JB |
4551 | the current accumulated string and a flag to indicate whether |
4552 | end-of-file has been reached. Previously only the string was supplied. | |
4553 | If end-of-file is reached, the match procedure will be called an | |
4554 | additional time with the same accumulated string as the previous call | |
4555 | but with the flag set. | |
ad226f25 | 4556 | |
b7e13f65 JB |
4557 | ** New module (ice-9 format), implementing the Common Lisp `format' function. |
4558 | ||
4559 | This code, and the documentation for it that appears here, was | |
4560 | borrowed from SLIB, with minor adaptations for Guile. | |
4561 | ||
4562 | - Function: format DESTINATION FORMAT-STRING . ARGUMENTS | |
4563 | An almost complete implementation of Common LISP format description | |
4564 | according to the CL reference book `Common LISP' from Guy L. | |
4565 | Steele, Digital Press. Backward compatible to most of the | |
4566 | available Scheme format implementations. | |
4567 | ||
4568 | Returns `#t', `#f' or a string; has side effect of printing | |
4569 | according to FORMAT-STRING. If DESTINATION is `#t', the output is | |
4570 | to the current output port and `#t' is returned. If DESTINATION | |
4571 | is `#f', a formatted string is returned as the result of the call. | |
4572 | NEW: If DESTINATION is a string, DESTINATION is regarded as the | |
4573 | format string; FORMAT-STRING is then the first argument and the | |
4574 | output is returned as a string. If DESTINATION is a number, the | |
4575 | output is to the current error port if available by the | |
4576 | implementation. Otherwise DESTINATION must be an output port and | |
4577 | `#t' is returned. | |
4578 | ||
4579 | FORMAT-STRING must be a string. In case of a formatting error | |
4580 | format returns `#f' and prints a message on the current output or | |
4581 | error port. Characters are output as if the string were output by | |
4582 | the `display' function with the exception of those prefixed by a | |
4583 | tilde (~). For a detailed description of the FORMAT-STRING syntax | |
4584 | please consult a Common LISP format reference manual. For a test | |
4585 | suite to verify this format implementation load `formatst.scm'. | |
4586 | Please send bug reports to `lutzeb@cs.tu-berlin.de'. | |
4587 | ||
4588 | Note: `format' is not reentrant, i.e. only one `format'-call may | |
4589 | be executed at a time. | |
4590 | ||
4591 | ||
4592 | *** Format Specification (Format version 3.0) | |
4593 | ||
4594 | Please consult a Common LISP format reference manual for a detailed | |
4595 | description of the format string syntax. For a demonstration of the | |
4596 | implemented directives see `formatst.scm'. | |
4597 | ||
4598 | This implementation supports directive parameters and modifiers (`:' | |
4599 | and `@' characters). Multiple parameters must be separated by a comma | |
4600 | (`,'). Parameters can be numerical parameters (positive or negative), | |
4601 | character parameters (prefixed by a quote character (`''), variable | |
4602 | parameters (`v'), number of rest arguments parameter (`#'), empty and | |
4603 | default parameters. Directive characters are case independent. The | |
4604 | general form of a directive is: | |
4605 | ||
4606 | DIRECTIVE ::= ~{DIRECTIVE-PARAMETER,}[:][@]DIRECTIVE-CHARACTER | |
4607 | ||
4608 | DIRECTIVE-PARAMETER ::= [ [-|+]{0-9}+ | 'CHARACTER | v | # ] | |
4609 | ||
4610 | *** Implemented CL Format Control Directives | |
4611 | ||
4612 | Documentation syntax: Uppercase characters represent the | |
4613 | corresponding control directive characters. Lowercase characters | |
4614 | represent control directive parameter descriptions. | |
4615 | ||
4616 | `~A' | |
4617 | Any (print as `display' does). | |
4618 | `~@A' | |
4619 | left pad. | |
4620 | ||
4621 | `~MINCOL,COLINC,MINPAD,PADCHARA' | |
4622 | full padding. | |
4623 | ||
4624 | `~S' | |
4625 | S-expression (print as `write' does). | |
4626 | `~@S' | |
4627 | left pad. | |
4628 | ||
4629 | `~MINCOL,COLINC,MINPAD,PADCHARS' | |
4630 | full padding. | |
4631 | ||
4632 | `~D' | |
4633 | Decimal. | |
4634 | `~@D' | |
4635 | print number sign always. | |
4636 | ||
4637 | `~:D' | |
4638 | print comma separated. | |
4639 | ||
4640 | `~MINCOL,PADCHAR,COMMACHARD' | |
4641 | padding. | |
4642 | ||
4643 | `~X' | |
4644 | Hexadecimal. | |
4645 | `~@X' | |
4646 | print number sign always. | |
4647 | ||
4648 | `~:X' | |
4649 | print comma separated. | |
4650 | ||
4651 | `~MINCOL,PADCHAR,COMMACHARX' | |
4652 | padding. | |
4653 | ||
4654 | `~O' | |
4655 | Octal. | |
4656 | `~@O' | |
4657 | print number sign always. | |
4658 | ||
4659 | `~:O' | |
4660 | print comma separated. | |
4661 | ||
4662 | `~MINCOL,PADCHAR,COMMACHARO' | |
4663 | padding. | |
4664 | ||
4665 | `~B' | |
4666 | Binary. | |
4667 | `~@B' | |
4668 | print number sign always. | |
4669 | ||
4670 | `~:B' | |
4671 | print comma separated. | |
4672 | ||
4673 | `~MINCOL,PADCHAR,COMMACHARB' | |
4674 | padding. | |
4675 | ||
4676 | `~NR' | |
4677 | Radix N. | |
4678 | `~N,MINCOL,PADCHAR,COMMACHARR' | |
4679 | padding. | |
4680 | ||
4681 | `~@R' | |
4682 | print a number as a Roman numeral. | |
4683 | ||
4684 | `~:@R' | |
4685 | print a number as an "old fashioned" Roman numeral. | |
4686 | ||
4687 | `~:R' | |
4688 | print a number as an ordinal English number. | |
4689 | ||
4690 | `~:@R' | |
4691 | print a number as a cardinal English number. | |
4692 | ||
4693 | `~P' | |
4694 | Plural. | |
4695 | `~@P' | |
4696 | prints `y' and `ies'. | |
4697 | ||
4698 | `~:P' | |
4699 | as `~P but jumps 1 argument backward.' | |
4700 | ||
4701 | `~:@P' | |
4702 | as `~@P but jumps 1 argument backward.' | |
4703 | ||
4704 | `~C' | |
4705 | Character. | |
4706 | `~@C' | |
4707 | prints a character as the reader can understand it (i.e. `#\' | |
4708 | prefixing). | |
4709 | ||
4710 | `~:C' | |
4711 | prints a character as emacs does (eg. `^C' for ASCII 03). | |
4712 | ||
4713 | `~F' | |
4714 | Fixed-format floating-point (prints a flonum like MMM.NNN). | |
4715 | `~WIDTH,DIGITS,SCALE,OVERFLOWCHAR,PADCHARF' | |
4716 | `~@F' | |
4717 | If the number is positive a plus sign is printed. | |
4718 | ||
4719 | `~E' | |
4720 | Exponential floating-point (prints a flonum like MMM.NNN`E'EE). | |
4721 | `~WIDTH,DIGITS,EXPONENTDIGITS,SCALE,OVERFLOWCHAR,PADCHAR,EXPONENTCHARE' | |
4722 | `~@E' | |
4723 | If the number is positive a plus sign is printed. | |
4724 | ||
4725 | `~G' | |
4726 | General floating-point (prints a flonum either fixed or | |
4727 | exponential). | |
4728 | `~WIDTH,DIGITS,EXPONENTDIGITS,SCALE,OVERFLOWCHAR,PADCHAR,EXPONENTCHARG' | |
4729 | `~@G' | |
4730 | If the number is positive a plus sign is printed. | |
4731 | ||
4732 | `~$' | |
4733 | Dollars floating-point (prints a flonum in fixed with signs | |
4734 | separated). | |
4735 | `~DIGITS,SCALE,WIDTH,PADCHAR$' | |
4736 | `~@$' | |
4737 | If the number is positive a plus sign is printed. | |
4738 | ||
4739 | `~:@$' | |
4740 | A sign is always printed and appears before the padding. | |
4741 | ||
4742 | `~:$' | |
4743 | The sign appears before the padding. | |
4744 | ||
4745 | `~%' | |
4746 | Newline. | |
4747 | `~N%' | |
4748 | print N newlines. | |
4749 | ||
4750 | `~&' | |
4751 | print newline if not at the beginning of the output line. | |
4752 | `~N&' | |
4753 | prints `~&' and then N-1 newlines. | |
4754 | ||
4755 | `~|' | |
4756 | Page Separator. | |
4757 | `~N|' | |
4758 | print N page separators. | |
4759 | ||
4760 | `~~' | |
4761 | Tilde. | |
4762 | `~N~' | |
4763 | print N tildes. | |
4764 | ||
4765 | `~'<newline> | |
4766 | Continuation Line. | |
4767 | `~:'<newline> | |
4768 | newline is ignored, white space left. | |
4769 | ||
4770 | `~@'<newline> | |
4771 | newline is left, white space ignored. | |
4772 | ||
4773 | `~T' | |
4774 | Tabulation. | |
4775 | `~@T' | |
4776 | relative tabulation. | |
4777 | ||
4778 | `~COLNUM,COLINCT' | |
4779 | full tabulation. | |
4780 | ||
4781 | `~?' | |
4782 | Indirection (expects indirect arguments as a list). | |
4783 | `~@?' | |
4784 | extracts indirect arguments from format arguments. | |
4785 | ||
4786 | `~(STR~)' | |
4787 | Case conversion (converts by `string-downcase'). | |
4788 | `~:(STR~)' | |
4789 | converts by `string-capitalize'. | |
4790 | ||
4791 | `~@(STR~)' | |
4792 | converts by `string-capitalize-first'. | |
4793 | ||
4794 | `~:@(STR~)' | |
4795 | converts by `string-upcase'. | |
4796 | ||
4797 | `~*' | |
4798 | Argument Jumping (jumps 1 argument forward). | |
4799 | `~N*' | |
4800 | jumps N arguments forward. | |
4801 | ||
4802 | `~:*' | |
4803 | jumps 1 argument backward. | |
4804 | ||
4805 | `~N:*' | |
4806 | jumps N arguments backward. | |
4807 | ||
4808 | `~@*' | |
4809 | jumps to the 0th argument. | |
4810 | ||
4811 | `~N@*' | |
4812 | jumps to the Nth argument (beginning from 0) | |
4813 | ||
4814 | `~[STR0~;STR1~;...~;STRN~]' | |
4815 | Conditional Expression (numerical clause conditional). | |
4816 | `~N[' | |
4817 | take argument from N. | |
4818 | ||
4819 | `~@[' | |
4820 | true test conditional. | |
4821 | ||
4822 | `~:[' | |
4823 | if-else-then conditional. | |
4824 | ||
4825 | `~;' | |
4826 | clause separator. | |
4827 | ||
4828 | `~:;' | |
4829 | default clause follows. | |
4830 | ||
4831 | `~{STR~}' | |
4832 | Iteration (args come from the next argument (a list)). | |
4833 | `~N{' | |
4834 | at most N iterations. | |
4835 | ||
4836 | `~:{' | |
4837 | args from next arg (a list of lists). | |
4838 | ||
4839 | `~@{' | |
4840 | args from the rest of arguments. | |
4841 | ||
4842 | `~:@{' | |
4843 | args from the rest args (lists). | |
4844 | ||
4845 | `~^' | |
4846 | Up and out. | |
4847 | `~N^' | |
4848 | aborts if N = 0 | |
4849 | ||
4850 | `~N,M^' | |
4851 | aborts if N = M | |
4852 | ||
4853 | `~N,M,K^' | |
4854 | aborts if N <= M <= K | |
4855 | ||
4856 | *** Not Implemented CL Format Control Directives | |
4857 | ||
4858 | `~:A' | |
4859 | print `#f' as an empty list (see below). | |
4860 | ||
4861 | `~:S' | |
4862 | print `#f' as an empty list (see below). | |
4863 | ||
4864 | `~<~>' | |
4865 | Justification. | |
4866 | ||
4867 | `~:^' | |
4868 | (sorry I don't understand its semantics completely) | |
4869 | ||
4870 | *** Extended, Replaced and Additional Control Directives | |
4871 | ||
4872 | `~MINCOL,PADCHAR,COMMACHAR,COMMAWIDTHD' | |
4873 | `~MINCOL,PADCHAR,COMMACHAR,COMMAWIDTHX' | |
4874 | `~MINCOL,PADCHAR,COMMACHAR,COMMAWIDTHO' | |
4875 | `~MINCOL,PADCHAR,COMMACHAR,COMMAWIDTHB' | |
4876 | `~N,MINCOL,PADCHAR,COMMACHAR,COMMAWIDTHR' | |
4877 | COMMAWIDTH is the number of characters between two comma | |
4878 | characters. | |
4879 | ||
4880 | `~I' | |
4881 | print a R4RS complex number as `~F~@Fi' with passed parameters for | |
4882 | `~F'. | |
4883 | ||
4884 | `~Y' | |
4885 | Pretty print formatting of an argument for scheme code lists. | |
4886 | ||
4887 | `~K' | |
4888 | Same as `~?.' | |
4889 | ||
4890 | `~!' | |
4891 | Flushes the output if format DESTINATION is a port. | |
4892 | ||
4893 | `~_' | |
4894 | Print a `#\space' character | |
4895 | `~N_' | |
4896 | print N `#\space' characters. | |
4897 | ||
4898 | `~/' | |
4899 | Print a `#\tab' character | |
4900 | `~N/' | |
4901 | print N `#\tab' characters. | |
4902 | ||
4903 | `~NC' | |
4904 | Takes N as an integer representation for a character. No arguments | |
4905 | are consumed. N is converted to a character by `integer->char'. N | |
4906 | must be a positive decimal number. | |
4907 | ||
4908 | `~:S' | |
4909 | Print out readproof. Prints out internal objects represented as | |
4910 | `#<...>' as strings `"#<...>"' so that the format output can always | |
4911 | be processed by `read'. | |
4912 | ||
4913 | `~:A' | |
4914 | Print out readproof. Prints out internal objects represented as | |
4915 | `#<...>' as strings `"#<...>"' so that the format output can always | |
4916 | be processed by `read'. | |
4917 | ||
4918 | `~Q' | |
4919 | Prints information and a copyright notice on the format | |
4920 | implementation. | |
4921 | `~:Q' | |
4922 | prints format version. | |
4923 | ||
4924 | `~F, ~E, ~G, ~$' | |
4925 | may also print number strings, i.e. passing a number as a string | |
4926 | and format it accordingly. | |
4927 | ||
4928 | *** Configuration Variables | |
4929 | ||
4930 | The format module exports some configuration variables to suit the | |
4931 | systems and users needs. There should be no modification necessary for | |
4932 | the configuration that comes with Guile. Format detects automatically | |
4933 | if the running scheme system implements floating point numbers and | |
4934 | complex numbers. | |
4935 | ||
4936 | format:symbol-case-conv | |
4937 | Symbols are converted by `symbol->string' so the case type of the | |
4938 | printed symbols is implementation dependent. | |
4939 | `format:symbol-case-conv' is a one arg closure which is either | |
4940 | `#f' (no conversion), `string-upcase', `string-downcase' or | |
4941 | `string-capitalize'. (default `#f') | |
4942 | ||
4943 | format:iobj-case-conv | |
4944 | As FORMAT:SYMBOL-CASE-CONV but applies for the representation of | |
4945 | implementation internal objects. (default `#f') | |
4946 | ||
4947 | format:expch | |
4948 | The character prefixing the exponent value in `~E' printing. | |
4949 | (default `#\E') | |
4950 | ||
4951 | *** Compatibility With Other Format Implementations | |
4952 | ||
4953 | SLIB format 2.x: | |
4954 | See `format.doc'. | |
4955 | ||
4956 | SLIB format 1.4: | |
4957 | Downward compatible except for padding support and `~A', `~S', | |
4958 | `~P', `~X' uppercase printing. SLIB format 1.4 uses C-style | |
4959 | `printf' padding support which is completely replaced by the CL | |
4960 | `format' padding style. | |
4961 | ||
4962 | MIT C-Scheme 7.1: | |
4963 | Downward compatible except for `~', which is not documented | |
4964 | (ignores all characters inside the format string up to a newline | |
4965 | character). (7.1 implements `~a', `~s', ~NEWLINE, `~~', `~%', | |
4966 | numerical and variable parameters and `:/@' modifiers in the CL | |
4967 | sense). | |
4968 | ||
4969 | Elk 1.5/2.0: | |
4970 | Downward compatible except for `~A' and `~S' which print in | |
4971 | uppercase. (Elk implements `~a', `~s', `~~', and `~%' (no | |
4972 | directive parameters or modifiers)). | |
4973 | ||
4974 | Scheme->C 01nov91: | |
4975 | Downward compatible except for an optional destination parameter: | |
4976 | S2C accepts a format call without a destination which returns a | |
4977 | formatted string. This is equivalent to a #f destination in S2C. | |
4978 | (S2C implements `~a', `~s', `~c', `~%', and `~~' (no directive | |
4979 | parameters or modifiers)). | |
4980 | ||
4981 | ||
e7d37b0a | 4982 | ** Changes to string-handling functions. |
b7e13f65 | 4983 | |
e7d37b0a | 4984 | These functions were added to support the (ice-9 format) module, above. |
b7e13f65 | 4985 | |
e7d37b0a JB |
4986 | *** New function: string-upcase STRING |
4987 | *** New function: string-downcase STRING | |
b7e13f65 | 4988 | |
e7d37b0a JB |
4989 | These are non-destructive versions of the existing string-upcase! and |
4990 | string-downcase! functions. | |
b7e13f65 | 4991 | |
e7d37b0a JB |
4992 | *** New function: string-capitalize! STRING |
4993 | *** New function: string-capitalize STRING | |
4994 | ||
4995 | These functions convert the first letter of each word in the string to | |
4996 | upper case. Thus: | |
4997 | ||
4998 | (string-capitalize "howdy there") | |
4999 | => "Howdy There" | |
5000 | ||
5001 | As with the other functions, string-capitalize! modifies the string in | |
5002 | place, while string-capitalize returns a modified copy of its argument. | |
5003 | ||
5004 | *** New function: string-ci->symbol STRING | |
5005 | ||
5006 | Return a symbol whose name is STRING, but having the same case as if | |
5007 | the symbol had be read by `read'. | |
5008 | ||
5009 | Guile can be configured to be sensitive or insensitive to case | |
5010 | differences in Scheme identifiers. If Guile is case-insensitive, all | |
5011 | symbols are converted to lower case on input. The `string-ci->symbol' | |
5012 | function returns a symbol whose name in STRING, transformed as Guile | |
5013 | would if STRING were input. | |
5014 | ||
5015 | *** New function: substring-move! STRING1 START END STRING2 START | |
5016 | ||
5017 | Copy the substring of STRING1 from START (inclusive) to END | |
5018 | (exclusive) to STRING2 at START. STRING1 and STRING2 may be the same | |
5019 | string, and the source and destination areas may overlap; in all | |
5020 | cases, the function behaves as if all the characters were copied | |
5021 | simultanously. | |
5022 | ||
6c0201ad | 5023 | *** Extended functions: substring-move-left! substring-move-right! |
e7d37b0a JB |
5024 | |
5025 | These functions now correctly copy arbitrarily overlapping substrings; | |
5026 | they are both synonyms for substring-move!. | |
b7e13f65 | 5027 | |
b7e13f65 | 5028 | |
deaceb4e JB |
5029 | ** New module (ice-9 getopt-long), with the function `getopt-long'. |
5030 | ||
5031 | getopt-long is a function for parsing command-line arguments in a | |
5032 | manner consistent with other GNU programs. | |
5033 | ||
5034 | (getopt-long ARGS GRAMMAR) | |
5035 | Parse the arguments ARGS according to the argument list grammar GRAMMAR. | |
5036 | ||
5037 | ARGS should be a list of strings. Its first element should be the | |
5038 | name of the program; subsequent elements should be the arguments | |
5039 | that were passed to the program on the command line. The | |
5040 | `program-arguments' procedure returns a list of this form. | |
5041 | ||
5042 | GRAMMAR is a list of the form: | |
5043 | ((OPTION (PROPERTY VALUE) ...) ...) | |
5044 | ||
5045 | Each OPTION should be a symbol. `getopt-long' will accept a | |
5046 | command-line option named `--OPTION'. | |
5047 | Each option can have the following (PROPERTY VALUE) pairs: | |
5048 | ||
5049 | (single-char CHAR) --- Accept `-CHAR' as a single-character | |
5050 | equivalent to `--OPTION'. This is how to specify traditional | |
5051 | Unix-style flags. | |
5052 | (required? BOOL) --- If BOOL is true, the option is required. | |
5053 | getopt-long will raise an error if it is not found in ARGS. | |
5054 | (value BOOL) --- If BOOL is #t, the option accepts a value; if | |
5055 | it is #f, it does not; and if it is the symbol | |
5056 | `optional', the option may appear in ARGS with or | |
6c0201ad | 5057 | without a value. |
deaceb4e JB |
5058 | (predicate FUNC) --- If the option accepts a value (i.e. you |
5059 | specified `(value #t)' for this option), then getopt | |
5060 | will apply FUNC to the value, and throw an exception | |
5061 | if it returns #f. FUNC should be a procedure which | |
5062 | accepts a string and returns a boolean value; you may | |
5063 | need to use quasiquotes to get it into GRAMMAR. | |
5064 | ||
5065 | The (PROPERTY VALUE) pairs may occur in any order, but each | |
5066 | property may occur only once. By default, options do not have | |
5067 | single-character equivalents, are not required, and do not take | |
5068 | values. | |
5069 | ||
5070 | In ARGS, single-character options may be combined, in the usual | |
5071 | Unix fashion: ("-x" "-y") is equivalent to ("-xy"). If an option | |
5072 | accepts values, then it must be the last option in the | |
5073 | combination; the value is the next argument. So, for example, using | |
5074 | the following grammar: | |
5075 | ((apples (single-char #\a)) | |
5076 | (blimps (single-char #\b) (value #t)) | |
5077 | (catalexis (single-char #\c) (value #t))) | |
5078 | the following argument lists would be acceptable: | |
5079 | ("-a" "-b" "bang" "-c" "couth") ("bang" and "couth" are the values | |
5080 | for "blimps" and "catalexis") | |
5081 | ("-ab" "bang" "-c" "couth") (same) | |
5082 | ("-ac" "couth" "-b" "bang") (same) | |
5083 | ("-abc" "couth" "bang") (an error, since `-b' is not the | |
5084 | last option in its combination) | |
5085 | ||
5086 | If an option's value is optional, then `getopt-long' decides | |
5087 | whether it has a value by looking at what follows it in ARGS. If | |
5088 | the next element is a string, and it does not appear to be an | |
5089 | option itself, then that string is the option's value. | |
5090 | ||
5091 | The value of a long option can appear as the next element in ARGS, | |
5092 | or it can follow the option name, separated by an `=' character. | |
5093 | Thus, using the same grammar as above, the following argument lists | |
5094 | are equivalent: | |
5095 | ("--apples" "Braeburn" "--blimps" "Goodyear") | |
5096 | ("--apples=Braeburn" "--blimps" "Goodyear") | |
5097 | ("--blimps" "Goodyear" "--apples=Braeburn") | |
5098 | ||
5099 | If the option "--" appears in ARGS, argument parsing stops there; | |
5100 | subsequent arguments are returned as ordinary arguments, even if | |
5101 | they resemble options. So, in the argument list: | |
5102 | ("--apples" "Granny Smith" "--" "--blimp" "Goodyear") | |
5103 | `getopt-long' will recognize the `apples' option as having the | |
5104 | value "Granny Smith", but it will not recognize the `blimp' | |
5105 | option; it will return the strings "--blimp" and "Goodyear" as | |
5106 | ordinary argument strings. | |
5107 | ||
5108 | The `getopt-long' function returns the parsed argument list as an | |
5109 | assocation list, mapping option names --- the symbols from GRAMMAR | |
5110 | --- onto their values, or #t if the option does not accept a value. | |
5111 | Unused options do not appear in the alist. | |
5112 | ||
5113 | All arguments that are not the value of any option are returned | |
5114 | as a list, associated with the empty list. | |
5115 | ||
5116 | `getopt-long' throws an exception if: | |
5117 | - it finds an unrecognized option in ARGS | |
5118 | - a required option is omitted | |
5119 | - an option that requires an argument doesn't get one | |
5120 | - an option that doesn't accept an argument does get one (this can | |
5121 | only happen using the long option `--opt=value' syntax) | |
5122 | - an option predicate fails | |
5123 | ||
5124 | So, for example: | |
5125 | ||
5126 | (define grammar | |
5127 | `((lockfile-dir (required? #t) | |
5128 | (value #t) | |
5129 | (single-char #\k) | |
5130 | (predicate ,file-is-directory?)) | |
5131 | (verbose (required? #f) | |
5132 | (single-char #\v) | |
5133 | (value #f)) | |
5134 | (x-includes (single-char #\x)) | |
6c0201ad | 5135 | (rnet-server (single-char #\y) |
deaceb4e JB |
5136 | (predicate ,string?)))) |
5137 | ||
6c0201ad | 5138 | (getopt-long '("my-prog" "-vk" "/tmp" "foo1" "--x-includes=/usr/include" |
deaceb4e JB |
5139 | "--rnet-server=lamprod" "--" "-fred" "foo2" "foo3") |
5140 | grammar) | |
5141 | => ((() "foo1" "-fred" "foo2" "foo3") | |
5142 | (rnet-server . "lamprod") | |
5143 | (x-includes . "/usr/include") | |
5144 | (lockfile-dir . "/tmp") | |
5145 | (verbose . #t)) | |
5146 | ||
5147 | ** The (ice-9 getopt-gnu-style) module is obsolete; use (ice-9 getopt-long). | |
5148 | ||
5149 | It will be removed in a few releases. | |
5150 | ||
08394899 MS |
5151 | ** New syntax: lambda* |
5152 | ** New syntax: define* | |
6c0201ad | 5153 | ** New syntax: define*-public |
08394899 MS |
5154 | ** New syntax: defmacro* |
5155 | ** New syntax: defmacro*-public | |
6c0201ad | 5156 | Guile now supports optional arguments. |
08394899 MS |
5157 | |
5158 | `lambda*', `define*', `define*-public', `defmacro*' and | |
5159 | `defmacro*-public' are identical to the non-* versions except that | |
5160 | they use an extended type of parameter list that has the following BNF | |
5161 | syntax (parentheses are literal, square brackets indicate grouping, | |
5162 | and `*', `+' and `?' have the usual meaning): | |
5163 | ||
5164 | ext-param-list ::= ( [identifier]* [#&optional [ext-var-decl]+]? | |
6c0201ad | 5165 | [#&key [ext-var-decl]+ [#&allow-other-keys]?]? |
08394899 MS |
5166 | [[#&rest identifier]|[. identifier]]? ) | [identifier] |
5167 | ||
6c0201ad | 5168 | ext-var-decl ::= identifier | ( identifier expression ) |
08394899 MS |
5169 | |
5170 | The semantics are best illustrated with the following documentation | |
5171 | and examples for `lambda*': | |
5172 | ||
5173 | lambda* args . body | |
5174 | lambda extended for optional and keyword arguments | |
6c0201ad | 5175 | |
08394899 MS |
5176 | lambda* creates a procedure that takes optional arguments. These |
5177 | are specified by putting them inside brackets at the end of the | |
5178 | paramater list, but before any dotted rest argument. For example, | |
5179 | (lambda* (a b #&optional c d . e) '()) | |
5180 | creates a procedure with fixed arguments a and b, optional arguments c | |
5181 | and d, and rest argument e. If the optional arguments are omitted | |
5182 | in a call, the variables for them are unbound in the procedure. This | |
5183 | can be checked with the bound? macro. | |
5184 | ||
5185 | lambda* can also take keyword arguments. For example, a procedure | |
5186 | defined like this: | |
5187 | (lambda* (#&key xyzzy larch) '()) | |
5188 | can be called with any of the argument lists (#:xyzzy 11) | |
5189 | (#:larch 13) (#:larch 42 #:xyzzy 19) (). Whichever arguments | |
5190 | are given as keywords are bound to values. | |
5191 | ||
5192 | Optional and keyword arguments can also be given default values | |
5193 | which they take on when they are not present in a call, by giving a | |
5194 | two-item list in place of an optional argument, for example in: | |
6c0201ad | 5195 | (lambda* (foo #&optional (bar 42) #&key (baz 73)) (list foo bar baz)) |
08394899 MS |
5196 | foo is a fixed argument, bar is an optional argument with default |
5197 | value 42, and baz is a keyword argument with default value 73. | |
5198 | Default value expressions are not evaluated unless they are needed | |
6c0201ad | 5199 | and until the procedure is called. |
08394899 MS |
5200 | |
5201 | lambda* now supports two more special parameter list keywords. | |
5202 | ||
5203 | lambda*-defined procedures now throw an error by default if a | |
5204 | keyword other than one of those specified is found in the actual | |
5205 | passed arguments. However, specifying #&allow-other-keys | |
5206 | immediately after the kyword argument declarations restores the | |
5207 | previous behavior of ignoring unknown keywords. lambda* also now | |
5208 | guarantees that if the same keyword is passed more than once, the | |
5209 | last one passed is the one that takes effect. For example, | |
5210 | ((lambda* (#&key (heads 0) (tails 0)) (display (list heads tails))) | |
5211 | #:heads 37 #:tails 42 #:heads 99) | |
5212 | would result in (99 47) being displayed. | |
5213 | ||
5214 | #&rest is also now provided as a synonym for the dotted syntax rest | |
5215 | argument. The argument lists (a . b) and (a #&rest b) are equivalent in | |
5216 | all respects to lambda*. This is provided for more similarity to DSSSL, | |
5217 | MIT-Scheme and Kawa among others, as well as for refugees from other | |
5218 | Lisp dialects. | |
5219 | ||
5220 | Further documentation may be found in the optargs.scm file itself. | |
5221 | ||
5222 | The optional argument module also exports the macros `let-optional', | |
5223 | `let-optional*', `let-keywords', `let-keywords*' and `bound?'. These | |
5224 | are not documented here because they may be removed in the future, but | |
5225 | full documentation is still available in optargs.scm. | |
5226 | ||
2e132553 JB |
5227 | ** New syntax: and-let* |
5228 | Guile now supports the `and-let*' form, described in the draft SRFI-2. | |
5229 | ||
5230 | Syntax: (land* (<clause> ...) <body> ...) | |
5231 | Each <clause> should have one of the following forms: | |
5232 | (<variable> <expression>) | |
5233 | (<expression>) | |
5234 | <bound-variable> | |
5235 | Each <variable> or <bound-variable> should be an identifier. Each | |
5236 | <expression> should be a valid expression. The <body> should be a | |
5237 | possibly empty sequence of expressions, like the <body> of a | |
5238 | lambda form. | |
5239 | ||
5240 | Semantics: A LAND* expression is evaluated by evaluating the | |
5241 | <expression> or <bound-variable> of each of the <clause>s from | |
5242 | left to right. The value of the first <expression> or | |
5243 | <bound-variable> that evaluates to a false value is returned; the | |
5244 | remaining <expression>s and <bound-variable>s are not evaluated. | |
5245 | The <body> forms are evaluated iff all the <expression>s and | |
5246 | <bound-variable>s evaluate to true values. | |
5247 | ||
5248 | The <expression>s and the <body> are evaluated in an environment | |
5249 | binding each <variable> of the preceding (<variable> <expression>) | |
5250 | clauses to the value of the <expression>. Later bindings | |
5251 | shadow earlier bindings. | |
5252 | ||
5253 | Guile's and-let* macro was contributed by Michael Livshin. | |
5254 | ||
36d3d540 MD |
5255 | ** New sorting functions |
5256 | ||
5257 | *** New function: sorted? SEQUENCE LESS? | |
ed8c8636 MD |
5258 | Returns `#t' when the sequence argument is in non-decreasing order |
5259 | according to LESS? (that is, there is no adjacent pair `... x y | |
5260 | ...' for which `(less? y x)'). | |
5261 | ||
5262 | Returns `#f' when the sequence contains at least one out-of-order | |
5263 | pair. It is an error if the sequence is neither a list nor a | |
5264 | vector. | |
5265 | ||
36d3d540 | 5266 | *** New function: merge LIST1 LIST2 LESS? |
ed8c8636 MD |
5267 | LIST1 and LIST2 are sorted lists. |
5268 | Returns the sorted list of all elements in LIST1 and LIST2. | |
5269 | ||
5270 | Assume that the elements a and b1 in LIST1 and b2 in LIST2 are "equal" | |
5271 | in the sense that (LESS? x y) --> #f for x, y in {a, b1, b2}, | |
5272 | and that a < b1 in LIST1. Then a < b1 < b2 in the result. | |
5273 | (Here "<" should read "comes before".) | |
5274 | ||
36d3d540 | 5275 | *** New procedure: merge! LIST1 LIST2 LESS? |
ed8c8636 MD |
5276 | Merges two lists, re-using the pairs of LIST1 and LIST2 to build |
5277 | the result. If the code is compiled, and LESS? constructs no new | |
5278 | pairs, no pairs at all will be allocated. The first pair of the | |
5279 | result will be either the first pair of LIST1 or the first pair of | |
5280 | LIST2. | |
5281 | ||
36d3d540 | 5282 | *** New function: sort SEQUENCE LESS? |
ed8c8636 MD |
5283 | Accepts either a list or a vector, and returns a new sequence |
5284 | which is sorted. The new sequence is the same type as the input. | |
5285 | Always `(sorted? (sort sequence less?) less?)'. The original | |
5286 | sequence is not altered in any way. The new sequence shares its | |
5287 | elements with the old one; no elements are copied. | |
5288 | ||
36d3d540 | 5289 | *** New procedure: sort! SEQUENCE LESS |
ed8c8636 MD |
5290 | Returns its sorted result in the original boxes. No new storage is |
5291 | allocated at all. Proper usage: (set! slist (sort! slist <)) | |
5292 | ||
36d3d540 | 5293 | *** New function: stable-sort SEQUENCE LESS? |
ed8c8636 MD |
5294 | Similar to `sort' but stable. That is, if "equal" elements are |
5295 | ordered a < b in the original sequence, they will have the same order | |
5296 | in the result. | |
5297 | ||
36d3d540 | 5298 | *** New function: stable-sort! SEQUENCE LESS? |
ed8c8636 MD |
5299 | Similar to `sort!' but stable. |
5300 | Uses temporary storage when sorting vectors. | |
5301 | ||
36d3d540 | 5302 | *** New functions: sort-list, sort-list! |
ed8c8636 MD |
5303 | Added for compatibility with scsh. |
5304 | ||
36d3d540 MD |
5305 | ** New built-in random number support |
5306 | ||
5307 | *** New function: random N [STATE] | |
3e8370c3 MD |
5308 | Accepts a positive integer or real N and returns a number of the |
5309 | same type between zero (inclusive) and N (exclusive). The values | |
5310 | returned have a uniform distribution. | |
5311 | ||
5312 | The optional argument STATE must be of the type produced by | |
416075f1 MD |
5313 | `copy-random-state' or `seed->random-state'. It defaults to the value |
5314 | of the variable `*random-state*'. This object is used to maintain the | |
5315 | state of the pseudo-random-number generator and is altered as a side | |
5316 | effect of the `random' operation. | |
3e8370c3 | 5317 | |
36d3d540 | 5318 | *** New variable: *random-state* |
3e8370c3 MD |
5319 | Holds a data structure that encodes the internal state of the |
5320 | random-number generator that `random' uses by default. The nature | |
5321 | of this data structure is implementation-dependent. It may be | |
5322 | printed out and successfully read back in, but may or may not | |
5323 | function correctly as a random-number state object in another | |
5324 | implementation. | |
5325 | ||
36d3d540 | 5326 | *** New function: copy-random-state [STATE] |
3e8370c3 MD |
5327 | Returns a new object of type suitable for use as the value of the |
5328 | variable `*random-state*' and as a second argument to `random'. | |
5329 | If argument STATE is given, a copy of it is returned. Otherwise a | |
5330 | copy of `*random-state*' is returned. | |
416075f1 | 5331 | |
36d3d540 | 5332 | *** New function: seed->random-state SEED |
416075f1 MD |
5333 | Returns a new object of type suitable for use as the value of the |
5334 | variable `*random-state*' and as a second argument to `random'. | |
5335 | SEED is a string or a number. A new state is generated and | |
5336 | initialized using SEED. | |
3e8370c3 | 5337 | |
36d3d540 | 5338 | *** New function: random:uniform [STATE] |
3e8370c3 MD |
5339 | Returns an uniformly distributed inexact real random number in the |
5340 | range between 0 and 1. | |
5341 | ||
36d3d540 | 5342 | *** New procedure: random:solid-sphere! VECT [STATE] |
3e8370c3 MD |
5343 | Fills VECT with inexact real random numbers the sum of whose |
5344 | squares is less than 1.0. Thinking of VECT as coordinates in | |
5345 | space of dimension N = `(vector-length VECT)', the coordinates are | |
5346 | uniformly distributed within the unit N-shere. The sum of the | |
5347 | squares of the numbers is returned. VECT can be either a vector | |
5348 | or a uniform vector of doubles. | |
5349 | ||
36d3d540 | 5350 | *** New procedure: random:hollow-sphere! VECT [STATE] |
3e8370c3 MD |
5351 | Fills VECT with inexact real random numbers the sum of whose squares |
5352 | is equal to 1.0. Thinking of VECT as coordinates in space of | |
5353 | dimension n = `(vector-length VECT)', the coordinates are uniformly | |
5354 | distributed over the surface of the unit n-shere. VECT can be either | |
5355 | a vector or a uniform vector of doubles. | |
5356 | ||
36d3d540 | 5357 | *** New function: random:normal [STATE] |
3e8370c3 MD |
5358 | Returns an inexact real in a normal distribution with mean 0 and |
5359 | standard deviation 1. For a normal distribution with mean M and | |
5360 | standard deviation D use `(+ M (* D (random:normal)))'. | |
5361 | ||
36d3d540 | 5362 | *** New procedure: random:normal-vector! VECT [STATE] |
3e8370c3 MD |
5363 | Fills VECT with inexact real random numbers which are independent and |
5364 | standard normally distributed (i.e., with mean 0 and variance 1). | |
5365 | VECT can be either a vector or a uniform vector of doubles. | |
5366 | ||
36d3d540 | 5367 | *** New function: random:exp STATE |
3e8370c3 MD |
5368 | Returns an inexact real in an exponential distribution with mean 1. |
5369 | For an exponential distribution with mean U use (* U (random:exp)). | |
5370 | ||
69c6acbb JB |
5371 | ** The range of logand, logior, logxor, logtest, and logbit? have changed. |
5372 | ||
5373 | These functions now operate on numbers in the range of a C unsigned | |
5374 | long. | |
5375 | ||
5376 | These functions used to operate on numbers in the range of a C signed | |
5377 | long; however, this seems inappropriate, because Guile integers don't | |
5378 | overflow. | |
5379 | ||
ba4ee0d6 MD |
5380 | ** New function: make-guardian |
5381 | This is an implementation of guardians as described in | |
5382 | R. Kent Dybvig, Carl Bruggeman, and David Eby (1993) "Guardians in a | |
5383 | Generation-Based Garbage Collector" ACM SIGPLAN Conference on | |
5384 | Programming Language Design and Implementation, June 1993 | |
5385 | ftp://ftp.cs.indiana.edu/pub/scheme-repository/doc/pubs/guardians.ps.gz | |
5386 | ||
88ceea5c MD |
5387 | ** New functions: delq1!, delv1!, delete1! |
5388 | These procedures behave similar to delq! and friends but delete only | |
5389 | one object if at all. | |
5390 | ||
55254a6a MD |
5391 | ** New function: unread-string STRING PORT |
5392 | Unread STRING to PORT, that is, push it back onto the port so that | |
5393 | next read operation will work on the pushed back characters. | |
5394 | ||
5395 | ** unread-char can now be called multiple times | |
5396 | If unread-char is called multiple times, the unread characters will be | |
5397 | read again in last-in first-out order. | |
5398 | ||
9e97c52d GH |
5399 | ** the procedures uniform-array-read! and uniform-array-write! now |
5400 | work on any kind of port, not just ports which are open on a file. | |
5401 | ||
b074884f | 5402 | ** Now 'l' in a port mode requests line buffering. |
9e97c52d | 5403 | |
69bc9ff3 GH |
5404 | ** The procedure truncate-file now works on string ports as well |
5405 | as file ports. If the size argument is omitted, the current | |
1b9c3dae | 5406 | file position is used. |
9e97c52d | 5407 | |
c94577b4 | 5408 | ** new procedure: seek PORT/FDES OFFSET WHENCE |
9e97c52d GH |
5409 | The arguments are the same as for the old fseek procedure, but it |
5410 | works on string ports as well as random-access file ports. | |
5411 | ||
5412 | ** the fseek procedure now works on string ports, since it has been | |
c94577b4 | 5413 | redefined using seek. |
9e97c52d GH |
5414 | |
5415 | ** the setvbuf procedure now uses a default size if mode is _IOFBF and | |
5416 | size is not supplied. | |
5417 | ||
5418 | ** the newline procedure no longer flushes the port if it's not | |
5419 | line-buffered: previously it did if it was the current output port. | |
5420 | ||
5421 | ** open-pipe and close-pipe are no longer primitive procedures, but | |
5422 | an emulation can be obtained using `(use-modules (ice-9 popen))'. | |
5423 | ||
5424 | ** the freopen procedure has been removed. | |
5425 | ||
5426 | ** new procedure: drain-input PORT | |
5427 | Drains PORT's read buffers (including any pushed-back characters) | |
5428 | and returns the contents as a single string. | |
5429 | ||
67ad463a | 5430 | ** New function: map-in-order PROC LIST1 LIST2 ... |
d41b3904 MD |
5431 | Version of `map' which guarantees that the procedure is applied to the |
5432 | lists in serial order. | |
5433 | ||
67ad463a MD |
5434 | ** Renamed `serial-array-copy!' and `serial-array-map!' to |
5435 | `array-copy-in-order!' and `array-map-in-order!'. The old names are | |
5436 | now obsolete and will go away in release 1.5. | |
5437 | ||
cf7132b3 | 5438 | ** New syntax: collect BODY1 ... |
d41b3904 MD |
5439 | Version of `begin' which returns a list of the results of the body |
5440 | forms instead of the result of the last body form. In contrast to | |
cf7132b3 | 5441 | `begin', `collect' allows an empty body. |
d41b3904 | 5442 | |
e4eae9b1 MD |
5443 | ** New functions: read-history FILENAME, write-history FILENAME |
5444 | Read/write command line history from/to file. Returns #t on success | |
5445 | and #f if an error occured. | |
5446 | ||
d21ffe26 JB |
5447 | ** `ls' and `lls' in module (ice-9 ls) now handle no arguments. |
5448 | ||
5449 | These procedures return a list of definitions available in the specified | |
5450 | argument, a relative module reference. In the case of no argument, | |
5451 | `(current-module)' is now consulted for definitions to return, instead | |
5452 | of simply returning #f, the former behavior. | |
5453 | ||
f8c9d497 JB |
5454 | ** The #/ syntax for lists is no longer supported. |
5455 | ||
5456 | Earlier versions of Scheme accepted this syntax, but printed a | |
5457 | warning. | |
5458 | ||
5459 | ** Guile no longer consults the SCHEME_LOAD_PATH environment variable. | |
5460 | ||
5461 | Instead, you should set GUILE_LOAD_PATH to tell Guile where to find | |
5462 | modules. | |
5463 | ||
3ffc7a36 MD |
5464 | * Changes to the gh_ interface |
5465 | ||
5466 | ** gh_scm2doubles | |
5467 | ||
5468 | Now takes a second argument which is the result array. If this | |
5469 | pointer is NULL, a new array is malloced (the old behaviour). | |
5470 | ||
5471 | ** gh_chars2byvect, gh_shorts2svect, gh_floats2fvect, gh_scm2chars, | |
5472 | gh_scm2shorts, gh_scm2longs, gh_scm2floats | |
5473 | ||
5474 | New functions. | |
5475 | ||
3e8370c3 MD |
5476 | * Changes to the scm_ interface |
5477 | ||
ad91d6c3 MD |
5478 | ** Function: scm_make_named_hook (char* name, int n_args) |
5479 | ||
5480 | Creates a hook in the same way as make-hook above but also | |
5481 | binds a variable named NAME to it. | |
5482 | ||
5483 | This is the typical way of creating a hook from C code. | |
5484 | ||
ece41168 MD |
5485 | Currently, the variable is created in the "current" module. This |
5486 | might change when we get the new module system. | |
ad91d6c3 | 5487 | |
16a5a9a4 MD |
5488 | ** The smob interface |
5489 | ||
5490 | The interface for creating smobs has changed. For documentation, see | |
5491 | data-rep.info (made from guile-core/doc/data-rep.texi). | |
5492 | ||
5493 | *** Deprecated function: SCM scm_newsmob (scm_smobfuns *) | |
5494 | ||
5495 | >>> This function will be removed in 1.3.4. <<< | |
5496 | ||
5497 | It is replaced by: | |
5498 | ||
5499 | *** Function: SCM scm_make_smob_type (const char *name, scm_sizet size) | |
5500 | This function adds a new smob type, named NAME, with instance size | |
5501 | SIZE to the system. The return value is a tag that is used in | |
5502 | creating instances of the type. If SIZE is 0, then no memory will | |
5503 | be allocated when instances of the smob are created, and nothing | |
5504 | will be freed by the default free function. | |
6c0201ad | 5505 | |
16a5a9a4 MD |
5506 | *** Function: void scm_set_smob_mark (long tc, SCM (*mark) (SCM)) |
5507 | This function sets the smob marking procedure for the smob type | |
5508 | specified by the tag TC. TC is the tag returned by | |
5509 | `scm_make_smob_type'. | |
5510 | ||
5511 | *** Function: void scm_set_smob_free (long tc, SCM (*mark) (SCM)) | |
5512 | This function sets the smob freeing procedure for the smob type | |
5513 | specified by the tag TC. TC is the tag returned by | |
5514 | `scm_make_smob_type'. | |
5515 | ||
5516 | *** Function: void scm_set_smob_print (tc, print) | |
5517 | ||
5518 | - Function: void scm_set_smob_print (long tc, | |
5519 | scm_sizet (*print) (SCM, | |
5520 | SCM, | |
5521 | scm_print_state *)) | |
5522 | ||
5523 | This function sets the smob printing procedure for the smob type | |
5524 | specified by the tag TC. TC is the tag returned by | |
5525 | `scm_make_smob_type'. | |
5526 | ||
5527 | *** Function: void scm_set_smob_equalp (long tc, SCM (*equalp) (SCM, SCM)) | |
5528 | This function sets the smob equality-testing predicate for the | |
5529 | smob type specified by the tag TC. TC is the tag returned by | |
5530 | `scm_make_smob_type'. | |
5531 | ||
5532 | *** Macro: void SCM_NEWSMOB (SCM var, long tc, void *data) | |
5533 | Make VALUE contain a smob instance of the type with type code TC and | |
5534 | smob data DATA. VALUE must be previously declared as C type `SCM'. | |
5535 | ||
5536 | *** Macro: fn_returns SCM_RETURN_NEWSMOB (long tc, void *data) | |
5537 | This macro expands to a block of code that creates a smob instance | |
5538 | of the type with type code TC and smob data DATA, and returns that | |
5539 | `SCM' value. It should be the last piece of code in a block. | |
5540 | ||
9e97c52d GH |
5541 | ** The interfaces for using I/O ports and implementing port types |
5542 | (ptobs) have changed significantly. The new interface is based on | |
5543 | shared access to buffers and a new set of ptob procedures. | |
5544 | ||
16a5a9a4 MD |
5545 | *** scm_newptob has been removed |
5546 | ||
5547 | It is replaced by: | |
5548 | ||
5549 | *** Function: SCM scm_make_port_type (type_name, fill_buffer, write_flush) | |
5550 | ||
5551 | - Function: SCM scm_make_port_type (char *type_name, | |
5552 | int (*fill_buffer) (SCM port), | |
5553 | void (*write_flush) (SCM port)); | |
5554 | ||
5555 | Similarly to the new smob interface, there is a set of function | |
5556 | setters by which the user can customize the behaviour of his port | |
544e9093 | 5557 | type. See ports.h (scm_set_port_XXX). |
16a5a9a4 | 5558 | |
9e97c52d GH |
5559 | ** scm_strport_to_string: New function: creates a new string from |
5560 | a string port's buffer. | |
5561 | ||
3e8370c3 MD |
5562 | ** Plug in interface for random number generators |
5563 | The variable `scm_the_rng' in random.c contains a value and three | |
5564 | function pointers which together define the current random number | |
5565 | generator being used by the Scheme level interface and the random | |
5566 | number library functions. | |
5567 | ||
5568 | The user is free to replace the default generator with the generator | |
5569 | of his own choice. | |
5570 | ||
5571 | *** Variable: size_t scm_the_rng.rstate_size | |
5572 | The size of the random state type used by the current RNG | |
5573 | measured in chars. | |
5574 | ||
5575 | *** Function: unsigned long scm_the_rng.random_bits (scm_rstate *STATE) | |
5576 | Given the random STATE, return 32 random bits. | |
5577 | ||
5578 | *** Function: void scm_the_rng.init_rstate (scm_rstate *STATE, chars *S, int N) | |
5579 | Seed random state STATE using string S of length N. | |
5580 | ||
5581 | *** Function: scm_rstate *scm_the_rng.copy_rstate (scm_rstate *STATE) | |
5582 | Given random state STATE, return a malloced copy. | |
5583 | ||
5584 | ** Default RNG | |
5585 | The default RNG is the MWC (Multiply With Carry) random number | |
5586 | generator described by George Marsaglia at the Department of | |
5587 | Statistics and Supercomputer Computations Research Institute, The | |
5588 | Florida State University (http://stat.fsu.edu/~geo). | |
5589 | ||
5590 | It uses 64 bits, has a period of 4578426017172946943 (4.6e18), and | |
5591 | passes all tests in the DIEHARD test suite | |
5592 | (http://stat.fsu.edu/~geo/diehard.html). The generation of 32 bits | |
5593 | costs one multiply and one add on platforms which either supports long | |
5594 | longs (gcc does this on most systems) or have 64 bit longs. The cost | |
5595 | is four multiply on other systems but this can be optimized by writing | |
5596 | scm_i_uniform32 in assembler. | |
5597 | ||
5598 | These functions are provided through the scm_the_rng interface for use | |
5599 | by libguile and the application. | |
5600 | ||
5601 | *** Function: unsigned long scm_i_uniform32 (scm_i_rstate *STATE) | |
5602 | Given the random STATE, return 32 random bits. | |
5603 | Don't use this function directly. Instead go through the plugin | |
5604 | interface (see "Plug in interface" above). | |
5605 | ||
5606 | *** Function: void scm_i_init_rstate (scm_i_rstate *STATE, char *SEED, int N) | |
5607 | Initialize STATE using SEED of length N. | |
5608 | ||
5609 | *** Function: scm_i_rstate *scm_i_copy_rstate (scm_i_rstate *STATE) | |
5610 | Return a malloc:ed copy of STATE. This function can easily be re-used | |
5611 | in the interfaces to other RNGs. | |
5612 | ||
5613 | ** Random number library functions | |
5614 | These functions use the current RNG through the scm_the_rng interface. | |
5615 | It might be a good idea to use these functions from your C code so | |
5616 | that only one random generator is used by all code in your program. | |
5617 | ||
259529f2 | 5618 | The default random state is stored in: |
3e8370c3 MD |
5619 | |
5620 | *** Variable: SCM scm_var_random_state | |
5621 | Contains the vcell of the Scheme variable "*random-state*" which is | |
5622 | used as default state by all random number functions in the Scheme | |
5623 | level interface. | |
5624 | ||
5625 | Example: | |
5626 | ||
259529f2 | 5627 | double x = scm_c_uniform01 (SCM_RSTATE (SCM_CDR (scm_var_random_state))); |
3e8370c3 | 5628 | |
259529f2 MD |
5629 | *** Function: scm_rstate *scm_c_default_rstate (void) |
5630 | This is a convenience function which returns the value of | |
5631 | scm_var_random_state. An error message is generated if this value | |
5632 | isn't a random state. | |
5633 | ||
5634 | *** Function: scm_rstate *scm_c_make_rstate (char *SEED, int LENGTH) | |
5635 | Make a new random state from the string SEED of length LENGTH. | |
5636 | ||
5637 | It is generally not a good idea to use multiple random states in a | |
5638 | program. While subsequent random numbers generated from one random | |
5639 | state are guaranteed to be reasonably independent, there is no such | |
5640 | guarantee for numbers generated from different random states. | |
5641 | ||
5642 | *** Macro: unsigned long scm_c_uniform32 (scm_rstate *STATE) | |
5643 | Return 32 random bits. | |
5644 | ||
5645 | *** Function: double scm_c_uniform01 (scm_rstate *STATE) | |
3e8370c3 MD |
5646 | Return a sample from the uniform(0,1) distribution. |
5647 | ||
259529f2 | 5648 | *** Function: double scm_c_normal01 (scm_rstate *STATE) |
3e8370c3 MD |
5649 | Return a sample from the normal(0,1) distribution. |
5650 | ||
259529f2 | 5651 | *** Function: double scm_c_exp1 (scm_rstate *STATE) |
3e8370c3 MD |
5652 | Return a sample from the exp(1) distribution. |
5653 | ||
259529f2 MD |
5654 | *** Function: unsigned long scm_c_random (scm_rstate *STATE, unsigned long M) |
5655 | Return a sample from the discrete uniform(0,M) distribution. | |
5656 | ||
5657 | *** Function: SCM scm_c_random_bignum (scm_rstate *STATE, SCM M) | |
3e8370c3 | 5658 | Return a sample from the discrete uniform(0,M) distribution. |
259529f2 | 5659 | M must be a bignum object. The returned value may be an INUM. |
3e8370c3 | 5660 | |
9e97c52d | 5661 | |
f3227c7a | 5662 | \f |
d23bbf3e | 5663 | Changes in Guile 1.3 (released Monday, October 19, 1998): |
c484bf7f JB |
5664 | |
5665 | * Changes to the distribution | |
5666 | ||
e2d6569c JB |
5667 | ** We renamed the SCHEME_LOAD_PATH environment variable to GUILE_LOAD_PATH. |
5668 | To avoid conflicts, programs should name environment variables after | |
5669 | themselves, except when there's a common practice establishing some | |
5670 | other convention. | |
5671 | ||
5672 | For now, Guile supports both GUILE_LOAD_PATH and SCHEME_LOAD_PATH, | |
5673 | giving the former precedence, and printing a warning message if the | |
5674 | latter is set. Guile 1.4 will not recognize SCHEME_LOAD_PATH at all. | |
5675 | ||
5676 | ** The header files related to multi-byte characters have been removed. | |
5677 | They were: libguile/extchrs.h and libguile/mbstrings.h. Any C code | |
5678 | which referred to these explicitly will probably need to be rewritten, | |
5679 | since the support for the variant string types has been removed; see | |
5680 | below. | |
5681 | ||
5682 | ** The header files append.h and sequences.h have been removed. These | |
5683 | files implemented non-R4RS operations which would encourage | |
5684 | non-portable programming style and less easy-to-read code. | |
3a97e020 | 5685 | |
c484bf7f JB |
5686 | * Changes to the stand-alone interpreter |
5687 | ||
2e368582 | 5688 | ** New procedures have been added to implement a "batch mode": |
ec4ab4fd | 5689 | |
2e368582 | 5690 | *** Function: batch-mode? |
ec4ab4fd GH |
5691 | |
5692 | Returns a boolean indicating whether the interpreter is in batch | |
5693 | mode. | |
5694 | ||
2e368582 | 5695 | *** Function: set-batch-mode?! ARG |
ec4ab4fd GH |
5696 | |
5697 | If ARG is true, switches the interpreter to batch mode. The `#f' | |
5698 | case has not been implemented. | |
5699 | ||
2e368582 JB |
5700 | ** Guile now provides full command-line editing, when run interactively. |
5701 | To use this feature, you must have the readline library installed. | |
5702 | The Guile build process will notice it, and automatically include | |
5703 | support for it. | |
5704 | ||
5705 | The readline library is available via anonymous FTP from any GNU | |
5706 | mirror site; the canonical location is "ftp://prep.ai.mit.edu/pub/gnu". | |
5707 | ||
a5d6d578 MD |
5708 | ** the-last-stack is now a fluid. |
5709 | ||
c484bf7f JB |
5710 | * Changes to the procedure for linking libguile with your programs |
5711 | ||
71f20534 | 5712 | ** You can now use the `guile-config' utility to build programs that use Guile. |
2e368582 | 5713 | |
2adfe1c0 | 5714 | Guile now includes a command-line utility called `guile-config', which |
71f20534 JB |
5715 | can provide information about how to compile and link programs that |
5716 | use Guile. | |
5717 | ||
5718 | *** `guile-config compile' prints any C compiler flags needed to use Guile. | |
5719 | You should include this command's output on the command line you use | |
5720 | to compile C or C++ code that #includes the Guile header files. It's | |
5721 | usually just a `-I' flag to help the compiler find the Guile headers. | |
5722 | ||
5723 | ||
5724 | *** `guile-config link' prints any linker flags necessary to link with Guile. | |
8aa5c148 | 5725 | |
71f20534 | 5726 | This command writes to its standard output a list of flags which you |
8aa5c148 JB |
5727 | must pass to the linker to link your code against the Guile library. |
5728 | The flags include '-lguile' itself, any other libraries the Guile | |
5729 | library depends upon, and any `-L' flags needed to help the linker | |
5730 | find those libraries. | |
2e368582 JB |
5731 | |
5732 | For example, here is a Makefile rule that builds a program named 'foo' | |
5733 | from the object files ${FOO_OBJECTS}, and links them against Guile: | |
5734 | ||
5735 | foo: ${FOO_OBJECTS} | |
2adfe1c0 | 5736 | ${CC} ${CFLAGS} ${FOO_OBJECTS} `guile-config link` -o foo |
2e368582 | 5737 | |
e2d6569c JB |
5738 | Previous Guile releases recommended that you use autoconf to detect |
5739 | which of a predefined set of libraries were present on your system. | |
2adfe1c0 | 5740 | It is more robust to use `guile-config', since it records exactly which |
e2d6569c JB |
5741 | libraries the installed Guile library requires. |
5742 | ||
2adfe1c0 JB |
5743 | This was originally called `build-guile', but was renamed to |
5744 | `guile-config' before Guile 1.3 was released, to be consistent with | |
5745 | the analogous script for the GTK+ GUI toolkit, which is called | |
5746 | `gtk-config'. | |
5747 | ||
2e368582 | 5748 | |
8aa5c148 JB |
5749 | ** Use the GUILE_FLAGS macro in your configure.in file to find Guile. |
5750 | ||
5751 | If you are using the GNU autoconf package to configure your program, | |
5752 | you can use the GUILE_FLAGS autoconf macro to call `guile-config' | |
5753 | (described above) and gather the necessary values for use in your | |
5754 | Makefiles. | |
5755 | ||
5756 | The GUILE_FLAGS macro expands to configure script code which runs the | |
5757 | `guile-config' script, to find out where Guile's header files and | |
5758 | libraries are installed. It sets two variables, marked for | |
5759 | substitution, as by AC_SUBST. | |
5760 | ||
5761 | GUILE_CFLAGS --- flags to pass to a C or C++ compiler to build | |
5762 | code that uses Guile header files. This is almost always just a | |
5763 | -I flag. | |
5764 | ||
5765 | GUILE_LDFLAGS --- flags to pass to the linker to link a | |
5766 | program against Guile. This includes `-lguile' for the Guile | |
5767 | library itself, any libraries that Guile itself requires (like | |
5768 | -lqthreads), and so on. It may also include a -L flag to tell the | |
5769 | compiler where to find the libraries. | |
5770 | ||
5771 | GUILE_FLAGS is defined in the file guile.m4, in the top-level | |
5772 | directory of the Guile distribution. You can copy it into your | |
5773 | package's aclocal.m4 file, and then use it in your configure.in file. | |
5774 | ||
5775 | If you are using the `aclocal' program, distributed with GNU automake, | |
5776 | to maintain your aclocal.m4 file, the Guile installation process | |
5777 | installs guile.m4 where aclocal will find it. All you need to do is | |
5778 | use GUILE_FLAGS in your configure.in file, and then run `aclocal'; | |
5779 | this will copy the definition of GUILE_FLAGS into your aclocal.m4 | |
5780 | file. | |
5781 | ||
5782 | ||
c484bf7f | 5783 | * Changes to Scheme functions and syntax |
7ad3c1e7 | 5784 | |
02755d59 | 5785 | ** Multi-byte strings have been removed, as have multi-byte and wide |
e2d6569c JB |
5786 | ports. We felt that these were the wrong approach to |
5787 | internationalization support. | |
02755d59 | 5788 | |
2e368582 JB |
5789 | ** New function: readline [PROMPT] |
5790 | Read a line from the terminal, and allow the user to edit it, | |
5791 | prompting with PROMPT. READLINE provides a large set of Emacs-like | |
5792 | editing commands, lets the user recall previously typed lines, and | |
5793 | works on almost every kind of terminal, including dumb terminals. | |
5794 | ||
5795 | READLINE assumes that the cursor is at the beginning of the line when | |
5796 | it is invoked. Thus, you can't print a prompt yourself, and then call | |
5797 | READLINE; you need to package up your prompt as a string, pass it to | |
5798 | the function, and let READLINE print the prompt itself. This is | |
5799 | because READLINE needs to know the prompt's screen width. | |
5800 | ||
8cd57bd0 JB |
5801 | For Guile to provide this function, you must have the readline |
5802 | library, version 2.1 or later, installed on your system. Readline is | |
5803 | available via anonymous FTP from prep.ai.mit.edu in pub/gnu, or from | |
5804 | any GNU mirror site. | |
2e368582 JB |
5805 | |
5806 | See also ADD-HISTORY function. | |
5807 | ||
5808 | ** New function: add-history STRING | |
5809 | Add STRING as the most recent line in the history used by the READLINE | |
5810 | command. READLINE does not add lines to the history itself; you must | |
5811 | call ADD-HISTORY to make previous input available to the user. | |
5812 | ||
8cd57bd0 JB |
5813 | ** The behavior of the read-line function has changed. |
5814 | ||
5815 | This function now uses standard C library functions to read the line, | |
5816 | for speed. This means that it doesn not respect the value of | |
5817 | scm-line-incrementors; it assumes that lines are delimited with | |
5818 | #\newline. | |
5819 | ||
5820 | (Note that this is read-line, the function that reads a line of text | |
5821 | from a port, not readline, the function that reads a line from a | |
5822 | terminal, providing full editing capabilities.) | |
5823 | ||
1a0106ef JB |
5824 | ** New module (ice-9 getopt-gnu-style): Parse command-line arguments. |
5825 | ||
5826 | This module provides some simple argument parsing. It exports one | |
5827 | function: | |
5828 | ||
5829 | Function: getopt-gnu-style ARG-LS | |
5830 | Parse a list of program arguments into an alist of option | |
5831 | descriptions. | |
5832 | ||
5833 | Each item in the list of program arguments is examined to see if | |
5834 | it meets the syntax of a GNU long-named option. An argument like | |
5835 | `--MUMBLE' produces an element of the form (MUMBLE . #t) in the | |
5836 | returned alist, where MUMBLE is a keyword object with the same | |
5837 | name as the argument. An argument like `--MUMBLE=FROB' produces | |
5838 | an element of the form (MUMBLE . FROB), where FROB is a string. | |
5839 | ||
5840 | As a special case, the returned alist also contains a pair whose | |
5841 | car is the symbol `rest'. The cdr of this pair is a list | |
5842 | containing all the items in the argument list that are not options | |
5843 | of the form mentioned above. | |
5844 | ||
5845 | The argument `--' is treated specially: all items in the argument | |
5846 | list appearing after such an argument are not examined, and are | |
5847 | returned in the special `rest' list. | |
5848 | ||
5849 | This function does not parse normal single-character switches. | |
5850 | You will need to parse them out of the `rest' list yourself. | |
5851 | ||
8cd57bd0 JB |
5852 | ** The read syntax for byte vectors and short vectors has changed. |
5853 | ||
5854 | Instead of #bytes(...), write #y(...). | |
5855 | ||
5856 | Instead of #short(...), write #h(...). | |
5857 | ||
5858 | This may seem nutty, but, like the other uniform vectors, byte vectors | |
5859 | and short vectors want to have the same print and read syntax (and, | |
5860 | more basic, want to have read syntax!). Changing the read syntax to | |
5861 | use multiple characters after the hash sign breaks with the | |
5862 | conventions used in R5RS and the conventions used for the other | |
5863 | uniform vectors. It also introduces complexity in the current reader, | |
5864 | both on the C and Scheme levels. (The Right solution is probably to | |
5865 | change the syntax and prototypes for uniform vectors entirely.) | |
5866 | ||
5867 | ||
5868 | ** The new module (ice-9 session) provides useful interactive functions. | |
5869 | ||
5870 | *** New procedure: (apropos REGEXP OPTION ...) | |
5871 | ||
5872 | Display a list of top-level variables whose names match REGEXP, and | |
5873 | the modules they are imported from. Each OPTION should be one of the | |
5874 | following symbols: | |
5875 | ||
5876 | value --- Show the value of each matching variable. | |
5877 | shadow --- Show bindings shadowed by subsequently imported modules. | |
5878 | full --- Same as both `shadow' and `value'. | |
5879 | ||
5880 | For example: | |
5881 | ||
5882 | guile> (apropos "trace" 'full) | |
5883 | debug: trace #<procedure trace args> | |
5884 | debug: untrace #<procedure untrace args> | |
5885 | the-scm-module: display-backtrace #<compiled-closure #<primitive-procedure gsubr-apply>> | |
5886 | the-scm-module: before-backtrace-hook () | |
5887 | the-scm-module: backtrace #<primitive-procedure backtrace> | |
5888 | the-scm-module: after-backtrace-hook () | |
5889 | the-scm-module: has-shown-backtrace-hint? #f | |
6c0201ad | 5890 | guile> |
8cd57bd0 JB |
5891 | |
5892 | ** There are new functions and syntax for working with macros. | |
5893 | ||
5894 | Guile implements macros as a special object type. Any variable whose | |
5895 | top-level binding is a macro object acts as a macro. The macro object | |
5896 | specifies how the expression should be transformed before evaluation. | |
5897 | ||
5898 | *** Macro objects now print in a reasonable way, resembling procedures. | |
5899 | ||
5900 | *** New function: (macro? OBJ) | |
5901 | True iff OBJ is a macro object. | |
5902 | ||
5903 | *** New function: (primitive-macro? OBJ) | |
5904 | Like (macro? OBJ), but true only if OBJ is one of the Guile primitive | |
5905 | macro transformers, implemented in eval.c rather than Scheme code. | |
5906 | ||
dbdd0c16 JB |
5907 | Why do we have this function? |
5908 | - For symmetry with procedure? and primitive-procedure?, | |
5909 | - to allow custom print procedures to tell whether a macro is | |
5910 | primitive, and display it differently, and | |
5911 | - to allow compilers and user-written evaluators to distinguish | |
5912 | builtin special forms from user-defined ones, which could be | |
5913 | compiled. | |
5914 | ||
8cd57bd0 JB |
5915 | *** New function: (macro-type OBJ) |
5916 | Return a value indicating what kind of macro OBJ is. Possible return | |
5917 | values are: | |
5918 | ||
5919 | The symbol `syntax' --- a macro created by procedure->syntax. | |
5920 | The symbol `macro' --- a macro created by procedure->macro. | |
5921 | The symbol `macro!' --- a macro created by procedure->memoizing-macro. | |
6c0201ad | 5922 | The boolean #f --- if OBJ is not a macro object. |
8cd57bd0 JB |
5923 | |
5924 | *** New function: (macro-name MACRO) | |
5925 | Return the name of the macro object MACRO's procedure, as returned by | |
5926 | procedure-name. | |
5927 | ||
5928 | *** New function: (macro-transformer MACRO) | |
5929 | Return the transformer procedure for MACRO. | |
5930 | ||
5931 | *** New syntax: (use-syntax MODULE ... TRANSFORMER) | |
5932 | ||
5933 | Specify a new macro expander to use in the current module. Each | |
5934 | MODULE is a module name, with the same meaning as in the `use-modules' | |
5935 | form; each named module's exported bindings are added to the current | |
5936 | top-level environment. TRANSFORMER is an expression evaluated in the | |
5937 | resulting environment which must yield a procedure to use as the | |
5938 | module's eval transformer: every expression evaluated in this module | |
5939 | is passed to this function, and the result passed to the Guile | |
6c0201ad | 5940 | interpreter. |
8cd57bd0 JB |
5941 | |
5942 | *** macro-eval! is removed. Use local-eval instead. | |
29521173 | 5943 | |
8d9dcb3c MV |
5944 | ** Some magic has been added to the printer to better handle user |
5945 | written printing routines (like record printers, closure printers). | |
5946 | ||
5947 | The problem is that these user written routines must have access to | |
7fbd77df | 5948 | the current `print-state' to be able to handle fancy things like |
8d9dcb3c MV |
5949 | detection of circular references. These print-states have to be |
5950 | passed to the builtin printing routines (display, write, etc) to | |
5951 | properly continue the print chain. | |
5952 | ||
5953 | We didn't want to change all existing print code so that it | |
8cd57bd0 | 5954 | explicitly passes thru a print state in addition to a port. Instead, |
8d9dcb3c MV |
5955 | we extented the possible values that the builtin printing routines |
5956 | accept as a `port'. In addition to a normal port, they now also take | |
5957 | a pair of a normal port and a print-state. Printing will go to the | |
5958 | port and the print-state will be used to control the detection of | |
5959 | circular references, etc. If the builtin function does not care for a | |
5960 | print-state, it is simply ignored. | |
5961 | ||
5962 | User written callbacks are now called with such a pair as their | |
5963 | `port', but because every function now accepts this pair as a PORT | |
5964 | argument, you don't have to worry about that. In fact, it is probably | |
5965 | safest to not check for these pairs. | |
5966 | ||
5967 | However, it is sometimes necessary to continue a print chain on a | |
5968 | different port, for example to get a intermediate string | |
5969 | representation of the printed value, mangle that string somehow, and | |
5970 | then to finally print the mangled string. Use the new function | |
5971 | ||
5972 | inherit-print-state OLD-PORT NEW-PORT | |
5973 | ||
5974 | for this. It constructs a new `port' that prints to NEW-PORT but | |
5975 | inherits the print-state of OLD-PORT. | |
5976 | ||
ef1ea498 MD |
5977 | ** struct-vtable-offset renamed to vtable-offset-user |
5978 | ||
5979 | ** New constants: vtable-index-layout, vtable-index-vtable, vtable-index-printer | |
5980 | ||
e478dffa MD |
5981 | ** There is now a third optional argument to make-vtable-vtable |
5982 | (and fourth to make-struct) when constructing new types (vtables). | |
5983 | This argument initializes field vtable-index-printer of the vtable. | |
ef1ea498 | 5984 | |
4851dc57 MV |
5985 | ** The detection of circular references has been extended to structs. |
5986 | That is, a structure that -- in the process of being printed -- prints | |
5987 | itself does not lead to infinite recursion. | |
5988 | ||
5989 | ** There is now some basic support for fluids. Please read | |
5990 | "libguile/fluid.h" to find out more. It is accessible from Scheme with | |
5991 | the following functions and macros: | |
5992 | ||
9c3fb66f MV |
5993 | Function: make-fluid |
5994 | ||
5995 | Create a new fluid object. Fluids are not special variables or | |
5996 | some other extension to the semantics of Scheme, but rather | |
5997 | ordinary Scheme objects. You can store them into variables (that | |
5998 | are still lexically scoped, of course) or into any other place you | |
5999 | like. Every fluid has a initial value of `#f'. | |
04c76b58 | 6000 | |
9c3fb66f | 6001 | Function: fluid? OBJ |
04c76b58 | 6002 | |
9c3fb66f | 6003 | Test whether OBJ is a fluid. |
04c76b58 | 6004 | |
9c3fb66f MV |
6005 | Function: fluid-ref FLUID |
6006 | Function: fluid-set! FLUID VAL | |
04c76b58 MV |
6007 | |
6008 | Access/modify the fluid FLUID. Modifications are only visible | |
6009 | within the current dynamic root (that includes threads). | |
6010 | ||
9c3fb66f MV |
6011 | Function: with-fluids* FLUIDS VALUES THUNK |
6012 | ||
6013 | FLUIDS is a list of fluids and VALUES a corresponding list of | |
6014 | values for these fluids. Before THUNK gets called the values are | |
6c0201ad | 6015 | installed in the fluids and the old values of the fluids are |
9c3fb66f MV |
6016 | saved in the VALUES list. When the flow of control leaves THUNK |
6017 | or reenters it, the values get swapped again. You might think of | |
6018 | this as a `safe-fluid-excursion'. Note that the VALUES list is | |
6019 | modified by `with-fluids*'. | |
6020 | ||
6021 | Macro: with-fluids ((FLUID VALUE) ...) FORM ... | |
6022 | ||
6023 | The same as `with-fluids*' but with a different syntax. It looks | |
6024 | just like `let', but both FLUID and VALUE are evaluated. Remember, | |
6025 | fluids are not special variables but ordinary objects. FLUID | |
6026 | should evaluate to a fluid. | |
04c76b58 | 6027 | |
e2d6569c | 6028 | ** Changes to system call interfaces: |
64d01d13 | 6029 | |
e2d6569c | 6030 | *** close-port, close-input-port and close-output-port now return a |
64d01d13 GH |
6031 | boolean instead of an `unspecified' object. #t means that the port |
6032 | was successfully closed, while #f means it was already closed. It is | |
6033 | also now possible for these procedures to raise an exception if an | |
6034 | error occurs (some errors from write can be delayed until close.) | |
6035 | ||
e2d6569c | 6036 | *** the first argument to chmod, fcntl, ftell and fseek can now be a |
6afcd3b2 GH |
6037 | file descriptor. |
6038 | ||
e2d6569c | 6039 | *** the third argument to fcntl is now optional. |
6afcd3b2 | 6040 | |
e2d6569c | 6041 | *** the first argument to chown can now be a file descriptor or a port. |
6afcd3b2 | 6042 | |
e2d6569c | 6043 | *** the argument to stat can now be a port. |
6afcd3b2 | 6044 | |
e2d6569c | 6045 | *** The following new procedures have been added (most use scsh |
64d01d13 GH |
6046 | interfaces): |
6047 | ||
e2d6569c | 6048 | *** procedure: close PORT/FD |
ec4ab4fd GH |
6049 | Similar to close-port (*note close-port: Closing Ports.), but also |
6050 | works on file descriptors. A side effect of closing a file | |
6051 | descriptor is that any ports using that file descriptor are moved | |
6052 | to a different file descriptor and have their revealed counts set | |
6053 | to zero. | |
6054 | ||
e2d6569c | 6055 | *** procedure: port->fdes PORT |
ec4ab4fd GH |
6056 | Returns the integer file descriptor underlying PORT. As a side |
6057 | effect the revealed count of PORT is incremented. | |
6058 | ||
e2d6569c | 6059 | *** procedure: fdes->ports FDES |
ec4ab4fd GH |
6060 | Returns a list of existing ports which have FDES as an underlying |
6061 | file descriptor, without changing their revealed counts. | |
6062 | ||
e2d6569c | 6063 | *** procedure: fdes->inport FDES |
ec4ab4fd GH |
6064 | Returns an existing input port which has FDES as its underlying |
6065 | file descriptor, if one exists, and increments its revealed count. | |
6066 | Otherwise, returns a new input port with a revealed count of 1. | |
6067 | ||
e2d6569c | 6068 | *** procedure: fdes->outport FDES |
ec4ab4fd GH |
6069 | Returns an existing output port which has FDES as its underlying |
6070 | file descriptor, if one exists, and increments its revealed count. | |
6071 | Otherwise, returns a new output port with a revealed count of 1. | |
6072 | ||
6073 | The next group of procedures perform a `dup2' system call, if NEWFD | |
6074 | (an integer) is supplied, otherwise a `dup'. The file descriptor to be | |
6075 | duplicated can be supplied as an integer or contained in a port. The | |
64d01d13 GH |
6076 | type of value returned varies depending on which procedure is used. |
6077 | ||
ec4ab4fd GH |
6078 | All procedures also have the side effect when performing `dup2' that |
6079 | any ports using NEWFD are moved to a different file descriptor and have | |
64d01d13 GH |
6080 | their revealed counts set to zero. |
6081 | ||
e2d6569c | 6082 | *** procedure: dup->fdes PORT/FD [NEWFD] |
ec4ab4fd | 6083 | Returns an integer file descriptor. |
64d01d13 | 6084 | |
e2d6569c | 6085 | *** procedure: dup->inport PORT/FD [NEWFD] |
ec4ab4fd | 6086 | Returns a new input port using the new file descriptor. |
64d01d13 | 6087 | |
e2d6569c | 6088 | *** procedure: dup->outport PORT/FD [NEWFD] |
ec4ab4fd | 6089 | Returns a new output port using the new file descriptor. |
64d01d13 | 6090 | |
e2d6569c | 6091 | *** procedure: dup PORT/FD [NEWFD] |
ec4ab4fd GH |
6092 | Returns a new port if PORT/FD is a port, with the same mode as the |
6093 | supplied port, otherwise returns an integer file descriptor. | |
64d01d13 | 6094 | |
e2d6569c | 6095 | *** procedure: dup->port PORT/FD MODE [NEWFD] |
ec4ab4fd GH |
6096 | Returns a new port using the new file descriptor. MODE supplies a |
6097 | mode string for the port (*note open-file: File Ports.). | |
64d01d13 | 6098 | |
e2d6569c | 6099 | *** procedure: setenv NAME VALUE |
ec4ab4fd GH |
6100 | Modifies the environment of the current process, which is also the |
6101 | default environment inherited by child processes. | |
64d01d13 | 6102 | |
ec4ab4fd GH |
6103 | If VALUE is `#f', then NAME is removed from the environment. |
6104 | Otherwise, the string NAME=VALUE is added to the environment, | |
6105 | replacing any existing string with name matching NAME. | |
64d01d13 | 6106 | |
ec4ab4fd | 6107 | The return value is unspecified. |
956055a9 | 6108 | |
e2d6569c | 6109 | *** procedure: truncate-file OBJ SIZE |
6afcd3b2 GH |
6110 | Truncates the file referred to by OBJ to at most SIZE bytes. OBJ |
6111 | can be a string containing a file name or an integer file | |
6112 | descriptor or port open for output on the file. The underlying | |
6113 | system calls are `truncate' and `ftruncate'. | |
6114 | ||
6115 | The return value is unspecified. | |
6116 | ||
e2d6569c | 6117 | *** procedure: setvbuf PORT MODE [SIZE] |
7a6f1ffa GH |
6118 | Set the buffering mode for PORT. MODE can be: |
6119 | `_IONBF' | |
6120 | non-buffered | |
6121 | ||
6122 | `_IOLBF' | |
6123 | line buffered | |
6124 | ||
6125 | `_IOFBF' | |
6126 | block buffered, using a newly allocated buffer of SIZE bytes. | |
6127 | However if SIZE is zero or unspecified, the port will be made | |
6128 | non-buffered. | |
6129 | ||
6130 | This procedure should not be used after I/O has been performed with | |
6131 | the port. | |
6132 | ||
6133 | Ports are usually block buffered by default, with a default buffer | |
6134 | size. Procedures e.g., *Note open-file: File Ports, which accept a | |
6135 | mode string allow `0' to be added to request an unbuffered port. | |
6136 | ||
e2d6569c | 6137 | *** procedure: fsync PORT/FD |
6afcd3b2 GH |
6138 | Copies any unwritten data for the specified output file descriptor |
6139 | to disk. If PORT/FD is a port, its buffer is flushed before the | |
6140 | underlying file descriptor is fsync'd. The return value is | |
6141 | unspecified. | |
6142 | ||
e2d6569c | 6143 | *** procedure: open-fdes PATH FLAGS [MODES] |
6afcd3b2 GH |
6144 | Similar to `open' but returns a file descriptor instead of a port. |
6145 | ||
e2d6569c | 6146 | *** procedure: execle PATH ENV [ARG] ... |
6afcd3b2 GH |
6147 | Similar to `execl', but the environment of the new process is |
6148 | specified by ENV, which must be a list of strings as returned by | |
6149 | the `environ' procedure. | |
6150 | ||
6151 | This procedure is currently implemented using the `execve' system | |
6152 | call, but we call it `execle' because of its Scheme calling | |
6153 | interface. | |
6154 | ||
e2d6569c | 6155 | *** procedure: strerror ERRNO |
ec4ab4fd GH |
6156 | Returns the Unix error message corresponding to ERRNO, an integer. |
6157 | ||
e2d6569c | 6158 | *** procedure: primitive-exit [STATUS] |
6afcd3b2 GH |
6159 | Terminate the current process without unwinding the Scheme stack. |
6160 | This is would typically be useful after a fork. The exit status | |
6161 | is STATUS if supplied, otherwise zero. | |
6162 | ||
e2d6569c | 6163 | *** procedure: times |
6afcd3b2 GH |
6164 | Returns an object with information about real and processor time. |
6165 | The following procedures accept such an object as an argument and | |
6166 | return a selected component: | |
6167 | ||
6168 | `tms:clock' | |
6169 | The current real time, expressed as time units relative to an | |
6170 | arbitrary base. | |
6171 | ||
6172 | `tms:utime' | |
6173 | The CPU time units used by the calling process. | |
6174 | ||
6175 | `tms:stime' | |
6176 | The CPU time units used by the system on behalf of the | |
6177 | calling process. | |
6178 | ||
6179 | `tms:cutime' | |
6180 | The CPU time units used by terminated child processes of the | |
6181 | calling process, whose status has been collected (e.g., using | |
6182 | `waitpid'). | |
6183 | ||
6184 | `tms:cstime' | |
6185 | Similarly, the CPU times units used by the system on behalf of | |
6186 | terminated child processes. | |
7ad3c1e7 | 6187 | |
e2d6569c JB |
6188 | ** Removed: list-length |
6189 | ** Removed: list-append, list-append! | |
6190 | ** Removed: list-reverse, list-reverse! | |
6191 | ||
6192 | ** array-map renamed to array-map! | |
6193 | ||
6194 | ** serial-array-map renamed to serial-array-map! | |
6195 | ||
660f41fa MD |
6196 | ** catch doesn't take #f as first argument any longer |
6197 | ||
6198 | Previously, it was possible to pass #f instead of a key to `catch'. | |
6199 | That would cause `catch' to pass a jump buffer object to the procedure | |
6200 | passed as second argument. The procedure could then use this jump | |
6201 | buffer objekt as an argument to throw. | |
6202 | ||
6203 | This mechanism has been removed since its utility doesn't motivate the | |
6204 | extra complexity it introduces. | |
6205 | ||
332d00f6 JB |
6206 | ** The `#/' notation for lists now provokes a warning message from Guile. |
6207 | This syntax will be removed from Guile in the near future. | |
6208 | ||
6209 | To disable the warning message, set the GUILE_HUSH environment | |
6210 | variable to any non-empty value. | |
6211 | ||
8cd57bd0 JB |
6212 | ** The newline character now prints as `#\newline', following the |
6213 | normal Scheme notation, not `#\nl'. | |
6214 | ||
c484bf7f JB |
6215 | * Changes to the gh_ interface |
6216 | ||
8986901b JB |
6217 | ** The gh_enter function now takes care of loading the Guile startup files. |
6218 | gh_enter works by calling scm_boot_guile; see the remarks below. | |
6219 | ||
5424b4f7 MD |
6220 | ** Function: void gh_write (SCM x) |
6221 | ||
6222 | Write the printed representation of the scheme object x to the current | |
6223 | output port. Corresponds to the scheme level `write'. | |
6224 | ||
3a97e020 MD |
6225 | ** gh_list_length renamed to gh_length. |
6226 | ||
8d6787b6 MG |
6227 | ** vector handling routines |
6228 | ||
6229 | Several major changes. In particular, gh_vector() now resembles | |
6230 | (vector ...) (with a caveat -- see manual), and gh_make_vector() now | |
956328d2 MG |
6231 | exists and behaves like (make-vector ...). gh_vset() and gh_vref() |
6232 | have been renamed gh_vector_set_x() and gh_vector_ref(). Some missing | |
8d6787b6 MG |
6233 | vector-related gh_ functions have been implemented. |
6234 | ||
7fee59bd MG |
6235 | ** pair and list routines |
6236 | ||
6237 | Implemented several of the R4RS pair and list functions that were | |
6238 | missing. | |
6239 | ||
171422a9 MD |
6240 | ** gh_scm2doubles, gh_doubles2scm, gh_doubles2dvect |
6241 | ||
6242 | New function. Converts double arrays back and forth between Scheme | |
6243 | and C. | |
6244 | ||
c484bf7f JB |
6245 | * Changes to the scm_ interface |
6246 | ||
8986901b JB |
6247 | ** The function scm_boot_guile now takes care of loading the startup files. |
6248 | ||
6249 | Guile's primary initialization function, scm_boot_guile, now takes | |
6250 | care of loading `boot-9.scm', in the `ice-9' module, to initialize | |
6251 | Guile, define the module system, and put together some standard | |
6252 | bindings. It also loads `init.scm', which is intended to hold | |
6253 | site-specific initialization code. | |
6254 | ||
6255 | Since Guile cannot operate properly until boot-9.scm is loaded, there | |
6256 | is no reason to separate loading boot-9.scm from Guile's other | |
6257 | initialization processes. | |
6258 | ||
6259 | This job used to be done by scm_compile_shell_switches, which didn't | |
6260 | make much sense; in particular, it meant that people using Guile for | |
6261 | non-shell-like applications had to jump through hoops to get Guile | |
6262 | initialized properly. | |
6263 | ||
6264 | ** The function scm_compile_shell_switches no longer loads the startup files. | |
6265 | Now, Guile always loads the startup files, whenever it is initialized; | |
6266 | see the notes above for scm_boot_guile and scm_load_startup_files. | |
6267 | ||
6268 | ** Function: scm_load_startup_files | |
6269 | This new function takes care of loading Guile's initialization file | |
6270 | (`boot-9.scm'), and the site initialization file, `init.scm'. Since | |
6271 | this is always called by the Guile initialization process, it's | |
6272 | probably not too useful to call this yourself, but it's there anyway. | |
6273 | ||
87148d9e JB |
6274 | ** The semantics of smob marking have changed slightly. |
6275 | ||
6276 | The smob marking function (the `mark' member of the scm_smobfuns | |
6277 | structure) is no longer responsible for setting the mark bit on the | |
6278 | smob. The generic smob handling code in the garbage collector will | |
6279 | set this bit. The mark function need only ensure that any other | |
6280 | objects the smob refers to get marked. | |
6281 | ||
6282 | Note that this change means that the smob's GC8MARK bit is typically | |
6283 | already set upon entry to the mark function. Thus, marking functions | |
6284 | which look like this: | |
6285 | ||
6286 | { | |
6287 | if (SCM_GC8MARKP (ptr)) | |
6288 | return SCM_BOOL_F; | |
6289 | SCM_SETGC8MARK (ptr); | |
6290 | ... mark objects to which the smob refers ... | |
6291 | } | |
6292 | ||
6293 | are now incorrect, since they will return early, and fail to mark any | |
6294 | other objects the smob refers to. Some code in the Guile library used | |
6295 | to work this way. | |
6296 | ||
1cf84ea5 JB |
6297 | ** The semantics of the I/O port functions in scm_ptobfuns have changed. |
6298 | ||
6299 | If you have implemented your own I/O port type, by writing the | |
6300 | functions required by the scm_ptobfuns and then calling scm_newptob, | |
6301 | you will need to change your functions slightly. | |
6302 | ||
6303 | The functions in a scm_ptobfuns structure now expect the port itself | |
6304 | as their argument; they used to expect the `stream' member of the | |
6305 | port's scm_port_table structure. This allows functions in an | |
6306 | scm_ptobfuns structure to easily access the port's cell (and any flags | |
6307 | it its CAR), and the port's scm_port_table structure. | |
6308 | ||
6309 | Guile now passes the I/O port itself as the `port' argument in the | |
6310 | following scm_ptobfuns functions: | |
6311 | ||
6312 | int (*free) (SCM port); | |
6313 | int (*fputc) (int, SCM port); | |
6314 | int (*fputs) (char *, SCM port); | |
6315 | scm_sizet (*fwrite) SCM_P ((char *ptr, | |
6316 | scm_sizet size, | |
6317 | scm_sizet nitems, | |
6318 | SCM port)); | |
6319 | int (*fflush) (SCM port); | |
6320 | int (*fgetc) (SCM port); | |
6321 | int (*fclose) (SCM port); | |
6322 | ||
6323 | The interfaces to the `mark', `print', `equalp', and `fgets' methods | |
6324 | are unchanged. | |
6325 | ||
6326 | If you have existing code which defines its own port types, it is easy | |
6327 | to convert your code to the new interface; simply apply SCM_STREAM to | |
6328 | the port argument to yield the value you code used to expect. | |
6329 | ||
6330 | Note that since both the port and the stream have the same type in the | |
6331 | C code --- they are both SCM values --- the C compiler will not remind | |
6332 | you if you forget to update your scm_ptobfuns functions. | |
6333 | ||
6334 | ||
933a7411 MD |
6335 | ** Function: int scm_internal_select (int fds, |
6336 | SELECT_TYPE *rfds, | |
6337 | SELECT_TYPE *wfds, | |
6338 | SELECT_TYPE *efds, | |
6339 | struct timeval *timeout); | |
6340 | ||
6341 | This is a replacement for the `select' function provided by the OS. | |
6342 | It enables I/O blocking and sleeping to happen for one cooperative | |
6343 | thread without blocking other threads. It also avoids busy-loops in | |
6344 | these situations. It is intended that all I/O blocking and sleeping | |
6345 | will finally go through this function. Currently, this function is | |
6346 | only available on systems providing `gettimeofday' and `select'. | |
6347 | ||
5424b4f7 MD |
6348 | ** Function: SCM scm_internal_stack_catch (SCM tag, |
6349 | scm_catch_body_t body, | |
6350 | void *body_data, | |
6351 | scm_catch_handler_t handler, | |
6352 | void *handler_data) | |
6353 | ||
6354 | A new sibling to the other two C level `catch' functions | |
6355 | scm_internal_catch and scm_internal_lazy_catch. Use it if you want | |
6356 | the stack to be saved automatically into the variable `the-last-stack' | |
6357 | (scm_the_last_stack_var) on error. This is necessary if you want to | |
6358 | use advanced error reporting, such as calling scm_display_error and | |
6359 | scm_display_backtrace. (They both take a stack object as argument.) | |
6360 | ||
df366c26 MD |
6361 | ** Function: SCM scm_spawn_thread (scm_catch_body_t body, |
6362 | void *body_data, | |
6363 | scm_catch_handler_t handler, | |
6364 | void *handler_data) | |
6365 | ||
6366 | Spawns a new thread. It does a job similar to | |
6367 | scm_call_with_new_thread but takes arguments more suitable when | |
6368 | spawning threads from application C code. | |
6369 | ||
88482b31 MD |
6370 | ** The hook scm_error_callback has been removed. It was originally |
6371 | intended as a way for the user to install his own error handler. But | |
6372 | that method works badly since it intervenes between throw and catch, | |
6373 | thereby changing the semantics of expressions like (catch #t ...). | |
6374 | The correct way to do it is to use one of the C level catch functions | |
6375 | in throw.c: scm_internal_catch/lazy_catch/stack_catch. | |
6376 | ||
3a97e020 MD |
6377 | ** Removed functions: |
6378 | ||
6379 | scm_obj_length, scm_list_length, scm_list_append, scm_list_append_x, | |
6380 | scm_list_reverse, scm_list_reverse_x | |
6381 | ||
6382 | ** New macros: SCM_LISTn where n is one of the integers 0-9. | |
6383 | ||
6384 | These can be used for pretty list creation from C. The idea is taken | |
6385 | from Erick Gallesio's STk. | |
6386 | ||
298aa6e3 MD |
6387 | ** scm_array_map renamed to scm_array_map_x |
6388 | ||
527da704 MD |
6389 | ** mbstrings are now removed |
6390 | ||
6391 | This means that the type codes scm_tc7_mb_string and | |
6392 | scm_tc7_mb_substring has been removed. | |
6393 | ||
8cd57bd0 JB |
6394 | ** scm_gen_putc, scm_gen_puts, scm_gen_write, and scm_gen_getc have changed. |
6395 | ||
6396 | Since we no longer support multi-byte strings, these I/O functions | |
6397 | have been simplified, and renamed. Here are their old names, and | |
6398 | their new names and arguments: | |
6399 | ||
6400 | scm_gen_putc -> void scm_putc (int c, SCM port); | |
6401 | scm_gen_puts -> void scm_puts (char *s, SCM port); | |
6402 | scm_gen_write -> void scm_lfwrite (char *ptr, scm_sizet size, SCM port); | |
6403 | scm_gen_getc -> void scm_getc (SCM port); | |
6404 | ||
6405 | ||
527da704 MD |
6406 | ** The macros SCM_TYP7D and SCM_TYP7SD has been removed. |
6407 | ||
6408 | ** The macro SCM_TYP7S has taken the role of the old SCM_TYP7D | |
6409 | ||
6410 | SCM_TYP7S now masks away the bit which distinguishes substrings from | |
6411 | strings. | |
6412 | ||
660f41fa MD |
6413 | ** scm_catch_body_t: Backward incompatible change! |
6414 | ||
6415 | Body functions to scm_internal_catch and friends do not any longer | |
6416 | take a second argument. This is because it is no longer possible to | |
6417 | pass a #f arg to catch. | |
6418 | ||
a8e05009 JB |
6419 | ** Calls to scm_protect_object and scm_unprotect now nest properly. |
6420 | ||
6421 | The function scm_protect_object protects its argument from being freed | |
6422 | by the garbage collector. scm_unprotect_object removes that | |
6423 | protection. | |
6424 | ||
6425 | These functions now nest properly. That is, for every object O, there | |
6426 | is a counter which scm_protect_object(O) increments and | |
6427 | scm_unprotect_object(O) decrements, if the counter is greater than | |
6428 | zero. Every object's counter is zero when it is first created. If an | |
6429 | object's counter is greater than zero, the garbage collector will not | |
6430 | reclaim its storage. | |
6431 | ||
6432 | This allows you to use scm_protect_object in your code without | |
6433 | worrying that some other function you call will call | |
6434 | scm_unprotect_object, and allow it to be freed. Assuming that the | |
6435 | functions you call are well-behaved, and unprotect only those objects | |
6436 | they protect, you can follow the same rule and have confidence that | |
6437 | objects will be freed only at appropriate times. | |
6438 | ||
c484bf7f JB |
6439 | \f |
6440 | Changes in Guile 1.2 (released Tuesday, June 24 1997): | |
cf78e9e8 | 6441 | |
737c9113 JB |
6442 | * Changes to the distribution |
6443 | ||
832b09ed JB |
6444 | ** Nightly snapshots are now available from ftp.red-bean.com. |
6445 | The old server, ftp.cyclic.com, has been relinquished to its rightful | |
6446 | owner. | |
6447 | ||
6448 | Nightly snapshots of the Guile development sources are now available via | |
6449 | anonymous FTP from ftp.red-bean.com, as /pub/guile/guile-snap.tar.gz. | |
6450 | ||
6451 | Via the web, that's: ftp://ftp.red-bean.com/pub/guile/guile-snap.tar.gz | |
6452 | For getit, that's: ftp.red-bean.com:/pub/guile/guile-snap.tar.gz | |
6453 | ||
0fcab5ed JB |
6454 | ** To run Guile without installing it, the procedure has changed a bit. |
6455 | ||
6456 | If you used a separate build directory to compile Guile, you'll need | |
6457 | to include the build directory in SCHEME_LOAD_PATH, as well as the | |
6458 | source directory. See the `INSTALL' file for examples. | |
6459 | ||
737c9113 JB |
6460 | * Changes to the procedure for linking libguile with your programs |
6461 | ||
94982a4e JB |
6462 | ** The standard Guile load path for Scheme code now includes |
6463 | $(datadir)/guile (usually /usr/local/share/guile). This means that | |
6464 | you can install your own Scheme files there, and Guile will find them. | |
6465 | (Previous versions of Guile only checked a directory whose name | |
6466 | contained the Guile version number, so you had to re-install or move | |
6467 | your Scheme sources each time you installed a fresh version of Guile.) | |
6468 | ||
6469 | The load path also includes $(datadir)/guile/site; we recommend | |
6470 | putting individual Scheme files there. If you want to install a | |
6471 | package with multiple source files, create a directory for them under | |
6472 | $(datadir)/guile. | |
6473 | ||
6474 | ** Guile 1.2 will now use the Rx regular expression library, if it is | |
6475 | installed on your system. When you are linking libguile into your own | |
6476 | programs, this means you will have to link against -lguile, -lqt (if | |
6477 | you configured Guile with thread support), and -lrx. | |
27590f82 JB |
6478 | |
6479 | If you are using autoconf to generate configuration scripts for your | |
6480 | application, the following lines should suffice to add the appropriate | |
6481 | libraries to your link command: | |
6482 | ||
6483 | ### Find Rx, quickthreads and libguile. | |
6484 | AC_CHECK_LIB(rx, main) | |
6485 | AC_CHECK_LIB(qt, main) | |
6486 | AC_CHECK_LIB(guile, scm_shell) | |
6487 | ||
94982a4e JB |
6488 | The Guile 1.2 distribution does not contain sources for the Rx |
6489 | library, as Guile 1.0 did. If you want to use Rx, you'll need to | |
6490 | retrieve it from a GNU FTP site and install it separately. | |
6491 | ||
b83b8bee JB |
6492 | * Changes to Scheme functions and syntax |
6493 | ||
e035e7e6 MV |
6494 | ** The dynamic linking features of Guile are now enabled by default. |
6495 | You can disable them by giving the `--disable-dynamic-linking' option | |
6496 | to configure. | |
6497 | ||
e035e7e6 MV |
6498 | (dynamic-link FILENAME) |
6499 | ||
6500 | Find the object file denoted by FILENAME (a string) and link it | |
6501 | into the running Guile application. When everything works out, | |
6502 | return a Scheme object suitable for representing the linked object | |
6503 | file. Otherwise an error is thrown. How object files are | |
6504 | searched is system dependent. | |
6505 | ||
6506 | (dynamic-object? VAL) | |
6507 | ||
6508 | Determine whether VAL represents a dynamically linked object file. | |
6509 | ||
6510 | (dynamic-unlink DYNOBJ) | |
6511 | ||
6512 | Unlink the indicated object file from the application. DYNOBJ | |
6513 | should be one of the values returned by `dynamic-link'. | |
6514 | ||
6515 | (dynamic-func FUNCTION DYNOBJ) | |
6516 | ||
6517 | Search the C function indicated by FUNCTION (a string or symbol) | |
6518 | in DYNOBJ and return some Scheme object that can later be used | |
6519 | with `dynamic-call' to actually call this function. Right now, | |
6520 | these Scheme objects are formed by casting the address of the | |
6521 | function to `long' and converting this number to its Scheme | |
6522 | representation. | |
6523 | ||
6524 | (dynamic-call FUNCTION DYNOBJ) | |
6525 | ||
6526 | Call the C function indicated by FUNCTION and DYNOBJ. The | |
6527 | function is passed no arguments and its return value is ignored. | |
6528 | When FUNCTION is something returned by `dynamic-func', call that | |
6529 | function and ignore DYNOBJ. When FUNCTION is a string (or symbol, | |
6530 | etc.), look it up in DYNOBJ; this is equivalent to | |
6531 | ||
6532 | (dynamic-call (dynamic-func FUNCTION DYNOBJ) #f) | |
6533 | ||
6534 | Interrupts are deferred while the C function is executing (with | |
6535 | SCM_DEFER_INTS/SCM_ALLOW_INTS). | |
6536 | ||
6537 | (dynamic-args-call FUNCTION DYNOBJ ARGS) | |
6538 | ||
6539 | Call the C function indicated by FUNCTION and DYNOBJ, but pass it | |
6540 | some arguments and return its return value. The C function is | |
6541 | expected to take two arguments and return an `int', just like | |
6542 | `main': | |
6543 | ||
6544 | int c_func (int argc, char **argv); | |
6545 | ||
6546 | ARGS must be a list of strings and is converted into an array of | |
6547 | `char *'. The array is passed in ARGV and its size in ARGC. The | |
6548 | return value is converted to a Scheme number and returned from the | |
6549 | call to `dynamic-args-call'. | |
6550 | ||
0fcab5ed JB |
6551 | When dynamic linking is disabled or not supported on your system, |
6552 | the above functions throw errors, but they are still available. | |
6553 | ||
e035e7e6 MV |
6554 | Here is a small example that works on GNU/Linux: |
6555 | ||
6556 | (define libc-obj (dynamic-link "libc.so")) | |
6557 | (dynamic-args-call 'rand libc-obj '()) | |
6558 | ||
6559 | See the file `libguile/DYNAMIC-LINKING' for additional comments. | |
6560 | ||
27590f82 | 6561 | ** The #/ syntax for module names is depreciated, and will be removed |
6c0201ad | 6562 | in a future version of Guile. Instead of |
27590f82 JB |
6563 | |
6564 | #/foo/bar/baz | |
6565 | ||
6566 | instead write | |
6567 | ||
6568 | (foo bar baz) | |
6569 | ||
6570 | The latter syntax is more consistent with existing Lisp practice. | |
6571 | ||
5dade857 MV |
6572 | ** Guile now does fancier printing of structures. Structures are the |
6573 | underlying implementation for records, which in turn are used to | |
6574 | implement modules, so all of these object now print differently and in | |
6575 | a more informative way. | |
6576 | ||
161029df JB |
6577 | The Scheme printer will examine the builtin variable *struct-printer* |
6578 | whenever it needs to print a structure object. When this variable is | |
6579 | not `#f' it is deemed to be a procedure and will be applied to the | |
6580 | structure object and the output port. When *struct-printer* is `#f' | |
6581 | or the procedure return `#f' the structure object will be printed in | |
6582 | the boring #<struct 80458270> form. | |
5dade857 MV |
6583 | |
6584 | This hook is used by some routines in ice-9/boot-9.scm to implement | |
6585 | type specific printing routines. Please read the comments there about | |
6586 | "printing structs". | |
6587 | ||
6588 | One of the more specific uses of structs are records. The printing | |
6589 | procedure that could be passed to MAKE-RECORD-TYPE is now actually | |
6590 | called. It should behave like a *struct-printer* procedure (described | |
6591 | above). | |
6592 | ||
b83b8bee JB |
6593 | ** Guile now supports a new R4RS-compliant syntax for keywords. A |
6594 | token of the form #:NAME, where NAME has the same syntax as a Scheme | |
6595 | symbol, is the external representation of the keyword named NAME. | |
6596 | Keyword objects print using this syntax as well, so values containing | |
1e5afba0 JB |
6597 | keyword objects can be read back into Guile. When used in an |
6598 | expression, keywords are self-quoting objects. | |
b83b8bee JB |
6599 | |
6600 | Guile suports this read syntax, and uses this print syntax, regardless | |
6601 | of the current setting of the `keyword' read option. The `keyword' | |
6602 | read option only controls whether Guile recognizes the `:NAME' syntax, | |
6603 | which is incompatible with R4RS. (R4RS says such token represent | |
6604 | symbols.) | |
737c9113 JB |
6605 | |
6606 | ** Guile has regular expression support again. Guile 1.0 included | |
6607 | functions for matching regular expressions, based on the Rx library. | |
6608 | In Guile 1.1, the Guile/Rx interface was removed to simplify the | |
6609 | distribution, and thus Guile had no regular expression support. Guile | |
94982a4e JB |
6610 | 1.2 again supports the most commonly used functions, and supports all |
6611 | of SCSH's regular expression functions. | |
2409cdfa | 6612 | |
94982a4e JB |
6613 | If your system does not include a POSIX regular expression library, |
6614 | and you have not linked Guile with a third-party regexp library such as | |
6615 | Rx, these functions will not be available. You can tell whether your | |
6616 | Guile installation includes regular expression support by checking | |
6617 | whether the `*features*' list includes the `regex' symbol. | |
737c9113 | 6618 | |
94982a4e | 6619 | *** regexp functions |
161029df | 6620 | |
94982a4e JB |
6621 | By default, Guile supports POSIX extended regular expressions. That |
6622 | means that the characters `(', `)', `+' and `?' are special, and must | |
6623 | be escaped if you wish to match the literal characters. | |
e1a191a8 | 6624 | |
94982a4e JB |
6625 | This regular expression interface was modeled after that implemented |
6626 | by SCSH, the Scheme Shell. It is intended to be upwardly compatible | |
6627 | with SCSH regular expressions. | |
6628 | ||
6629 | **** Function: string-match PATTERN STR [START] | |
6630 | Compile the string PATTERN into a regular expression and compare | |
6631 | it with STR. The optional numeric argument START specifies the | |
6632 | position of STR at which to begin matching. | |
6633 | ||
6634 | `string-match' returns a "match structure" which describes what, | |
6635 | if anything, was matched by the regular expression. *Note Match | |
6636 | Structures::. If STR does not match PATTERN at all, | |
6637 | `string-match' returns `#f'. | |
6638 | ||
6639 | Each time `string-match' is called, it must compile its PATTERN | |
6640 | argument into a regular expression structure. This operation is | |
6641 | expensive, which makes `string-match' inefficient if the same regular | |
6642 | expression is used several times (for example, in a loop). For better | |
6643 | performance, you can compile a regular expression in advance and then | |
6644 | match strings against the compiled regexp. | |
6645 | ||
6646 | **** Function: make-regexp STR [FLAGS] | |
6647 | Compile the regular expression described by STR, and return the | |
6648 | compiled regexp structure. If STR does not describe a legal | |
6649 | regular expression, `make-regexp' throws a | |
6650 | `regular-expression-syntax' error. | |
6651 | ||
6652 | FLAGS may be the bitwise-or of one or more of the following: | |
6653 | ||
6654 | **** Constant: regexp/extended | |
6655 | Use POSIX Extended Regular Expression syntax when interpreting | |
6656 | STR. If not set, POSIX Basic Regular Expression syntax is used. | |
6657 | If the FLAGS argument is omitted, we assume regexp/extended. | |
6658 | ||
6659 | **** Constant: regexp/icase | |
6660 | Do not differentiate case. Subsequent searches using the | |
6661 | returned regular expression will be case insensitive. | |
6662 | ||
6663 | **** Constant: regexp/newline | |
6664 | Match-any-character operators don't match a newline. | |
6665 | ||
6666 | A non-matching list ([^...]) not containing a newline matches a | |
6667 | newline. | |
6668 | ||
6669 | Match-beginning-of-line operator (^) matches the empty string | |
6670 | immediately after a newline, regardless of whether the FLAGS | |
6671 | passed to regexp-exec contain regexp/notbol. | |
6672 | ||
6673 | Match-end-of-line operator ($) matches the empty string | |
6674 | immediately before a newline, regardless of whether the FLAGS | |
6675 | passed to regexp-exec contain regexp/noteol. | |
6676 | ||
6677 | **** Function: regexp-exec REGEXP STR [START [FLAGS]] | |
6678 | Match the compiled regular expression REGEXP against `str'. If | |
6679 | the optional integer START argument is provided, begin matching | |
6680 | from that position in the string. Return a match structure | |
6681 | describing the results of the match, or `#f' if no match could be | |
6682 | found. | |
6683 | ||
6684 | FLAGS may be the bitwise-or of one or more of the following: | |
6685 | ||
6686 | **** Constant: regexp/notbol | |
6687 | The match-beginning-of-line operator always fails to match (but | |
6688 | see the compilation flag regexp/newline above) This flag may be | |
6689 | used when different portions of a string are passed to | |
6690 | regexp-exec and the beginning of the string should not be | |
6691 | interpreted as the beginning of the line. | |
6692 | ||
6693 | **** Constant: regexp/noteol | |
6694 | The match-end-of-line operator always fails to match (but see the | |
6695 | compilation flag regexp/newline above) | |
6696 | ||
6697 | **** Function: regexp? OBJ | |
6698 | Return `#t' if OBJ is a compiled regular expression, or `#f' | |
6699 | otherwise. | |
6700 | ||
6701 | Regular expressions are commonly used to find patterns in one string | |
6702 | and replace them with the contents of another string. | |
6703 | ||
6704 | **** Function: regexp-substitute PORT MATCH [ITEM...] | |
6705 | Write to the output port PORT selected contents of the match | |
6706 | structure MATCH. Each ITEM specifies what should be written, and | |
6707 | may be one of the following arguments: | |
6708 | ||
6709 | * A string. String arguments are written out verbatim. | |
6710 | ||
6711 | * An integer. The submatch with that number is written. | |
6712 | ||
6713 | * The symbol `pre'. The portion of the matched string preceding | |
6714 | the regexp match is written. | |
6715 | ||
6716 | * The symbol `post'. The portion of the matched string | |
6717 | following the regexp match is written. | |
6718 | ||
6719 | PORT may be `#f', in which case nothing is written; instead, | |
6720 | `regexp-substitute' constructs a string from the specified ITEMs | |
6721 | and returns that. | |
6722 | ||
6723 | **** Function: regexp-substitute/global PORT REGEXP TARGET [ITEM...] | |
6724 | Similar to `regexp-substitute', but can be used to perform global | |
6725 | substitutions on STR. Instead of taking a match structure as an | |
6726 | argument, `regexp-substitute/global' takes two string arguments: a | |
6727 | REGEXP string describing a regular expression, and a TARGET string | |
6728 | which should be matched against this regular expression. | |
6729 | ||
6730 | Each ITEM behaves as in REGEXP-SUBSTITUTE, with the following | |
6731 | exceptions: | |
6732 | ||
6733 | * A function may be supplied. When this function is called, it | |
6734 | will be passed one argument: a match structure for a given | |
6735 | regular expression match. It should return a string to be | |
6736 | written out to PORT. | |
6737 | ||
6738 | * The `post' symbol causes `regexp-substitute/global' to recurse | |
6739 | on the unmatched portion of STR. This *must* be supplied in | |
6740 | order to perform global search-and-replace on STR; if it is | |
6741 | not present among the ITEMs, then `regexp-substitute/global' | |
6742 | will return after processing a single match. | |
6743 | ||
6744 | *** Match Structures | |
6745 | ||
6746 | A "match structure" is the object returned by `string-match' and | |
6747 | `regexp-exec'. It describes which portion of a string, if any, matched | |
6748 | the given regular expression. Match structures include: a reference to | |
6749 | the string that was checked for matches; the starting and ending | |
6750 | positions of the regexp match; and, if the regexp included any | |
6751 | parenthesized subexpressions, the starting and ending positions of each | |
6752 | submatch. | |
6753 | ||
6754 | In each of the regexp match functions described below, the `match' | |
6755 | argument must be a match structure returned by a previous call to | |
6756 | `string-match' or `regexp-exec'. Most of these functions return some | |
6757 | information about the original target string that was matched against a | |
6758 | regular expression; we will call that string TARGET for easy reference. | |
6759 | ||
6760 | **** Function: regexp-match? OBJ | |
6761 | Return `#t' if OBJ is a match structure returned by a previous | |
6762 | call to `regexp-exec', or `#f' otherwise. | |
6763 | ||
6764 | **** Function: match:substring MATCH [N] | |
6765 | Return the portion of TARGET matched by subexpression number N. | |
6766 | Submatch 0 (the default) represents the entire regexp match. If | |
6767 | the regular expression as a whole matched, but the subexpression | |
6768 | number N did not match, return `#f'. | |
6769 | ||
6770 | **** Function: match:start MATCH [N] | |
6771 | Return the starting position of submatch number N. | |
6772 | ||
6773 | **** Function: match:end MATCH [N] | |
6774 | Return the ending position of submatch number N. | |
6775 | ||
6776 | **** Function: match:prefix MATCH | |
6777 | Return the unmatched portion of TARGET preceding the regexp match. | |
6778 | ||
6779 | **** Function: match:suffix MATCH | |
6780 | Return the unmatched portion of TARGET following the regexp match. | |
6781 | ||
6782 | **** Function: match:count MATCH | |
6783 | Return the number of parenthesized subexpressions from MATCH. | |
6784 | Note that the entire regular expression match itself counts as a | |
6785 | subexpression, and failed submatches are included in the count. | |
6786 | ||
6787 | **** Function: match:string MATCH | |
6788 | Return the original TARGET string. | |
6789 | ||
6790 | *** Backslash Escapes | |
6791 | ||
6792 | Sometimes you will want a regexp to match characters like `*' or `$' | |
6793 | exactly. For example, to check whether a particular string represents | |
6794 | a menu entry from an Info node, it would be useful to match it against | |
6795 | a regexp like `^* [^:]*::'. However, this won't work; because the | |
6796 | asterisk is a metacharacter, it won't match the `*' at the beginning of | |
6797 | the string. In this case, we want to make the first asterisk un-magic. | |
6798 | ||
6799 | You can do this by preceding the metacharacter with a backslash | |
6800 | character `\'. (This is also called "quoting" the metacharacter, and | |
6801 | is known as a "backslash escape".) When Guile sees a backslash in a | |
6802 | regular expression, it considers the following glyph to be an ordinary | |
6803 | character, no matter what special meaning it would ordinarily have. | |
6804 | Therefore, we can make the above example work by changing the regexp to | |
6805 | `^\* [^:]*::'. The `\*' sequence tells the regular expression engine | |
6806 | to match only a single asterisk in the target string. | |
6807 | ||
6808 | Since the backslash is itself a metacharacter, you may force a | |
6809 | regexp to match a backslash in the target string by preceding the | |
6810 | backslash with itself. For example, to find variable references in a | |
6811 | TeX program, you might want to find occurrences of the string `\let\' | |
6812 | followed by any number of alphabetic characters. The regular expression | |
6813 | `\\let\\[A-Za-z]*' would do this: the double backslashes in the regexp | |
6814 | each match a single backslash in the target string. | |
6815 | ||
6816 | **** Function: regexp-quote STR | |
6817 | Quote each special character found in STR with a backslash, and | |
6818 | return the resulting string. | |
6819 | ||
6820 | *Very important:* Using backslash escapes in Guile source code (as | |
6821 | in Emacs Lisp or C) can be tricky, because the backslash character has | |
6822 | special meaning for the Guile reader. For example, if Guile encounters | |
6823 | the character sequence `\n' in the middle of a string while processing | |
6824 | Scheme code, it replaces those characters with a newline character. | |
6825 | Similarly, the character sequence `\t' is replaced by a horizontal tab. | |
6826 | Several of these "escape sequences" are processed by the Guile reader | |
6827 | before your code is executed. Unrecognized escape sequences are | |
6828 | ignored: if the characters `\*' appear in a string, they will be | |
6829 | translated to the single character `*'. | |
6830 | ||
6831 | This translation is obviously undesirable for regular expressions, | |
6832 | since we want to be able to include backslashes in a string in order to | |
6833 | escape regexp metacharacters. Therefore, to make sure that a backslash | |
6834 | is preserved in a string in your Guile program, you must use *two* | |
6835 | consecutive backslashes: | |
6836 | ||
6837 | (define Info-menu-entry-pattern (make-regexp "^\\* [^:]*")) | |
6838 | ||
6839 | The string in this example is preprocessed by the Guile reader before | |
6840 | any code is executed. The resulting argument to `make-regexp' is the | |
6841 | string `^\* [^:]*', which is what we really want. | |
6842 | ||
6843 | This also means that in order to write a regular expression that | |
6844 | matches a single backslash character, the regular expression string in | |
6845 | the source code must include *four* backslashes. Each consecutive pair | |
6846 | of backslashes gets translated by the Guile reader to a single | |
6847 | backslash, and the resulting double-backslash is interpreted by the | |
6848 | regexp engine as matching a single backslash character. Hence: | |
6849 | ||
6850 | (define tex-variable-pattern (make-regexp "\\\\let\\\\=[A-Za-z]*")) | |
6851 | ||
6852 | The reason for the unwieldiness of this syntax is historical. Both | |
6853 | regular expression pattern matchers and Unix string processing systems | |
6854 | have traditionally used backslashes with the special meanings described | |
6855 | above. The POSIX regular expression specification and ANSI C standard | |
6856 | both require these semantics. Attempting to abandon either convention | |
6857 | would cause other kinds of compatibility problems, possibly more severe | |
6858 | ones. Therefore, without extending the Scheme reader to support | |
6859 | strings with different quoting conventions (an ungainly and confusing | |
6860 | extension when implemented in other languages), we must adhere to this | |
6861 | cumbersome escape syntax. | |
6862 | ||
7ad3c1e7 GH |
6863 | * Changes to the gh_ interface |
6864 | ||
6865 | * Changes to the scm_ interface | |
6866 | ||
6867 | * Changes to system call interfaces: | |
94982a4e | 6868 | |
7ad3c1e7 | 6869 | ** The value returned by `raise' is now unspecified. It throws an exception |
e1a191a8 GH |
6870 | if an error occurs. |
6871 | ||
94982a4e | 6872 | *** A new procedure `sigaction' can be used to install signal handlers |
115b09a5 GH |
6873 | |
6874 | (sigaction signum [action] [flags]) | |
6875 | ||
6876 | signum is the signal number, which can be specified using the value | |
6877 | of SIGINT etc. | |
6878 | ||
6879 | If action is omitted, sigaction returns a pair: the CAR is the current | |
6880 | signal hander, which will be either an integer with the value SIG_DFL | |
6881 | (default action) or SIG_IGN (ignore), or the Scheme procedure which | |
6882 | handles the signal, or #f if a non-Scheme procedure handles the | |
6883 | signal. The CDR contains the current sigaction flags for the handler. | |
6884 | ||
6885 | If action is provided, it is installed as the new handler for signum. | |
6886 | action can be a Scheme procedure taking one argument, or the value of | |
6887 | SIG_DFL (default action) or SIG_IGN (ignore), or #f to restore | |
6888 | whatever signal handler was installed before sigaction was first used. | |
6889 | Flags can optionally be specified for the new handler (SA_RESTART is | |
6890 | always used if the system provides it, so need not be specified.) The | |
6891 | return value is a pair with information about the old handler as | |
6892 | described above. | |
6893 | ||
6894 | This interface does not provide access to the "signal blocking" | |
6895 | facility. Maybe this is not needed, since the thread support may | |
6896 | provide solutions to the problem of consistent access to data | |
6897 | structures. | |
e1a191a8 | 6898 | |
94982a4e | 6899 | *** A new procedure `flush-all-ports' is equivalent to running |
89ea5b7c GH |
6900 | `force-output' on every port open for output. |
6901 | ||
94982a4e JB |
6902 | ** Guile now provides information on how it was built, via the new |
6903 | global variable, %guile-build-info. This variable records the values | |
6904 | of the standard GNU makefile directory variables as an assocation | |
6905 | list, mapping variable names (symbols) onto directory paths (strings). | |
6906 | For example, to find out where the Guile link libraries were | |
6907 | installed, you can say: | |
6908 | ||
6909 | guile -c "(display (assq-ref %guile-build-info 'libdir)) (newline)" | |
6910 | ||
6911 | ||
6912 | * Changes to the scm_ interface | |
6913 | ||
6914 | ** The new function scm_handle_by_message_noexit is just like the | |
6915 | existing scm_handle_by_message function, except that it doesn't call | |
6916 | exit to terminate the process. Instead, it prints a message and just | |
6917 | returns #f. This might be a more appropriate catch-all handler for | |
6918 | new dynamic roots and threads. | |
6919 | ||
cf78e9e8 | 6920 | \f |
c484bf7f | 6921 | Changes in Guile 1.1 (released Friday, May 16 1997): |
f3b1485f JB |
6922 | |
6923 | * Changes to the distribution. | |
6924 | ||
6925 | The Guile 1.0 distribution has been split up into several smaller | |
6926 | pieces: | |
6927 | guile-core --- the Guile interpreter itself. | |
6928 | guile-tcltk --- the interface between the Guile interpreter and | |
6929 | Tcl/Tk; Tcl is an interpreter for a stringy language, and Tk | |
6930 | is a toolkit for building graphical user interfaces. | |
6931 | guile-rgx-ctax --- the interface between Guile and the Rx regular | |
6932 | expression matcher, and the translator for the Ctax | |
6933 | programming language. These are packaged together because the | |
6934 | Ctax translator uses Rx to parse Ctax source code. | |
6935 | ||
095936d2 JB |
6936 | This NEWS file describes the changes made to guile-core since the 1.0 |
6937 | release. | |
6938 | ||
48d224d7 JB |
6939 | We no longer distribute the documentation, since it was either out of |
6940 | date, or incomplete. As soon as we have current documentation, we | |
6941 | will distribute it. | |
6942 | ||
0fcab5ed JB |
6943 | |
6944 | ||
f3b1485f JB |
6945 | * Changes to the stand-alone interpreter |
6946 | ||
48d224d7 JB |
6947 | ** guile now accepts command-line arguments compatible with SCSH, Olin |
6948 | Shivers' Scheme Shell. | |
6949 | ||
6950 | In general, arguments are evaluated from left to right, but there are | |
6951 | exceptions. The following switches stop argument processing, and | |
6952 | stash all remaining command-line arguments as the value returned by | |
6953 | the (command-line) function. | |
6954 | -s SCRIPT load Scheme source code from FILE, and exit | |
6955 | -c EXPR evalute Scheme expression EXPR, and exit | |
6956 | -- stop scanning arguments; run interactively | |
6957 | ||
6958 | The switches below are processed as they are encountered. | |
6959 | -l FILE load Scheme source code from FILE | |
6960 | -e FUNCTION after reading script, apply FUNCTION to | |
6961 | command line arguments | |
6962 | -ds do -s script at this point | |
6963 | --emacs enable Emacs protocol (experimental) | |
6964 | -h, --help display this help and exit | |
6965 | -v, --version display version information and exit | |
6966 | \ read arguments from following script lines | |
6967 | ||
6968 | So, for example, here is a Guile script named `ekko' (thanks, Olin) | |
6969 | which re-implements the traditional "echo" command: | |
6970 | ||
6971 | #!/usr/local/bin/guile -s | |
6972 | !# | |
6973 | (define (main args) | |
6974 | (map (lambda (arg) (display arg) (display " ")) | |
6975 | (cdr args)) | |
6976 | (newline)) | |
6977 | ||
6978 | (main (command-line)) | |
6979 | ||
6980 | Suppose we invoke this script as follows: | |
6981 | ||
6982 | ekko a speckled gecko | |
6983 | ||
6984 | Through the magic of Unix script processing (triggered by the `#!' | |
6985 | token at the top of the file), /usr/local/bin/guile receives the | |
6986 | following list of command-line arguments: | |
6987 | ||
6988 | ("-s" "./ekko" "a" "speckled" "gecko") | |
6989 | ||
6990 | Unix inserts the name of the script after the argument specified on | |
6991 | the first line of the file (in this case, "-s"), and then follows that | |
6992 | with the arguments given to the script. Guile loads the script, which | |
6993 | defines the `main' function, and then applies it to the list of | |
6994 | remaining command-line arguments, ("a" "speckled" "gecko"). | |
6995 | ||
095936d2 JB |
6996 | In Unix, the first line of a script file must take the following form: |
6997 | ||
6998 | #!INTERPRETER ARGUMENT | |
6999 | ||
7000 | where INTERPRETER is the absolute filename of the interpreter | |
7001 | executable, and ARGUMENT is a single command-line argument to pass to | |
7002 | the interpreter. | |
7003 | ||
7004 | You may only pass one argument to the interpreter, and its length is | |
7005 | limited. These restrictions can be annoying to work around, so Guile | |
7006 | provides a general mechanism (borrowed from, and compatible with, | |
7007 | SCSH) for circumventing them. | |
7008 | ||
7009 | If the ARGUMENT in a Guile script is a single backslash character, | |
7010 | `\', Guile will open the script file, parse arguments from its second | |
7011 | and subsequent lines, and replace the `\' with them. So, for example, | |
7012 | here is another implementation of the `ekko' script: | |
7013 | ||
7014 | #!/usr/local/bin/guile \ | |
7015 | -e main -s | |
7016 | !# | |
7017 | (define (main args) | |
7018 | (for-each (lambda (arg) (display arg) (display " ")) | |
7019 | (cdr args)) | |
7020 | (newline)) | |
7021 | ||
7022 | If the user invokes this script as follows: | |
7023 | ||
7024 | ekko a speckled gecko | |
7025 | ||
7026 | Unix expands this into | |
7027 | ||
7028 | /usr/local/bin/guile \ ekko a speckled gecko | |
7029 | ||
7030 | When Guile sees the `\' argument, it replaces it with the arguments | |
7031 | read from the second line of the script, producing: | |
7032 | ||
7033 | /usr/local/bin/guile -e main -s ekko a speckled gecko | |
7034 | ||
7035 | This tells Guile to load the `ekko' script, and apply the function | |
7036 | `main' to the argument list ("a" "speckled" "gecko"). | |
7037 | ||
7038 | Here is how Guile parses the command-line arguments: | |
7039 | - Each space character terminates an argument. This means that two | |
7040 | spaces in a row introduce an empty-string argument. | |
7041 | - The tab character is not permitted (unless you quote it with the | |
7042 | backslash character, as described below), to avoid confusion. | |
7043 | - The newline character terminates the sequence of arguments, and will | |
7044 | also terminate a final non-empty argument. (However, a newline | |
7045 | following a space will not introduce a final empty-string argument; | |
7046 | it only terminates the argument list.) | |
7047 | - The backslash character is the escape character. It escapes | |
7048 | backslash, space, tab, and newline. The ANSI C escape sequences | |
7049 | like \n and \t are also supported. These produce argument | |
7050 | constituents; the two-character combination \n doesn't act like a | |
7051 | terminating newline. The escape sequence \NNN for exactly three | |
7052 | octal digits reads as the character whose ASCII code is NNN. As | |
7053 | above, characters produced this way are argument constituents. | |
7054 | Backslash followed by other characters is not allowed. | |
7055 | ||
48d224d7 JB |
7056 | * Changes to the procedure for linking libguile with your programs |
7057 | ||
7058 | ** Guile now builds and installs a shared guile library, if your | |
7059 | system support shared libraries. (It still builds a static library on | |
7060 | all systems.) Guile automatically detects whether your system | |
7061 | supports shared libraries. To prevent Guile from buildisg shared | |
7062 | libraries, pass the `--disable-shared' flag to the configure script. | |
7063 | ||
7064 | Guile takes longer to compile when it builds shared libraries, because | |
7065 | it must compile every file twice --- once to produce position- | |
7066 | independent object code, and once to produce normal object code. | |
7067 | ||
7068 | ** The libthreads library has been merged into libguile. | |
7069 | ||
7070 | To link a program against Guile, you now need only link against | |
7071 | -lguile and -lqt; -lthreads is no longer needed. If you are using | |
7072 | autoconf to generate configuration scripts for your application, the | |
7073 | following lines should suffice to add the appropriate libraries to | |
7074 | your link command: | |
7075 | ||
7076 | ### Find quickthreads and libguile. | |
7077 | AC_CHECK_LIB(qt, main) | |
7078 | AC_CHECK_LIB(guile, scm_shell) | |
f3b1485f JB |
7079 | |
7080 | * Changes to Scheme functions | |
7081 | ||
095936d2 JB |
7082 | ** Guile Scheme's special syntax for keyword objects is now optional, |
7083 | and disabled by default. | |
7084 | ||
7085 | The syntax variation from R4RS made it difficult to port some | |
7086 | interesting packages to Guile. The routines which accepted keyword | |
7087 | arguments (mostly in the module system) have been modified to also | |
7088 | accept symbols whose names begin with `:'. | |
7089 | ||
7090 | To change the keyword syntax, you must first import the (ice-9 debug) | |
7091 | module: | |
7092 | (use-modules (ice-9 debug)) | |
7093 | ||
7094 | Then you can enable the keyword syntax as follows: | |
7095 | (read-set! keywords 'prefix) | |
7096 | ||
7097 | To disable keyword syntax, do this: | |
7098 | (read-set! keywords #f) | |
7099 | ||
7100 | ** Many more primitive functions accept shared substrings as | |
7101 | arguments. In the past, these functions required normal, mutable | |
7102 | strings as arguments, although they never made use of this | |
7103 | restriction. | |
7104 | ||
7105 | ** The uniform array functions now operate on byte vectors. These | |
7106 | functions are `array-fill!', `serial-array-copy!', `array-copy!', | |
7107 | `serial-array-map', `array-map', `array-for-each', and | |
7108 | `array-index-map!'. | |
7109 | ||
7110 | ** The new functions `trace' and `untrace' implement simple debugging | |
7111 | support for Scheme functions. | |
7112 | ||
7113 | The `trace' function accepts any number of procedures as arguments, | |
7114 | and tells the Guile interpreter to display each procedure's name and | |
7115 | arguments each time the procedure is invoked. When invoked with no | |
7116 | arguments, `trace' returns the list of procedures currently being | |
7117 | traced. | |
7118 | ||
7119 | The `untrace' function accepts any number of procedures as arguments, | |
7120 | and tells the Guile interpreter not to trace them any more. When | |
7121 | invoked with no arguments, `untrace' untraces all curretly traced | |
7122 | procedures. | |
7123 | ||
7124 | The tracing in Guile has an advantage over most other systems: we | |
7125 | don't create new procedure objects, but mark the procedure objects | |
7126 | themselves. This means that anonymous and internal procedures can be | |
7127 | traced. | |
7128 | ||
7129 | ** The function `assert-repl-prompt' has been renamed to | |
7130 | `set-repl-prompt!'. It takes one argument, PROMPT. | |
7131 | - If PROMPT is #f, the Guile read-eval-print loop will not prompt. | |
7132 | - If PROMPT is a string, we use it as a prompt. | |
7133 | - If PROMPT is a procedure accepting no arguments, we call it, and | |
7134 | display the result as a prompt. | |
7135 | - Otherwise, we display "> ". | |
7136 | ||
7137 | ** The new function `eval-string' reads Scheme expressions from a | |
7138 | string and evaluates them, returning the value of the last expression | |
7139 | in the string. If the string contains no expressions, it returns an | |
7140 | unspecified value. | |
7141 | ||
7142 | ** The new function `thunk?' returns true iff its argument is a | |
7143 | procedure of zero arguments. | |
7144 | ||
7145 | ** `defined?' is now a builtin function, instead of syntax. This | |
7146 | means that its argument should be quoted. It returns #t iff its | |
7147 | argument is bound in the current module. | |
7148 | ||
7149 | ** The new syntax `use-modules' allows you to add new modules to your | |
7150 | environment without re-typing a complete `define-module' form. It | |
7151 | accepts any number of module names as arguments, and imports their | |
7152 | public bindings into the current module. | |
7153 | ||
7154 | ** The new function (module-defined? NAME MODULE) returns true iff | |
7155 | NAME, a symbol, is defined in MODULE, a module object. | |
7156 | ||
7157 | ** The new function `builtin-bindings' creates and returns a hash | |
7158 | table containing copies of all the root module's bindings. | |
7159 | ||
7160 | ** The new function `builtin-weak-bindings' does the same as | |
7161 | `builtin-bindings', but creates a doubly-weak hash table. | |
7162 | ||
7163 | ** The `equal?' function now considers variable objects to be | |
7164 | equivalent if they have the same name and the same value. | |
7165 | ||
7166 | ** The new function `command-line' returns the command-line arguments | |
7167 | given to Guile, as a list of strings. | |
7168 | ||
7169 | When using guile as a script interpreter, `command-line' returns the | |
7170 | script's arguments; those processed by the interpreter (like `-s' or | |
7171 | `-c') are omitted. (In other words, you get the normal, expected | |
7172 | behavior.) Any application that uses scm_shell to process its | |
7173 | command-line arguments gets this behavior as well. | |
7174 | ||
7175 | ** The new function `load-user-init' looks for a file called `.guile' | |
7176 | in the user's home directory, and loads it if it exists. This is | |
7177 | mostly for use by the code generated by scm_compile_shell_switches, | |
7178 | but we thought it might also be useful in other circumstances. | |
7179 | ||
7180 | ** The new function `log10' returns the base-10 logarithm of its | |
7181 | argument. | |
7182 | ||
7183 | ** Changes to I/O functions | |
7184 | ||
6c0201ad | 7185 | *** The functions `read', `primitive-load', `read-and-eval!', and |
095936d2 JB |
7186 | `primitive-load-path' no longer take optional arguments controlling |
7187 | case insensitivity and a `#' parser. | |
7188 | ||
7189 | Case sensitivity is now controlled by a read option called | |
7190 | `case-insensitive'. The user can add new `#' syntaxes with the | |
7191 | `read-hash-extend' function (see below). | |
7192 | ||
7193 | *** The new function `read-hash-extend' allows the user to change the | |
7194 | syntax of Guile Scheme in a somewhat controlled way. | |
7195 | ||
7196 | (read-hash-extend CHAR PROC) | |
7197 | When parsing S-expressions, if we read a `#' character followed by | |
7198 | the character CHAR, use PROC to parse an object from the stream. | |
7199 | If PROC is #f, remove any parsing procedure registered for CHAR. | |
7200 | ||
7201 | The reader applies PROC to two arguments: CHAR and an input port. | |
7202 | ||
6c0201ad | 7203 | *** The new functions read-delimited and read-delimited! provide a |
095936d2 JB |
7204 | general mechanism for doing delimited input on streams. |
7205 | ||
7206 | (read-delimited DELIMS [PORT HANDLE-DELIM]) | |
7207 | Read until we encounter one of the characters in DELIMS (a string), | |
7208 | or end-of-file. PORT is the input port to read from; it defaults to | |
7209 | the current input port. The HANDLE-DELIM parameter determines how | |
7210 | the terminating character is handled; it should be one of the | |
7211 | following symbols: | |
7212 | ||
7213 | 'trim omit delimiter from result | |
7214 | 'peek leave delimiter character in input stream | |
7215 | 'concat append delimiter character to returned value | |
7216 | 'split return a pair: (RESULT . TERMINATOR) | |
7217 | ||
7218 | HANDLE-DELIM defaults to 'peek. | |
7219 | ||
7220 | (read-delimited! DELIMS BUF [PORT HANDLE-DELIM START END]) | |
7221 | A side-effecting variant of `read-delimited'. | |
7222 | ||
7223 | The data is written into the string BUF at the indices in the | |
7224 | half-open interval [START, END); the default interval is the whole | |
7225 | string: START = 0 and END = (string-length BUF). The values of | |
7226 | START and END must specify a well-defined interval in BUF, i.e. | |
7227 | 0 <= START <= END <= (string-length BUF). | |
7228 | ||
7229 | It returns NBYTES, the number of bytes read. If the buffer filled | |
7230 | up without a delimiter character being found, it returns #f. If the | |
7231 | port is at EOF when the read starts, it returns the EOF object. | |
7232 | ||
7233 | If an integer is returned (i.e., the read is successfully terminated | |
7234 | by reading a delimiter character), then the HANDLE-DELIM parameter | |
7235 | determines how to handle the terminating character. It is described | |
7236 | above, and defaults to 'peek. | |
7237 | ||
7238 | (The descriptions of these functions were borrowed from the SCSH | |
7239 | manual, by Olin Shivers and Brian Carlstrom.) | |
7240 | ||
7241 | *** The `%read-delimited!' function is the primitive used to implement | |
7242 | `read-delimited' and `read-delimited!'. | |
7243 | ||
7244 | (%read-delimited! DELIMS BUF GOBBLE? [PORT START END]) | |
7245 | ||
7246 | This returns a pair of values: (TERMINATOR . NUM-READ). | |
7247 | - TERMINATOR describes why the read was terminated. If it is a | |
7248 | character or the eof object, then that is the value that terminated | |
7249 | the read. If it is #f, the function filled the buffer without finding | |
7250 | a delimiting character. | |
7251 | - NUM-READ is the number of characters read into BUF. | |
7252 | ||
7253 | If the read is successfully terminated by reading a delimiter | |
7254 | character, then the gobble? parameter determines what to do with the | |
7255 | terminating character. If true, the character is removed from the | |
7256 | input stream; if false, the character is left in the input stream | |
7257 | where a subsequent read operation will retrieve it. In either case, | |
7258 | the character is also the first value returned by the procedure call. | |
7259 | ||
7260 | (The descriptions of this function was borrowed from the SCSH manual, | |
7261 | by Olin Shivers and Brian Carlstrom.) | |
7262 | ||
7263 | *** The `read-line' and `read-line!' functions have changed; they now | |
7264 | trim the terminator by default; previously they appended it to the | |
7265 | returned string. For the old behavior, use (read-line PORT 'concat). | |
7266 | ||
7267 | *** The functions `uniform-array-read!' and `uniform-array-write!' now | |
7268 | take new optional START and END arguments, specifying the region of | |
7269 | the array to read and write. | |
7270 | ||
f348c807 JB |
7271 | *** The `ungetc-char-ready?' function has been removed. We feel it's |
7272 | inappropriate for an interface to expose implementation details this | |
7273 | way. | |
095936d2 JB |
7274 | |
7275 | ** Changes to the Unix library and system call interface | |
7276 | ||
7277 | *** The new fcntl function provides access to the Unix `fcntl' system | |
7278 | call. | |
7279 | ||
7280 | (fcntl PORT COMMAND VALUE) | |
7281 | Apply COMMAND to PORT's file descriptor, with VALUE as an argument. | |
7282 | Values for COMMAND are: | |
7283 | ||
7284 | F_DUPFD duplicate a file descriptor | |
7285 | F_GETFD read the descriptor's close-on-exec flag | |
7286 | F_SETFD set the descriptor's close-on-exec flag to VALUE | |
7287 | F_GETFL read the descriptor's flags, as set on open | |
7288 | F_SETFL set the descriptor's flags, as set on open to VALUE | |
7289 | F_GETOWN return the process ID of a socket's owner, for SIGIO | |
7290 | F_SETOWN set the process that owns a socket to VALUE, for SIGIO | |
7291 | FD_CLOEXEC not sure what this is | |
7292 | ||
7293 | For details, see the documentation for the fcntl system call. | |
7294 | ||
7295 | *** The arguments to `select' have changed, for compatibility with | |
7296 | SCSH. The TIMEOUT parameter may now be non-integral, yielding the | |
7297 | expected behavior. The MILLISECONDS parameter has been changed to | |
7298 | MICROSECONDS, to more closely resemble the underlying system call. | |
7299 | The RVEC, WVEC, and EVEC arguments can now be vectors; the type of the | |
7300 | corresponding return set will be the same. | |
7301 | ||
7302 | *** The arguments to the `mknod' system call have changed. They are | |
7303 | now: | |
7304 | ||
7305 | (mknod PATH TYPE PERMS DEV) | |
7306 | Create a new file (`node') in the file system. PATH is the name of | |
7307 | the file to create. TYPE is the kind of file to create; it should | |
7308 | be 'fifo, 'block-special, or 'char-special. PERMS specifies the | |
7309 | permission bits to give the newly created file. If TYPE is | |
7310 | 'block-special or 'char-special, DEV specifies which device the | |
7311 | special file refers to; its interpretation depends on the kind of | |
7312 | special file being created. | |
7313 | ||
7314 | *** The `fork' function has been renamed to `primitive-fork', to avoid | |
7315 | clashing with various SCSH forks. | |
7316 | ||
7317 | *** The `recv' and `recvfrom' functions have been renamed to `recv!' | |
7318 | and `recvfrom!'. They no longer accept a size for a second argument; | |
7319 | you must pass a string to hold the received value. They no longer | |
7320 | return the buffer. Instead, `recv' returns the length of the message | |
7321 | received, and `recvfrom' returns a pair containing the packet's length | |
6c0201ad | 7322 | and originating address. |
095936d2 JB |
7323 | |
7324 | *** The file descriptor datatype has been removed, as have the | |
7325 | `read-fd', `write-fd', `close', `lseek', and `dup' functions. | |
7326 | We plan to replace these functions with a SCSH-compatible interface. | |
7327 | ||
7328 | *** The `create' function has been removed; it's just a special case | |
7329 | of `open'. | |
7330 | ||
7331 | *** There are new functions to break down process termination status | |
7332 | values. In the descriptions below, STATUS is a value returned by | |
7333 | `waitpid'. | |
7334 | ||
7335 | (status:exit-val STATUS) | |
7336 | If the child process exited normally, this function returns the exit | |
7337 | code for the child process (i.e., the value passed to exit, or | |
7338 | returned from main). If the child process did not exit normally, | |
7339 | this function returns #f. | |
7340 | ||
7341 | (status:stop-sig STATUS) | |
7342 | If the child process was suspended by a signal, this function | |
7343 | returns the signal that suspended the child. Otherwise, it returns | |
7344 | #f. | |
7345 | ||
7346 | (status:term-sig STATUS) | |
7347 | If the child process terminated abnormally, this function returns | |
7348 | the signal that terminated the child. Otherwise, this function | |
7349 | returns false. | |
7350 | ||
7351 | POSIX promises that exactly one of these functions will return true on | |
7352 | a valid STATUS value. | |
7353 | ||
7354 | These functions are compatible with SCSH. | |
7355 | ||
7356 | *** There are new accessors and setters for the broken-out time vectors | |
48d224d7 JB |
7357 | returned by `localtime', `gmtime', and that ilk. They are: |
7358 | ||
7359 | Component Accessor Setter | |
7360 | ========================= ============ ============ | |
7361 | seconds tm:sec set-tm:sec | |
7362 | minutes tm:min set-tm:min | |
7363 | hours tm:hour set-tm:hour | |
7364 | day of the month tm:mday set-tm:mday | |
7365 | month tm:mon set-tm:mon | |
7366 | year tm:year set-tm:year | |
7367 | day of the week tm:wday set-tm:wday | |
7368 | day in the year tm:yday set-tm:yday | |
7369 | daylight saving time tm:isdst set-tm:isdst | |
7370 | GMT offset, seconds tm:gmtoff set-tm:gmtoff | |
7371 | name of time zone tm:zone set-tm:zone | |
7372 | ||
095936d2 JB |
7373 | *** There are new accessors for the vectors returned by `uname', |
7374 | describing the host system: | |
48d224d7 JB |
7375 | |
7376 | Component Accessor | |
7377 | ============================================== ================ | |
7378 | name of the operating system implementation utsname:sysname | |
7379 | network name of this machine utsname:nodename | |
7380 | release level of the operating system utsname:release | |
7381 | version level of the operating system utsname:version | |
7382 | machine hardware platform utsname:machine | |
7383 | ||
095936d2 JB |
7384 | *** There are new accessors for the vectors returned by `getpw', |
7385 | `getpwnam', `getpwuid', and `getpwent', describing entries from the | |
7386 | system's user database: | |
7387 | ||
7388 | Component Accessor | |
7389 | ====================== ================= | |
7390 | user name passwd:name | |
7391 | user password passwd:passwd | |
7392 | user id passwd:uid | |
7393 | group id passwd:gid | |
7394 | real name passwd:gecos | |
7395 | home directory passwd:dir | |
7396 | shell program passwd:shell | |
7397 | ||
7398 | *** There are new accessors for the vectors returned by `getgr', | |
7399 | `getgrnam', `getgrgid', and `getgrent', describing entries from the | |
7400 | system's group database: | |
7401 | ||
7402 | Component Accessor | |
7403 | ======================= ============ | |
7404 | group name group:name | |
7405 | group password group:passwd | |
7406 | group id group:gid | |
7407 | group members group:mem | |
7408 | ||
7409 | *** There are new accessors for the vectors returned by `gethost', | |
7410 | `gethostbyaddr', `gethostbyname', and `gethostent', describing | |
7411 | internet hosts: | |
7412 | ||
7413 | Component Accessor | |
7414 | ========================= =============== | |
7415 | official name of host hostent:name | |
7416 | alias list hostent:aliases | |
7417 | host address type hostent:addrtype | |
7418 | length of address hostent:length | |
7419 | list of addresses hostent:addr-list | |
7420 | ||
7421 | *** There are new accessors for the vectors returned by `getnet', | |
7422 | `getnetbyaddr', `getnetbyname', and `getnetent', describing internet | |
7423 | networks: | |
7424 | ||
7425 | Component Accessor | |
7426 | ========================= =============== | |
7427 | official name of net netent:name | |
7428 | alias list netent:aliases | |
7429 | net number type netent:addrtype | |
7430 | net number netent:net | |
7431 | ||
7432 | *** There are new accessors for the vectors returned by `getproto', | |
7433 | `getprotobyname', `getprotobynumber', and `getprotoent', describing | |
7434 | internet protocols: | |
7435 | ||
7436 | Component Accessor | |
7437 | ========================= =============== | |
7438 | official protocol name protoent:name | |
7439 | alias list protoent:aliases | |
7440 | protocol number protoent:proto | |
7441 | ||
7442 | *** There are new accessors for the vectors returned by `getserv', | |
7443 | `getservbyname', `getservbyport', and `getservent', describing | |
7444 | internet protocols: | |
7445 | ||
7446 | Component Accessor | |
7447 | ========================= =============== | |
6c0201ad | 7448 | official service name servent:name |
095936d2 | 7449 | alias list servent:aliases |
6c0201ad TTN |
7450 | port number servent:port |
7451 | protocol to use servent:proto | |
095936d2 JB |
7452 | |
7453 | *** There are new accessors for the sockaddr structures returned by | |
7454 | `accept', `getsockname', `getpeername', `recvfrom!': | |
7455 | ||
7456 | Component Accessor | |
7457 | ======================================== =============== | |
6c0201ad | 7458 | address format (`family') sockaddr:fam |
095936d2 JB |
7459 | path, for file domain addresses sockaddr:path |
7460 | address, for internet domain addresses sockaddr:addr | |
7461 | TCP or UDP port, for internet sockaddr:port | |
7462 | ||
7463 | *** The `getpwent', `getgrent', `gethostent', `getnetent', | |
7464 | `getprotoent', and `getservent' functions now return #f at the end of | |
7465 | the user database. (They used to throw an exception.) | |
7466 | ||
7467 | Note that calling MUMBLEent function is equivalent to calling the | |
7468 | corresponding MUMBLE function with no arguments. | |
7469 | ||
7470 | *** The `setpwent', `setgrent', `sethostent', `setnetent', | |
7471 | `setprotoent', and `setservent' routines now take no arguments. | |
7472 | ||
7473 | *** The `gethost', `getproto', `getnet', and `getserv' functions now | |
7474 | provide more useful information when they throw an exception. | |
7475 | ||
7476 | *** The `lnaof' function has been renamed to `inet-lnaof'. | |
7477 | ||
7478 | *** Guile now claims to have the `current-time' feature. | |
7479 | ||
7480 | *** The `mktime' function now takes an optional second argument ZONE, | |
7481 | giving the time zone to use for the conversion. ZONE should be a | |
7482 | string, in the same format as expected for the "TZ" environment variable. | |
7483 | ||
7484 | *** The `strptime' function now returns a pair (TIME . COUNT), where | |
7485 | TIME is the parsed time as a vector, and COUNT is the number of | |
7486 | characters from the string left unparsed. This function used to | |
7487 | return the remaining characters as a string. | |
7488 | ||
7489 | *** The `gettimeofday' function has replaced the old `time+ticks' function. | |
7490 | The return value is now (SECONDS . MICROSECONDS); the fractional | |
7491 | component is no longer expressed in "ticks". | |
7492 | ||
7493 | *** The `ticks/sec' constant has been removed, in light of the above change. | |
6685dc83 | 7494 | |
ea00ecba MG |
7495 | * Changes to the gh_ interface |
7496 | ||
7497 | ** gh_eval_str() now returns an SCM object which is the result of the | |
7498 | evaluation | |
7499 | ||
aaef0d2a MG |
7500 | ** gh_scm2str() now copies the Scheme data to a caller-provided C |
7501 | array | |
7502 | ||
7503 | ** gh_scm2newstr() now makes a C array, copies the Scheme data to it, | |
7504 | and returns the array | |
7505 | ||
7506 | ** gh_scm2str0() is gone: there is no need to distinguish | |
7507 | null-terminated from non-null-terminated, since gh_scm2newstr() allows | |
7508 | the user to interpret the data both ways. | |
7509 | ||
f3b1485f JB |
7510 | * Changes to the scm_ interface |
7511 | ||
095936d2 JB |
7512 | ** The new function scm_symbol_value0 provides an easy way to get a |
7513 | symbol's value from C code: | |
7514 | ||
7515 | SCM scm_symbol_value0 (char *NAME) | |
7516 | Return the value of the symbol named by the null-terminated string | |
7517 | NAME in the current module. If the symbol named NAME is unbound in | |
7518 | the current module, return SCM_UNDEFINED. | |
7519 | ||
7520 | ** The new function scm_sysintern0 creates new top-level variables, | |
7521 | without assigning them a value. | |
7522 | ||
7523 | SCM scm_sysintern0 (char *NAME) | |
7524 | Create a new Scheme top-level variable named NAME. NAME is a | |
7525 | null-terminated string. Return the variable's value cell. | |
7526 | ||
7527 | ** The function scm_internal_catch is the guts of catch. It handles | |
7528 | all the mechanics of setting up a catch target, invoking the catch | |
7529 | body, and perhaps invoking the handler if the body does a throw. | |
7530 | ||
7531 | The function is designed to be usable from C code, but is general | |
7532 | enough to implement all the semantics Guile Scheme expects from throw. | |
7533 | ||
7534 | TAG is the catch tag. Typically, this is a symbol, but this function | |
7535 | doesn't actually care about that. | |
7536 | ||
7537 | BODY is a pointer to a C function which runs the body of the catch; | |
7538 | this is the code you can throw from. We call it like this: | |
7539 | BODY (BODY_DATA, JMPBUF) | |
7540 | where: | |
7541 | BODY_DATA is just the BODY_DATA argument we received; we pass it | |
7542 | through to BODY as its first argument. The caller can make | |
7543 | BODY_DATA point to anything useful that BODY might need. | |
7544 | JMPBUF is the Scheme jmpbuf object corresponding to this catch, | |
7545 | which we have just created and initialized. | |
7546 | ||
7547 | HANDLER is a pointer to a C function to deal with a throw to TAG, | |
7548 | should one occur. We call it like this: | |
7549 | HANDLER (HANDLER_DATA, THROWN_TAG, THROW_ARGS) | |
7550 | where | |
7551 | HANDLER_DATA is the HANDLER_DATA argument we recevied; it's the | |
7552 | same idea as BODY_DATA above. | |
7553 | THROWN_TAG is the tag that the user threw to; usually this is | |
7554 | TAG, but it could be something else if TAG was #t (i.e., a | |
7555 | catch-all), or the user threw to a jmpbuf. | |
7556 | THROW_ARGS is the list of arguments the user passed to the THROW | |
7557 | function. | |
7558 | ||
7559 | BODY_DATA is just a pointer we pass through to BODY. HANDLER_DATA | |
7560 | is just a pointer we pass through to HANDLER. We don't actually | |
7561 | use either of those pointers otherwise ourselves. The idea is | |
7562 | that, if our caller wants to communicate something to BODY or | |
7563 | HANDLER, it can pass a pointer to it as MUMBLE_DATA, which BODY and | |
7564 | HANDLER can then use. Think of it as a way to make BODY and | |
7565 | HANDLER closures, not just functions; MUMBLE_DATA points to the | |
7566 | enclosed variables. | |
7567 | ||
7568 | Of course, it's up to the caller to make sure that any data a | |
7569 | MUMBLE_DATA needs is protected from GC. A common way to do this is | |
7570 | to make MUMBLE_DATA a pointer to data stored in an automatic | |
7571 | structure variable; since the collector must scan the stack for | |
7572 | references anyway, this assures that any references in MUMBLE_DATA | |
7573 | will be found. | |
7574 | ||
7575 | ** The new function scm_internal_lazy_catch is exactly like | |
7576 | scm_internal_catch, except: | |
7577 | ||
7578 | - It does not unwind the stack (this is the major difference). | |
7579 | - If handler returns, its value is returned from the throw. | |
7580 | - BODY always receives #f as its JMPBUF argument (since there's no | |
7581 | jmpbuf associated with a lazy catch, because we don't unwind the | |
7582 | stack.) | |
7583 | ||
7584 | ** scm_body_thunk is a new body function you can pass to | |
7585 | scm_internal_catch if you want the body to be like Scheme's `catch' | |
7586 | --- a thunk, or a function of one argument if the tag is #f. | |
7587 | ||
7588 | BODY_DATA is a pointer to a scm_body_thunk_data structure, which | |
7589 | contains the Scheme procedure to invoke as the body, and the tag | |
7590 | we're catching. If the tag is #f, then we pass JMPBUF (created by | |
7591 | scm_internal_catch) to the body procedure; otherwise, the body gets | |
7592 | no arguments. | |
7593 | ||
7594 | ** scm_handle_by_proc is a new handler function you can pass to | |
7595 | scm_internal_catch if you want the handler to act like Scheme's catch | |
7596 | --- call a procedure with the tag and the throw arguments. | |
7597 | ||
7598 | If the user does a throw to this catch, this function runs a handler | |
7599 | procedure written in Scheme. HANDLER_DATA is a pointer to an SCM | |
7600 | variable holding the Scheme procedure object to invoke. It ought to | |
7601 | be a pointer to an automatic variable (i.e., one living on the stack), | |
7602 | or the procedure object should be otherwise protected from GC. | |
7603 | ||
7604 | ** scm_handle_by_message is a new handler function to use with | |
7605 | `scm_internal_catch' if you want Guile to print a message and die. | |
7606 | It's useful for dealing with throws to uncaught keys at the top level. | |
7607 | ||
7608 | HANDLER_DATA, if non-zero, is assumed to be a char * pointing to a | |
7609 | message header to print; if zero, we use "guile" instead. That | |
7610 | text is followed by a colon, then the message described by ARGS. | |
7611 | ||
7612 | ** The return type of scm_boot_guile is now void; the function does | |
7613 | not return a value, and indeed, never returns at all. | |
7614 | ||
f3b1485f JB |
7615 | ** The new function scm_shell makes it easy for user applications to |
7616 | process command-line arguments in a way that is compatible with the | |
7617 | stand-alone guile interpreter (which is in turn compatible with SCSH, | |
7618 | the Scheme shell). | |
7619 | ||
7620 | To use the scm_shell function, first initialize any guile modules | |
7621 | linked into your application, and then call scm_shell with the values | |
7ed46dc8 | 7622 | of ARGC and ARGV your `main' function received. scm_shell will add |
f3b1485f JB |
7623 | any SCSH-style meta-arguments from the top of the script file to the |
7624 | argument vector, and then process the command-line arguments. This | |
7625 | generally means loading a script file or starting up an interactive | |
7626 | command interpreter. For details, see "Changes to the stand-alone | |
7627 | interpreter" above. | |
7628 | ||
095936d2 | 7629 | ** The new functions scm_get_meta_args and scm_count_argv help you |
6c0201ad | 7630 | implement the SCSH-style meta-argument, `\'. |
095936d2 JB |
7631 | |
7632 | char **scm_get_meta_args (int ARGC, char **ARGV) | |
7633 | If the second element of ARGV is a string consisting of a single | |
7634 | backslash character (i.e. "\\" in Scheme notation), open the file | |
7635 | named by the following argument, parse arguments from it, and return | |
7636 | the spliced command line. The returned array is terminated by a | |
7637 | null pointer. | |
6c0201ad | 7638 | |
095936d2 JB |
7639 | For details of argument parsing, see above, under "guile now accepts |
7640 | command-line arguments compatible with SCSH..." | |
7641 | ||
7642 | int scm_count_argv (char **ARGV) | |
7643 | Count the arguments in ARGV, assuming it is terminated by a null | |
7644 | pointer. | |
7645 | ||
7646 | For an example of how these functions might be used, see the source | |
7647 | code for the function scm_shell in libguile/script.c. | |
7648 | ||
7649 | You will usually want to use scm_shell instead of calling this | |
7650 | function yourself. | |
7651 | ||
7652 | ** The new function scm_compile_shell_switches turns an array of | |
7653 | command-line arguments into Scheme code to carry out the actions they | |
7654 | describe. Given ARGC and ARGV, it returns a Scheme expression to | |
7655 | evaluate, and calls scm_set_program_arguments to make any remaining | |
7656 | command-line arguments available to the Scheme code. For example, | |
7657 | given the following arguments: | |
7658 | ||
7659 | -e main -s ekko a speckled gecko | |
7660 | ||
7661 | scm_set_program_arguments will return the following expression: | |
7662 | ||
7663 | (begin (load "ekko") (main (command-line)) (quit)) | |
7664 | ||
7665 | You will usually want to use scm_shell instead of calling this | |
7666 | function yourself. | |
7667 | ||
7668 | ** The function scm_shell_usage prints a usage message appropriate for | |
7669 | an interpreter that uses scm_compile_shell_switches to handle its | |
7670 | command-line arguments. | |
7671 | ||
7672 | void scm_shell_usage (int FATAL, char *MESSAGE) | |
7673 | Print a usage message to the standard error output. If MESSAGE is | |
7674 | non-zero, write it before the usage message, followed by a newline. | |
7675 | If FATAL is non-zero, exit the process, using FATAL as the | |
7676 | termination status. (If you want to be compatible with Guile, | |
7677 | always use 1 as the exit status when terminating due to command-line | |
7678 | usage problems.) | |
7679 | ||
7680 | You will usually want to use scm_shell instead of calling this | |
7681 | function yourself. | |
48d224d7 JB |
7682 | |
7683 | ** scm_eval_0str now returns SCM_UNSPECIFIED if the string contains no | |
095936d2 JB |
7684 | expressions. It used to return SCM_EOL. Earth-shattering. |
7685 | ||
7686 | ** The macros for declaring scheme objects in C code have been | |
7687 | rearranged slightly. They are now: | |
7688 | ||
7689 | SCM_SYMBOL (C_NAME, SCHEME_NAME) | |
7690 | Declare a static SCM variable named C_NAME, and initialize it to | |
7691 | point to the Scheme symbol whose name is SCHEME_NAME. C_NAME should | |
7692 | be a C identifier, and SCHEME_NAME should be a C string. | |
7693 | ||
7694 | SCM_GLOBAL_SYMBOL (C_NAME, SCHEME_NAME) | |
7695 | Just like SCM_SYMBOL, but make C_NAME globally visible. | |
7696 | ||
7697 | SCM_VCELL (C_NAME, SCHEME_NAME) | |
7698 | Create a global variable at the Scheme level named SCHEME_NAME. | |
7699 | Declare a static SCM variable named C_NAME, and initialize it to | |
7700 | point to the Scheme variable's value cell. | |
7701 | ||
7702 | SCM_GLOBAL_VCELL (C_NAME, SCHEME_NAME) | |
7703 | Just like SCM_VCELL, but make C_NAME globally visible. | |
7704 | ||
7705 | The `guile-snarf' script writes initialization code for these macros | |
7706 | to its standard output, given C source code as input. | |
7707 | ||
7708 | The SCM_GLOBAL macro is gone. | |
7709 | ||
7710 | ** The scm_read_line and scm_read_line_x functions have been replaced | |
7711 | by Scheme code based on the %read-delimited! procedure (known to C | |
7712 | code as scm_read_delimited_x). See its description above for more | |
7713 | information. | |
48d224d7 | 7714 | |
095936d2 JB |
7715 | ** The function scm_sys_open has been renamed to scm_open. It now |
7716 | returns a port instead of an FD object. | |
ea00ecba | 7717 | |
095936d2 JB |
7718 | * The dynamic linking support has changed. For more information, see |
7719 | libguile/DYNAMIC-LINKING. | |
ea00ecba | 7720 | |
f7b47737 JB |
7721 | \f |
7722 | Guile 1.0b3 | |
3065a62a | 7723 | |
f3b1485f JB |
7724 | User-visible changes from Thursday, September 5, 1996 until Guile 1.0 |
7725 | (Sun 5 Jan 1997): | |
3065a62a | 7726 | |
4b521edb | 7727 | * Changes to the 'guile' program: |
3065a62a | 7728 | |
4b521edb JB |
7729 | ** Guile now loads some new files when it starts up. Guile first |
7730 | searches the load path for init.scm, and loads it if found. Then, if | |
7731 | Guile is not being used to execute a script, and the user's home | |
7732 | directory contains a file named `.guile', Guile loads that. | |
c6486f8a | 7733 | |
4b521edb | 7734 | ** You can now use Guile as a shell script interpreter. |
3065a62a JB |
7735 | |
7736 | To paraphrase the SCSH manual: | |
7737 | ||
7738 | When Unix tries to execute an executable file whose first two | |
7739 | characters are the `#!', it treats the file not as machine code to | |
7740 | be directly executed by the native processor, but as source code | |
7741 | to be executed by some interpreter. The interpreter to use is | |
7742 | specified immediately after the #! sequence on the first line of | |
7743 | the source file. The kernel reads in the name of the interpreter, | |
7744 | and executes that instead. It passes the interpreter the source | |
7745 | filename as its first argument, with the original arguments | |
7746 | following. Consult the Unix man page for the `exec' system call | |
7747 | for more information. | |
7748 | ||
1a1945be JB |
7749 | Now you can use Guile as an interpreter, using a mechanism which is a |
7750 | compatible subset of that provided by SCSH. | |
7751 | ||
3065a62a JB |
7752 | Guile now recognizes a '-s' command line switch, whose argument is the |
7753 | name of a file of Scheme code to load. It also treats the two | |
7754 | characters `#!' as the start of a comment, terminated by `!#'. Thus, | |
7755 | to make a file of Scheme code directly executable by Unix, insert the | |
7756 | following two lines at the top of the file: | |
7757 | ||
7758 | #!/usr/local/bin/guile -s | |
7759 | !# | |
7760 | ||
7761 | Guile treats the argument of the `-s' command-line switch as the name | |
7762 | of a file of Scheme code to load, and treats the sequence `#!' as the | |
7763 | start of a block comment, terminated by `!#'. | |
7764 | ||
7765 | For example, here's a version of 'echo' written in Scheme: | |
7766 | ||
7767 | #!/usr/local/bin/guile -s | |
7768 | !# | |
7769 | (let loop ((args (cdr (program-arguments)))) | |
7770 | (if (pair? args) | |
7771 | (begin | |
7772 | (display (car args)) | |
7773 | (if (pair? (cdr args)) | |
7774 | (display " ")) | |
7775 | (loop (cdr args))))) | |
7776 | (newline) | |
7777 | ||
7778 | Why does `#!' start a block comment terminated by `!#', instead of the | |
7779 | end of the line? That is the notation SCSH uses, and although we | |
7780 | don't yet support the other SCSH features that motivate that choice, | |
7781 | we would like to be backward-compatible with any existing Guile | |
3763761c JB |
7782 | scripts once we do. Furthermore, if the path to Guile on your system |
7783 | is too long for your kernel, you can start the script with this | |
7784 | horrible hack: | |
7785 | ||
7786 | #!/bin/sh | |
7787 | exec /really/long/path/to/guile -s "$0" ${1+"$@"} | |
7788 | !# | |
3065a62a JB |
7789 | |
7790 | Note that some very old Unix systems don't support the `#!' syntax. | |
7791 | ||
c6486f8a | 7792 | |
4b521edb | 7793 | ** You can now run Guile without installing it. |
6685dc83 JB |
7794 | |
7795 | Previous versions of the interactive Guile interpreter (`guile') | |
7796 | couldn't start up unless Guile's Scheme library had been installed; | |
7797 | they used the value of the environment variable `SCHEME_LOAD_PATH' | |
7798 | later on in the startup process, but not to find the startup code | |
7799 | itself. Now Guile uses `SCHEME_LOAD_PATH' in all searches for Scheme | |
7800 | code. | |
7801 | ||
7802 | To run Guile without installing it, build it in the normal way, and | |
7803 | then set the environment variable `SCHEME_LOAD_PATH' to a | |
7804 | colon-separated list of directories, including the top-level directory | |
7805 | of the Guile sources. For example, if you unpacked Guile so that the | |
7806 | full filename of this NEWS file is /home/jimb/guile-1.0b3/NEWS, then | |
7807 | you might say | |
7808 | ||
7809 | export SCHEME_LOAD_PATH=/home/jimb/my-scheme:/home/jimb/guile-1.0b3 | |
7810 | ||
c6486f8a | 7811 | |
4b521edb JB |
7812 | ** Guile's read-eval-print loop no longer prints #<unspecified> |
7813 | results. If the user wants to see this, she can evaluate the | |
7814 | expression (assert-repl-print-unspecified #t), perhaps in her startup | |
48d224d7 | 7815 | file. |
6685dc83 | 7816 | |
4b521edb JB |
7817 | ** Guile no longer shows backtraces by default when an error occurs; |
7818 | however, it does display a message saying how to get one, and how to | |
7819 | request that they be displayed by default. After an error, evaluate | |
7820 | (backtrace) | |
7821 | to see a backtrace, and | |
7822 | (debug-enable 'backtrace) | |
7823 | to see them by default. | |
6685dc83 | 7824 | |
6685dc83 | 7825 | |
d9fb83d9 | 7826 | |
4b521edb JB |
7827 | * Changes to Guile Scheme: |
7828 | ||
7829 | ** Guile now distinguishes between #f and the empty list. | |
7830 | ||
7831 | This is for compatibility with the IEEE standard, the (possibly) | |
7832 | upcoming Revised^5 Report on Scheme, and many extant Scheme | |
7833 | implementations. | |
7834 | ||
7835 | Guile used to have #f and '() denote the same object, to make Scheme's | |
7836 | type system more compatible with Emacs Lisp's. However, the change | |
7837 | caused too much trouble for Scheme programmers, and we found another | |
7838 | way to reconcile Emacs Lisp with Scheme that didn't require this. | |
7839 | ||
7840 | ||
7841 | ** Guile's delq, delv, delete functions, and their destructive | |
c6486f8a JB |
7842 | counterparts, delq!, delv!, and delete!, now remove all matching |
7843 | elements from the list, not just the first. This matches the behavior | |
7844 | of the corresponding Emacs Lisp functions, and (I believe) the Maclisp | |
7845 | functions which inspired them. | |
7846 | ||
7847 | I recognize that this change may break code in subtle ways, but it | |
7848 | seems best to make the change before the FSF's first Guile release, | |
7849 | rather than after. | |
7850 | ||
7851 | ||
4b521edb | 7852 | ** The compiled-library-path function has been deleted from libguile. |
6685dc83 | 7853 | |
4b521edb | 7854 | ** The facilities for loading Scheme source files have changed. |
c6486f8a | 7855 | |
4b521edb | 7856 | *** The variable %load-path now tells Guile which directories to search |
6685dc83 JB |
7857 | for Scheme code. Its value is a list of strings, each of which names |
7858 | a directory. | |
7859 | ||
4b521edb JB |
7860 | *** The variable %load-extensions now tells Guile which extensions to |
7861 | try appending to a filename when searching the load path. Its value | |
7862 | is a list of strings. Its default value is ("" ".scm"). | |
7863 | ||
7864 | *** (%search-load-path FILENAME) searches the directories listed in the | |
7865 | value of the %load-path variable for a Scheme file named FILENAME, | |
7866 | with all the extensions listed in %load-extensions. If it finds a | |
7867 | match, then it returns its full filename. If FILENAME is absolute, it | |
7868 | returns it unchanged. Otherwise, it returns #f. | |
6685dc83 | 7869 | |
4b521edb JB |
7870 | %search-load-path will not return matches that refer to directories. |
7871 | ||
7872 | *** (primitive-load FILENAME :optional CASE-INSENSITIVE-P SHARP) | |
7873 | uses %seach-load-path to find a file named FILENAME, and loads it if | |
7874 | it finds it. If it can't read FILENAME for any reason, it throws an | |
7875 | error. | |
6685dc83 JB |
7876 | |
7877 | The arguments CASE-INSENSITIVE-P and SHARP are interpreted as by the | |
4b521edb JB |
7878 | `read' function. |
7879 | ||
7880 | *** load uses the same searching semantics as primitive-load. | |
7881 | ||
7882 | *** The functions %try-load, try-load-with-path, %load, load-with-path, | |
7883 | basic-try-load-with-path, basic-load-with-path, try-load-module-with- | |
7884 | path, and load-module-with-path have been deleted. The functions | |
7885 | above should serve their purposes. | |
7886 | ||
7887 | *** If the value of the variable %load-hook is a procedure, | |
7888 | `primitive-load' applies its value to the name of the file being | |
7889 | loaded (without the load path directory name prepended). If its value | |
7890 | is #f, it is ignored. Otherwise, an error occurs. | |
7891 | ||
7892 | This is mostly useful for printing load notification messages. | |
7893 | ||
7894 | ||
7895 | ** The function `eval!' is no longer accessible from the scheme level. | |
7896 | We can't allow operations which introduce glocs into the scheme level, | |
7897 | because Guile's type system can't handle these as data. Use `eval' or | |
7898 | `read-and-eval!' (see below) as replacement. | |
7899 | ||
7900 | ** The new function read-and-eval! reads an expression from PORT, | |
7901 | evaluates it, and returns the result. This is more efficient than | |
7902 | simply calling `read' and `eval', since it is not necessary to make a | |
7903 | copy of the expression for the evaluator to munge. | |
7904 | ||
7905 | Its optional arguments CASE_INSENSITIVE_P and SHARP are interpreted as | |
7906 | for the `read' function. | |
7907 | ||
7908 | ||
7909 | ** The function `int?' has been removed; its definition was identical | |
7910 | to that of `integer?'. | |
7911 | ||
7912 | ** The functions `<?', `<?', `<=?', `=?', `>?', and `>=?'. Code should | |
7913 | use the R4RS names for these functions. | |
7914 | ||
7915 | ** The function object-properties no longer returns the hash handle; | |
7916 | it simply returns the object's property list. | |
7917 | ||
7918 | ** Many functions have been changed to throw errors, instead of | |
7919 | returning #f on failure. The point of providing exception handling in | |
7920 | the language is to simplify the logic of user code, but this is less | |
7921 | useful if Guile's primitives don't throw exceptions. | |
7922 | ||
7923 | ** The function `fileno' has been renamed from `%fileno'. | |
7924 | ||
7925 | ** The function primitive-mode->fdes returns #t or #f now, not 1 or 0. | |
7926 | ||
7927 | ||
7928 | * Changes to Guile's C interface: | |
7929 | ||
7930 | ** The library's initialization procedure has been simplified. | |
7931 | scm_boot_guile now has the prototype: | |
7932 | ||
7933 | void scm_boot_guile (int ARGC, | |
7934 | char **ARGV, | |
7935 | void (*main_func) (), | |
7936 | void *closure); | |
7937 | ||
7938 | scm_boot_guile calls MAIN_FUNC, passing it CLOSURE, ARGC, and ARGV. | |
7939 | MAIN_FUNC should do all the work of the program (initializing other | |
7940 | packages, reading user input, etc.) before returning. When MAIN_FUNC | |
7941 | returns, call exit (0); this function never returns. If you want some | |
7942 | other exit value, MAIN_FUNC may call exit itself. | |
7943 | ||
7944 | scm_boot_guile arranges for program-arguments to return the strings | |
7945 | given by ARGC and ARGV. If MAIN_FUNC modifies ARGC/ARGV, should call | |
7946 | scm_set_program_arguments with the final list, so Scheme code will | |
7947 | know which arguments have been processed. | |
7948 | ||
7949 | scm_boot_guile establishes a catch-all catch handler which prints an | |
7950 | error message and exits the process. This means that Guile exits in a | |
7951 | coherent way when system errors occur and the user isn't prepared to | |
7952 | handle it. If the user doesn't like this behavior, they can establish | |
7953 | their own universal catcher in MAIN_FUNC to shadow this one. | |
7954 | ||
7955 | Why must the caller do all the real work from MAIN_FUNC? The garbage | |
7956 | collector assumes that all local variables of type SCM will be above | |
7957 | scm_boot_guile's stack frame on the stack. If you try to manipulate | |
7958 | SCM values after this function returns, it's the luck of the draw | |
7959 | whether the GC will be able to find the objects you allocate. So, | |
7960 | scm_boot_guile function exits, rather than returning, to discourage | |
7961 | people from making that mistake. | |
7962 | ||
7963 | The IN, OUT, and ERR arguments were removed; there are other | |
7964 | convenient ways to override these when desired. | |
7965 | ||
7966 | The RESULT argument was deleted; this function should never return. | |
7967 | ||
7968 | The BOOT_CMD argument was deleted; the MAIN_FUNC argument is more | |
7969 | general. | |
7970 | ||
7971 | ||
7972 | ** Guile's header files should no longer conflict with your system's | |
7973 | header files. | |
7974 | ||
7975 | In order to compile code which #included <libguile.h>, previous | |
7976 | versions of Guile required you to add a directory containing all the | |
7977 | Guile header files to your #include path. This was a problem, since | |
7978 | Guile's header files have names which conflict with many systems' | |
7979 | header files. | |
7980 | ||
7981 | Now only <libguile.h> need appear in your #include path; you must | |
7982 | refer to all Guile's other header files as <libguile/mumble.h>. | |
7983 | Guile's installation procedure puts libguile.h in $(includedir), and | |
7984 | the rest in $(includedir)/libguile. | |
7985 | ||
7986 | ||
7987 | ** Two new C functions, scm_protect_object and scm_unprotect_object, | |
7988 | have been added to the Guile library. | |
7989 | ||
7990 | scm_protect_object (OBJ) protects OBJ from the garbage collector. | |
7991 | OBJ will not be freed, even if all other references are dropped, | |
7992 | until someone does scm_unprotect_object (OBJ). Both functions | |
7993 | return OBJ. | |
7994 | ||
7995 | Note that calls to scm_protect_object do not nest. You can call | |
7996 | scm_protect_object any number of times on a given object, and the | |
7997 | next call to scm_unprotect_object will unprotect it completely. | |
7998 | ||
7999 | Basically, scm_protect_object and scm_unprotect_object just | |
8000 | maintain a list of references to things. Since the GC knows about | |
8001 | this list, all objects it mentions stay alive. scm_protect_object | |
8002 | adds its argument to the list; scm_unprotect_object remove its | |
8003 | argument from the list. | |
8004 | ||
8005 | ||
8006 | ** scm_eval_0str now returns the value of the last expression | |
8007 | evaluated. | |
8008 | ||
8009 | ** The new function scm_read_0str reads an s-expression from a | |
8010 | null-terminated string, and returns it. | |
8011 | ||
8012 | ** The new function `scm_stdio_to_port' converts a STDIO file pointer | |
8013 | to a Scheme port object. | |
8014 | ||
8015 | ** The new function `scm_set_program_arguments' allows C code to set | |
e80c8fea | 8016 | the value returned by the Scheme `program-arguments' function. |
6685dc83 | 8017 | |
6685dc83 | 8018 | \f |
1a1945be JB |
8019 | Older changes: |
8020 | ||
8021 | * Guile no longer includes sophisticated Tcl/Tk support. | |
8022 | ||
8023 | The old Tcl/Tk support was unsatisfying to us, because it required the | |
8024 | user to link against the Tcl library, as well as Tk and Guile. The | |
8025 | interface was also un-lispy, in that it preserved Tcl/Tk's practice of | |
8026 | referring to widgets by names, rather than exporting widgets to Scheme | |
8027 | code as a special datatype. | |
8028 | ||
8029 | In the Usenix Tk Developer's Workshop held in July 1996, the Tcl/Tk | |
8030 | maintainers described some very interesting changes in progress to the | |
8031 | Tcl/Tk internals, which would facilitate clean interfaces between lone | |
8032 | Tk and other interpreters --- even for garbage-collected languages | |
8033 | like Scheme. They expected the new Tk to be publicly available in the | |
8034 | fall of 1996. | |
8035 | ||
8036 | Since it seems that Guile might soon have a new, cleaner interface to | |
8037 | lone Tk, and that the old Guile/Tk glue code would probably need to be | |
8038 | completely rewritten, we (Jim Blandy and Richard Stallman) have | |
8039 | decided not to support the old code. We'll spend the time instead on | |
8040 | a good interface to the newer Tk, as soon as it is available. | |
5c54da76 | 8041 | |
8512dea6 | 8042 | Until then, gtcltk-lib provides trivial, low-maintenance functionality. |
deb95d71 | 8043 | |
5c54da76 JB |
8044 | \f |
8045 | Copyright information: | |
8046 | ||
4f416616 | 8047 | Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2006 Free Software Foundation, Inc. |
5c54da76 JB |
8048 | |
8049 | Permission is granted to anyone to make or distribute verbatim copies | |
8050 | of this document as received, in any medium, provided that the | |
8051 | copyright notice and this permission notice are preserved, | |
8052 | thus giving the recipient permission to redistribute in turn. | |
8053 | ||
8054 | Permission is granted to distribute modified versions | |
8055 | of this document, or of portions of it, | |
8056 | under the above conditions, provided also that they | |
8057 | carry prominent notices stating who last changed them. | |
8058 | ||
48d224d7 JB |
8059 | \f |
8060 | Local variables: | |
8061 | mode: outline | |
8062 | paragraph-separate: "[ \f]*$" | |
8063 | end: |