Commit | Line | Data |
---|---|---|
f7b47737 | 1 | Guile NEWS --- history of user-visible changes. -*- text -*- |
d23bbf3e | 2 | Copyright (C) 1996, 1997, 1998 Free Software Foundation, Inc. |
5c54da76 JB |
3 | See the end for copying conditions. |
4 | ||
e1b6c710 | 5 | Please send Guile bug reports to bug-guile@gnu.org. |
5c54da76 | 6 | \f |
f3227c7a JB |
7 | Changes since Guile 1.3: |
8 | ||
e4eae9b1 MD |
9 | * Changes to the stand-alone interpreter |
10 | ||
b3a941b9 MD |
11 | ** New options interface: readline-options, |
12 | readline-enable, readline-disable, readline-set! | |
13 | ||
e4eae9b1 MD |
14 | ** Command line history is now restored from and saved to file |
15 | ||
b3a941b9 MD |
16 | If readline is used and the readline option `history-file' is enabled, |
17 | the command line history is read from file when the interpreter is | |
e4eae9b1 MD |
18 | entered, and written to file on exit. The filename used can be |
19 | specified with the environment variable GUILE_HISTORY. Default file | |
20 | name is "$HOME/.guile_history". Nothing special happens if errors | |
21 | occur during read or write. | |
22 | ||
23 | ** Command line history length can now be customized. | |
b3a941b9 | 24 | Command line history length is now controlled by the readline option |
e4eae9b1 MD |
25 | `history-length'. Default is 200 lines. |
26 | ||
67ad463a MD |
27 | ** All builtins now print as primitives. |
28 | Previously builtin procedures not belonging to the fundamental subr | |
29 | types printed as #<compiled closure #<primitive-procedure gsubr-apply>>. | |
30 | Now, they print as #<primitive-procedure NAME>. | |
31 | ||
32 | ** Backtraces slightly more intelligible. | |
33 | gsubr-apply and macro transformer application frames no longer appear | |
34 | in backtraces. | |
35 | ||
69c6acbb JB |
36 | * Changes to Scheme functions and syntax |
37 | ||
ed8c8636 MD |
38 | ** New function: sorted? SEQUENCE LESS? |
39 | Returns `#t' when the sequence argument is in non-decreasing order | |
40 | according to LESS? (that is, there is no adjacent pair `... x y | |
41 | ...' for which `(less? y x)'). | |
42 | ||
43 | Returns `#f' when the sequence contains at least one out-of-order | |
44 | pair. It is an error if the sequence is neither a list nor a | |
45 | vector. | |
46 | ||
47 | ** New function: merge LIST1 LIST2 LESS? | |
48 | LIST1 and LIST2 are sorted lists. | |
49 | Returns the sorted list of all elements in LIST1 and LIST2. | |
50 | ||
51 | Assume that the elements a and b1 in LIST1 and b2 in LIST2 are "equal" | |
52 | in the sense that (LESS? x y) --> #f for x, y in {a, b1, b2}, | |
53 | and that a < b1 in LIST1. Then a < b1 < b2 in the result. | |
54 | (Here "<" should read "comes before".) | |
55 | ||
56 | ** New procedure: merge! LIST1 LIST2 LESS? | |
57 | Merges two lists, re-using the pairs of LIST1 and LIST2 to build | |
58 | the result. If the code is compiled, and LESS? constructs no new | |
59 | pairs, no pairs at all will be allocated. The first pair of the | |
60 | result will be either the first pair of LIST1 or the first pair of | |
61 | LIST2. | |
62 | ||
63 | ** New function: sort SEQUENCE LESS? | |
64 | Accepts either a list or a vector, and returns a new sequence | |
65 | which is sorted. The new sequence is the same type as the input. | |
66 | Always `(sorted? (sort sequence less?) less?)'. The original | |
67 | sequence is not altered in any way. The new sequence shares its | |
68 | elements with the old one; no elements are copied. | |
69 | ||
70 | ** New procedure: sort! SEQUENCE LESS | |
71 | Returns its sorted result in the original boxes. No new storage is | |
72 | allocated at all. Proper usage: (set! slist (sort! slist <)) | |
73 | ||
74 | ** New function: stable-sort SEQUENCE LESS? | |
75 | Similar to `sort' but stable. That is, if "equal" elements are | |
76 | ordered a < b in the original sequence, they will have the same order | |
77 | in the result. | |
78 | ||
79 | ** New function: stable-sort! SEQUENCE LESS? | |
80 | Similar to `sort!' but stable. | |
81 | Uses temporary storage when sorting vectors. | |
82 | ||
83 | ** New functions: sort-list, sort-list! | |
84 | Added for compatibility with scsh. | |
85 | ||
69c6acbb JB |
86 | ** The range of logand, logior, logxor, logtest, and logbit? have changed. |
87 | ||
88 | These functions now operate on numbers in the range of a C unsigned | |
89 | long. | |
90 | ||
91 | These functions used to operate on numbers in the range of a C signed | |
92 | long; however, this seems inappropriate, because Guile integers don't | |
93 | overflow. | |
94 | ||
ba4ee0d6 MD |
95 | ** New function: make-guardian |
96 | This is an implementation of guardians as described in | |
97 | R. Kent Dybvig, Carl Bruggeman, and David Eby (1993) "Guardians in a | |
98 | Generation-Based Garbage Collector" ACM SIGPLAN Conference on | |
99 | Programming Language Design and Implementation, June 1993 | |
100 | ftp://ftp.cs.indiana.edu/pub/scheme-repository/doc/pubs/guardians.ps.gz | |
101 | ||
88ceea5c MD |
102 | ** New functions: delq1!, delv1!, delete1! |
103 | These procedures behave similar to delq! and friends but delete only | |
104 | one object if at all. | |
105 | ||
55254a6a MD |
106 | ** New function: unread-string STRING PORT |
107 | Unread STRING to PORT, that is, push it back onto the port so that | |
108 | next read operation will work on the pushed back characters. | |
109 | ||
110 | ** unread-char can now be called multiple times | |
111 | If unread-char is called multiple times, the unread characters will be | |
112 | read again in last-in first-out order. | |
113 | ||
67ad463a | 114 | ** New function: map-in-order PROC LIST1 LIST2 ... |
d41b3904 MD |
115 | Version of `map' which guarantees that the procedure is applied to the |
116 | lists in serial order. | |
117 | ||
67ad463a MD |
118 | ** Renamed `serial-array-copy!' and `serial-array-map!' to |
119 | `array-copy-in-order!' and `array-map-in-order!'. The old names are | |
120 | now obsolete and will go away in release 1.5. | |
121 | ||
cf7132b3 | 122 | ** New syntax: collect BODY1 ... |
d41b3904 MD |
123 | Version of `begin' which returns a list of the results of the body |
124 | forms instead of the result of the last body form. In contrast to | |
cf7132b3 | 125 | `begin', `collect' allows an empty body. |
d41b3904 | 126 | |
e4eae9b1 MD |
127 | ** New functions: read-history FILENAME, write-history FILENAME |
128 | Read/write command line history from/to file. Returns #t on success | |
129 | and #f if an error occured. | |
130 | ||
3ffc7a36 MD |
131 | * Changes to the gh_ interface |
132 | ||
133 | ** gh_scm2doubles | |
134 | ||
135 | Now takes a second argument which is the result array. If this | |
136 | pointer is NULL, a new array is malloced (the old behaviour). | |
137 | ||
138 | ** gh_chars2byvect, gh_shorts2svect, gh_floats2fvect, gh_scm2chars, | |
139 | gh_scm2shorts, gh_scm2longs, gh_scm2floats | |
140 | ||
141 | New functions. | |
142 | ||
f3227c7a | 143 | \f |
d23bbf3e | 144 | Changes in Guile 1.3 (released Monday, October 19, 1998): |
c484bf7f JB |
145 | |
146 | * Changes to the distribution | |
147 | ||
e2d6569c JB |
148 | ** We renamed the SCHEME_LOAD_PATH environment variable to GUILE_LOAD_PATH. |
149 | To avoid conflicts, programs should name environment variables after | |
150 | themselves, except when there's a common practice establishing some | |
151 | other convention. | |
152 | ||
153 | For now, Guile supports both GUILE_LOAD_PATH and SCHEME_LOAD_PATH, | |
154 | giving the former precedence, and printing a warning message if the | |
155 | latter is set. Guile 1.4 will not recognize SCHEME_LOAD_PATH at all. | |
156 | ||
157 | ** The header files related to multi-byte characters have been removed. | |
158 | They were: libguile/extchrs.h and libguile/mbstrings.h. Any C code | |
159 | which referred to these explicitly will probably need to be rewritten, | |
160 | since the support for the variant string types has been removed; see | |
161 | below. | |
162 | ||
163 | ** The header files append.h and sequences.h have been removed. These | |
164 | files implemented non-R4RS operations which would encourage | |
165 | non-portable programming style and less easy-to-read code. | |
3a97e020 | 166 | |
c484bf7f JB |
167 | * Changes to the stand-alone interpreter |
168 | ||
2e368582 | 169 | ** New procedures have been added to implement a "batch mode": |
ec4ab4fd | 170 | |
2e368582 | 171 | *** Function: batch-mode? |
ec4ab4fd GH |
172 | |
173 | Returns a boolean indicating whether the interpreter is in batch | |
174 | mode. | |
175 | ||
2e368582 | 176 | *** Function: set-batch-mode?! ARG |
ec4ab4fd GH |
177 | |
178 | If ARG is true, switches the interpreter to batch mode. The `#f' | |
179 | case has not been implemented. | |
180 | ||
2e368582 JB |
181 | ** Guile now provides full command-line editing, when run interactively. |
182 | To use this feature, you must have the readline library installed. | |
183 | The Guile build process will notice it, and automatically include | |
184 | support for it. | |
185 | ||
186 | The readline library is available via anonymous FTP from any GNU | |
187 | mirror site; the canonical location is "ftp://prep.ai.mit.edu/pub/gnu". | |
188 | ||
a5d6d578 MD |
189 | ** the-last-stack is now a fluid. |
190 | ||
c484bf7f JB |
191 | * Changes to the procedure for linking libguile with your programs |
192 | ||
71f20534 | 193 | ** You can now use the `guile-config' utility to build programs that use Guile. |
2e368582 | 194 | |
2adfe1c0 | 195 | Guile now includes a command-line utility called `guile-config', which |
71f20534 JB |
196 | can provide information about how to compile and link programs that |
197 | use Guile. | |
198 | ||
199 | *** `guile-config compile' prints any C compiler flags needed to use Guile. | |
200 | You should include this command's output on the command line you use | |
201 | to compile C or C++ code that #includes the Guile header files. It's | |
202 | usually just a `-I' flag to help the compiler find the Guile headers. | |
203 | ||
204 | ||
205 | *** `guile-config link' prints any linker flags necessary to link with Guile. | |
8aa5c148 | 206 | |
71f20534 | 207 | This command writes to its standard output a list of flags which you |
8aa5c148 JB |
208 | must pass to the linker to link your code against the Guile library. |
209 | The flags include '-lguile' itself, any other libraries the Guile | |
210 | library depends upon, and any `-L' flags needed to help the linker | |
211 | find those libraries. | |
2e368582 JB |
212 | |
213 | For example, here is a Makefile rule that builds a program named 'foo' | |
214 | from the object files ${FOO_OBJECTS}, and links them against Guile: | |
215 | ||
216 | foo: ${FOO_OBJECTS} | |
2adfe1c0 | 217 | ${CC} ${CFLAGS} ${FOO_OBJECTS} `guile-config link` -o foo |
2e368582 | 218 | |
e2d6569c JB |
219 | Previous Guile releases recommended that you use autoconf to detect |
220 | which of a predefined set of libraries were present on your system. | |
2adfe1c0 | 221 | It is more robust to use `guile-config', since it records exactly which |
e2d6569c JB |
222 | libraries the installed Guile library requires. |
223 | ||
2adfe1c0 JB |
224 | This was originally called `build-guile', but was renamed to |
225 | `guile-config' before Guile 1.3 was released, to be consistent with | |
226 | the analogous script for the GTK+ GUI toolkit, which is called | |
227 | `gtk-config'. | |
228 | ||
2e368582 | 229 | |
8aa5c148 JB |
230 | ** Use the GUILE_FLAGS macro in your configure.in file to find Guile. |
231 | ||
232 | If you are using the GNU autoconf package to configure your program, | |
233 | you can use the GUILE_FLAGS autoconf macro to call `guile-config' | |
234 | (described above) and gather the necessary values for use in your | |
235 | Makefiles. | |
236 | ||
237 | The GUILE_FLAGS macro expands to configure script code which runs the | |
238 | `guile-config' script, to find out where Guile's header files and | |
239 | libraries are installed. It sets two variables, marked for | |
240 | substitution, as by AC_SUBST. | |
241 | ||
242 | GUILE_CFLAGS --- flags to pass to a C or C++ compiler to build | |
243 | code that uses Guile header files. This is almost always just a | |
244 | -I flag. | |
245 | ||
246 | GUILE_LDFLAGS --- flags to pass to the linker to link a | |
247 | program against Guile. This includes `-lguile' for the Guile | |
248 | library itself, any libraries that Guile itself requires (like | |
249 | -lqthreads), and so on. It may also include a -L flag to tell the | |
250 | compiler where to find the libraries. | |
251 | ||
252 | GUILE_FLAGS is defined in the file guile.m4, in the top-level | |
253 | directory of the Guile distribution. You can copy it into your | |
254 | package's aclocal.m4 file, and then use it in your configure.in file. | |
255 | ||
256 | If you are using the `aclocal' program, distributed with GNU automake, | |
257 | to maintain your aclocal.m4 file, the Guile installation process | |
258 | installs guile.m4 where aclocal will find it. All you need to do is | |
259 | use GUILE_FLAGS in your configure.in file, and then run `aclocal'; | |
260 | this will copy the definition of GUILE_FLAGS into your aclocal.m4 | |
261 | file. | |
262 | ||
263 | ||
c484bf7f | 264 | * Changes to Scheme functions and syntax |
7ad3c1e7 | 265 | |
02755d59 | 266 | ** Multi-byte strings have been removed, as have multi-byte and wide |
e2d6569c JB |
267 | ports. We felt that these were the wrong approach to |
268 | internationalization support. | |
02755d59 | 269 | |
2e368582 JB |
270 | ** New function: readline [PROMPT] |
271 | Read a line from the terminal, and allow the user to edit it, | |
272 | prompting with PROMPT. READLINE provides a large set of Emacs-like | |
273 | editing commands, lets the user recall previously typed lines, and | |
274 | works on almost every kind of terminal, including dumb terminals. | |
275 | ||
276 | READLINE assumes that the cursor is at the beginning of the line when | |
277 | it is invoked. Thus, you can't print a prompt yourself, and then call | |
278 | READLINE; you need to package up your prompt as a string, pass it to | |
279 | the function, and let READLINE print the prompt itself. This is | |
280 | because READLINE needs to know the prompt's screen width. | |
281 | ||
8cd57bd0 JB |
282 | For Guile to provide this function, you must have the readline |
283 | library, version 2.1 or later, installed on your system. Readline is | |
284 | available via anonymous FTP from prep.ai.mit.edu in pub/gnu, or from | |
285 | any GNU mirror site. | |
2e368582 JB |
286 | |
287 | See also ADD-HISTORY function. | |
288 | ||
289 | ** New function: add-history STRING | |
290 | Add STRING as the most recent line in the history used by the READLINE | |
291 | command. READLINE does not add lines to the history itself; you must | |
292 | call ADD-HISTORY to make previous input available to the user. | |
293 | ||
8cd57bd0 JB |
294 | ** The behavior of the read-line function has changed. |
295 | ||
296 | This function now uses standard C library functions to read the line, | |
297 | for speed. This means that it doesn not respect the value of | |
298 | scm-line-incrementors; it assumes that lines are delimited with | |
299 | #\newline. | |
300 | ||
301 | (Note that this is read-line, the function that reads a line of text | |
302 | from a port, not readline, the function that reads a line from a | |
303 | terminal, providing full editing capabilities.) | |
304 | ||
1a0106ef JB |
305 | ** New module (ice-9 getopt-gnu-style): Parse command-line arguments. |
306 | ||
307 | This module provides some simple argument parsing. It exports one | |
308 | function: | |
309 | ||
310 | Function: getopt-gnu-style ARG-LS | |
311 | Parse a list of program arguments into an alist of option | |
312 | descriptions. | |
313 | ||
314 | Each item in the list of program arguments is examined to see if | |
315 | it meets the syntax of a GNU long-named option. An argument like | |
316 | `--MUMBLE' produces an element of the form (MUMBLE . #t) in the | |
317 | returned alist, where MUMBLE is a keyword object with the same | |
318 | name as the argument. An argument like `--MUMBLE=FROB' produces | |
319 | an element of the form (MUMBLE . FROB), where FROB is a string. | |
320 | ||
321 | As a special case, the returned alist also contains a pair whose | |
322 | car is the symbol `rest'. The cdr of this pair is a list | |
323 | containing all the items in the argument list that are not options | |
324 | of the form mentioned above. | |
325 | ||
326 | The argument `--' is treated specially: all items in the argument | |
327 | list appearing after such an argument are not examined, and are | |
328 | returned in the special `rest' list. | |
329 | ||
330 | This function does not parse normal single-character switches. | |
331 | You will need to parse them out of the `rest' list yourself. | |
332 | ||
8cd57bd0 JB |
333 | ** The read syntax for byte vectors and short vectors has changed. |
334 | ||
335 | Instead of #bytes(...), write #y(...). | |
336 | ||
337 | Instead of #short(...), write #h(...). | |
338 | ||
339 | This may seem nutty, but, like the other uniform vectors, byte vectors | |
340 | and short vectors want to have the same print and read syntax (and, | |
341 | more basic, want to have read syntax!). Changing the read syntax to | |
342 | use multiple characters after the hash sign breaks with the | |
343 | conventions used in R5RS and the conventions used for the other | |
344 | uniform vectors. It also introduces complexity in the current reader, | |
345 | both on the C and Scheme levels. (The Right solution is probably to | |
346 | change the syntax and prototypes for uniform vectors entirely.) | |
347 | ||
348 | ||
349 | ** The new module (ice-9 session) provides useful interactive functions. | |
350 | ||
351 | *** New procedure: (apropos REGEXP OPTION ...) | |
352 | ||
353 | Display a list of top-level variables whose names match REGEXP, and | |
354 | the modules they are imported from. Each OPTION should be one of the | |
355 | following symbols: | |
356 | ||
357 | value --- Show the value of each matching variable. | |
358 | shadow --- Show bindings shadowed by subsequently imported modules. | |
359 | full --- Same as both `shadow' and `value'. | |
360 | ||
361 | For example: | |
362 | ||
363 | guile> (apropos "trace" 'full) | |
364 | debug: trace #<procedure trace args> | |
365 | debug: untrace #<procedure untrace args> | |
366 | the-scm-module: display-backtrace #<compiled-closure #<primitive-procedure gsubr-apply>> | |
367 | the-scm-module: before-backtrace-hook () | |
368 | the-scm-module: backtrace #<primitive-procedure backtrace> | |
369 | the-scm-module: after-backtrace-hook () | |
370 | the-scm-module: has-shown-backtrace-hint? #f | |
371 | guile> | |
372 | ||
373 | ** There are new functions and syntax for working with macros. | |
374 | ||
375 | Guile implements macros as a special object type. Any variable whose | |
376 | top-level binding is a macro object acts as a macro. The macro object | |
377 | specifies how the expression should be transformed before evaluation. | |
378 | ||
379 | *** Macro objects now print in a reasonable way, resembling procedures. | |
380 | ||
381 | *** New function: (macro? OBJ) | |
382 | True iff OBJ is a macro object. | |
383 | ||
384 | *** New function: (primitive-macro? OBJ) | |
385 | Like (macro? OBJ), but true only if OBJ is one of the Guile primitive | |
386 | macro transformers, implemented in eval.c rather than Scheme code. | |
387 | ||
dbdd0c16 JB |
388 | Why do we have this function? |
389 | - For symmetry with procedure? and primitive-procedure?, | |
390 | - to allow custom print procedures to tell whether a macro is | |
391 | primitive, and display it differently, and | |
392 | - to allow compilers and user-written evaluators to distinguish | |
393 | builtin special forms from user-defined ones, which could be | |
394 | compiled. | |
395 | ||
8cd57bd0 JB |
396 | *** New function: (macro-type OBJ) |
397 | Return a value indicating what kind of macro OBJ is. Possible return | |
398 | values are: | |
399 | ||
400 | The symbol `syntax' --- a macro created by procedure->syntax. | |
401 | The symbol `macro' --- a macro created by procedure->macro. | |
402 | The symbol `macro!' --- a macro created by procedure->memoizing-macro. | |
403 | The boolean #f --- if OBJ is not a macro object. | |
404 | ||
405 | *** New function: (macro-name MACRO) | |
406 | Return the name of the macro object MACRO's procedure, as returned by | |
407 | procedure-name. | |
408 | ||
409 | *** New function: (macro-transformer MACRO) | |
410 | Return the transformer procedure for MACRO. | |
411 | ||
412 | *** New syntax: (use-syntax MODULE ... TRANSFORMER) | |
413 | ||
414 | Specify a new macro expander to use in the current module. Each | |
415 | MODULE is a module name, with the same meaning as in the `use-modules' | |
416 | form; each named module's exported bindings are added to the current | |
417 | top-level environment. TRANSFORMER is an expression evaluated in the | |
418 | resulting environment which must yield a procedure to use as the | |
419 | module's eval transformer: every expression evaluated in this module | |
420 | is passed to this function, and the result passed to the Guile | |
421 | interpreter. | |
422 | ||
423 | *** macro-eval! is removed. Use local-eval instead. | |
29521173 | 424 | |
8d9dcb3c MV |
425 | ** Some magic has been added to the printer to better handle user |
426 | written printing routines (like record printers, closure printers). | |
427 | ||
428 | The problem is that these user written routines must have access to | |
7fbd77df | 429 | the current `print-state' to be able to handle fancy things like |
8d9dcb3c MV |
430 | detection of circular references. These print-states have to be |
431 | passed to the builtin printing routines (display, write, etc) to | |
432 | properly continue the print chain. | |
433 | ||
434 | We didn't want to change all existing print code so that it | |
8cd57bd0 | 435 | explicitly passes thru a print state in addition to a port. Instead, |
8d9dcb3c MV |
436 | we extented the possible values that the builtin printing routines |
437 | accept as a `port'. In addition to a normal port, they now also take | |
438 | a pair of a normal port and a print-state. Printing will go to the | |
439 | port and the print-state will be used to control the detection of | |
440 | circular references, etc. If the builtin function does not care for a | |
441 | print-state, it is simply ignored. | |
442 | ||
443 | User written callbacks are now called with such a pair as their | |
444 | `port', but because every function now accepts this pair as a PORT | |
445 | argument, you don't have to worry about that. In fact, it is probably | |
446 | safest to not check for these pairs. | |
447 | ||
448 | However, it is sometimes necessary to continue a print chain on a | |
449 | different port, for example to get a intermediate string | |
450 | representation of the printed value, mangle that string somehow, and | |
451 | then to finally print the mangled string. Use the new function | |
452 | ||
453 | inherit-print-state OLD-PORT NEW-PORT | |
454 | ||
455 | for this. It constructs a new `port' that prints to NEW-PORT but | |
456 | inherits the print-state of OLD-PORT. | |
457 | ||
ef1ea498 MD |
458 | ** struct-vtable-offset renamed to vtable-offset-user |
459 | ||
460 | ** New constants: vtable-index-layout, vtable-index-vtable, vtable-index-printer | |
461 | ||
462 | ** There is now a fourth (optional) argument to make-vtable-vtable and | |
463 | make-struct when constructing new types (vtables). This argument | |
464 | initializes field vtable-index-printer of the vtable. | |
465 | ||
4851dc57 MV |
466 | ** The detection of circular references has been extended to structs. |
467 | That is, a structure that -- in the process of being printed -- prints | |
468 | itself does not lead to infinite recursion. | |
469 | ||
470 | ** There is now some basic support for fluids. Please read | |
471 | "libguile/fluid.h" to find out more. It is accessible from Scheme with | |
472 | the following functions and macros: | |
473 | ||
9c3fb66f MV |
474 | Function: make-fluid |
475 | ||
476 | Create a new fluid object. Fluids are not special variables or | |
477 | some other extension to the semantics of Scheme, but rather | |
478 | ordinary Scheme objects. You can store them into variables (that | |
479 | are still lexically scoped, of course) or into any other place you | |
480 | like. Every fluid has a initial value of `#f'. | |
04c76b58 | 481 | |
9c3fb66f | 482 | Function: fluid? OBJ |
04c76b58 | 483 | |
9c3fb66f | 484 | Test whether OBJ is a fluid. |
04c76b58 | 485 | |
9c3fb66f MV |
486 | Function: fluid-ref FLUID |
487 | Function: fluid-set! FLUID VAL | |
04c76b58 MV |
488 | |
489 | Access/modify the fluid FLUID. Modifications are only visible | |
490 | within the current dynamic root (that includes threads). | |
491 | ||
9c3fb66f MV |
492 | Function: with-fluids* FLUIDS VALUES THUNK |
493 | ||
494 | FLUIDS is a list of fluids and VALUES a corresponding list of | |
495 | values for these fluids. Before THUNK gets called the values are | |
496 | installed in the fluids and the old values of the fluids are | |
497 | saved in the VALUES list. When the flow of control leaves THUNK | |
498 | or reenters it, the values get swapped again. You might think of | |
499 | this as a `safe-fluid-excursion'. Note that the VALUES list is | |
500 | modified by `with-fluids*'. | |
501 | ||
502 | Macro: with-fluids ((FLUID VALUE) ...) FORM ... | |
503 | ||
504 | The same as `with-fluids*' but with a different syntax. It looks | |
505 | just like `let', but both FLUID and VALUE are evaluated. Remember, | |
506 | fluids are not special variables but ordinary objects. FLUID | |
507 | should evaluate to a fluid. | |
04c76b58 | 508 | |
e2d6569c | 509 | ** Changes to system call interfaces: |
64d01d13 | 510 | |
e2d6569c | 511 | *** close-port, close-input-port and close-output-port now return a |
64d01d13 GH |
512 | boolean instead of an `unspecified' object. #t means that the port |
513 | was successfully closed, while #f means it was already closed. It is | |
514 | also now possible for these procedures to raise an exception if an | |
515 | error occurs (some errors from write can be delayed until close.) | |
516 | ||
e2d6569c | 517 | *** the first argument to chmod, fcntl, ftell and fseek can now be a |
6afcd3b2 GH |
518 | file descriptor. |
519 | ||
e2d6569c | 520 | *** the third argument to fcntl is now optional. |
6afcd3b2 | 521 | |
e2d6569c | 522 | *** the first argument to chown can now be a file descriptor or a port. |
6afcd3b2 | 523 | |
e2d6569c | 524 | *** the argument to stat can now be a port. |
6afcd3b2 | 525 | |
e2d6569c | 526 | *** The following new procedures have been added (most use scsh |
64d01d13 GH |
527 | interfaces): |
528 | ||
e2d6569c | 529 | *** procedure: close PORT/FD |
ec4ab4fd GH |
530 | Similar to close-port (*note close-port: Closing Ports.), but also |
531 | works on file descriptors. A side effect of closing a file | |
532 | descriptor is that any ports using that file descriptor are moved | |
533 | to a different file descriptor and have their revealed counts set | |
534 | to zero. | |
535 | ||
e2d6569c | 536 | *** procedure: port->fdes PORT |
ec4ab4fd GH |
537 | Returns the integer file descriptor underlying PORT. As a side |
538 | effect the revealed count of PORT is incremented. | |
539 | ||
e2d6569c | 540 | *** procedure: fdes->ports FDES |
ec4ab4fd GH |
541 | Returns a list of existing ports which have FDES as an underlying |
542 | file descriptor, without changing their revealed counts. | |
543 | ||
e2d6569c | 544 | *** procedure: fdes->inport FDES |
ec4ab4fd GH |
545 | Returns an existing input port which has FDES as its underlying |
546 | file descriptor, if one exists, and increments its revealed count. | |
547 | Otherwise, returns a new input port with a revealed count of 1. | |
548 | ||
e2d6569c | 549 | *** procedure: fdes->outport FDES |
ec4ab4fd GH |
550 | Returns an existing output port which has FDES as its underlying |
551 | file descriptor, if one exists, and increments its revealed count. | |
552 | Otherwise, returns a new output port with a revealed count of 1. | |
553 | ||
554 | The next group of procedures perform a `dup2' system call, if NEWFD | |
555 | (an integer) is supplied, otherwise a `dup'. The file descriptor to be | |
556 | duplicated can be supplied as an integer or contained in a port. The | |
64d01d13 GH |
557 | type of value returned varies depending on which procedure is used. |
558 | ||
ec4ab4fd GH |
559 | All procedures also have the side effect when performing `dup2' that |
560 | any ports using NEWFD are moved to a different file descriptor and have | |
64d01d13 GH |
561 | their revealed counts set to zero. |
562 | ||
e2d6569c | 563 | *** procedure: dup->fdes PORT/FD [NEWFD] |
ec4ab4fd | 564 | Returns an integer file descriptor. |
64d01d13 | 565 | |
e2d6569c | 566 | *** procedure: dup->inport PORT/FD [NEWFD] |
ec4ab4fd | 567 | Returns a new input port using the new file descriptor. |
64d01d13 | 568 | |
e2d6569c | 569 | *** procedure: dup->outport PORT/FD [NEWFD] |
ec4ab4fd | 570 | Returns a new output port using the new file descriptor. |
64d01d13 | 571 | |
e2d6569c | 572 | *** procedure: dup PORT/FD [NEWFD] |
ec4ab4fd GH |
573 | Returns a new port if PORT/FD is a port, with the same mode as the |
574 | supplied port, otherwise returns an integer file descriptor. | |
64d01d13 | 575 | |
e2d6569c | 576 | *** procedure: dup->port PORT/FD MODE [NEWFD] |
ec4ab4fd GH |
577 | Returns a new port using the new file descriptor. MODE supplies a |
578 | mode string for the port (*note open-file: File Ports.). | |
64d01d13 | 579 | |
e2d6569c | 580 | *** procedure: setenv NAME VALUE |
ec4ab4fd GH |
581 | Modifies the environment of the current process, which is also the |
582 | default environment inherited by child processes. | |
64d01d13 | 583 | |
ec4ab4fd GH |
584 | If VALUE is `#f', then NAME is removed from the environment. |
585 | Otherwise, the string NAME=VALUE is added to the environment, | |
586 | replacing any existing string with name matching NAME. | |
64d01d13 | 587 | |
ec4ab4fd | 588 | The return value is unspecified. |
956055a9 | 589 | |
e2d6569c | 590 | *** procedure: truncate-file OBJ SIZE |
6afcd3b2 GH |
591 | Truncates the file referred to by OBJ to at most SIZE bytes. OBJ |
592 | can be a string containing a file name or an integer file | |
593 | descriptor or port open for output on the file. The underlying | |
594 | system calls are `truncate' and `ftruncate'. | |
595 | ||
596 | The return value is unspecified. | |
597 | ||
e2d6569c | 598 | *** procedure: setvbuf PORT MODE [SIZE] |
7a6f1ffa GH |
599 | Set the buffering mode for PORT. MODE can be: |
600 | `_IONBF' | |
601 | non-buffered | |
602 | ||
603 | `_IOLBF' | |
604 | line buffered | |
605 | ||
606 | `_IOFBF' | |
607 | block buffered, using a newly allocated buffer of SIZE bytes. | |
608 | However if SIZE is zero or unspecified, the port will be made | |
609 | non-buffered. | |
610 | ||
611 | This procedure should not be used after I/O has been performed with | |
612 | the port. | |
613 | ||
614 | Ports are usually block buffered by default, with a default buffer | |
615 | size. Procedures e.g., *Note open-file: File Ports, which accept a | |
616 | mode string allow `0' to be added to request an unbuffered port. | |
617 | ||
e2d6569c | 618 | *** procedure: fsync PORT/FD |
6afcd3b2 GH |
619 | Copies any unwritten data for the specified output file descriptor |
620 | to disk. If PORT/FD is a port, its buffer is flushed before the | |
621 | underlying file descriptor is fsync'd. The return value is | |
622 | unspecified. | |
623 | ||
e2d6569c | 624 | *** procedure: open-fdes PATH FLAGS [MODES] |
6afcd3b2 GH |
625 | Similar to `open' but returns a file descriptor instead of a port. |
626 | ||
e2d6569c | 627 | *** procedure: execle PATH ENV [ARG] ... |
6afcd3b2 GH |
628 | Similar to `execl', but the environment of the new process is |
629 | specified by ENV, which must be a list of strings as returned by | |
630 | the `environ' procedure. | |
631 | ||
632 | This procedure is currently implemented using the `execve' system | |
633 | call, but we call it `execle' because of its Scheme calling | |
634 | interface. | |
635 | ||
e2d6569c | 636 | *** procedure: strerror ERRNO |
ec4ab4fd GH |
637 | Returns the Unix error message corresponding to ERRNO, an integer. |
638 | ||
e2d6569c | 639 | *** procedure: primitive-exit [STATUS] |
6afcd3b2 GH |
640 | Terminate the current process without unwinding the Scheme stack. |
641 | This is would typically be useful after a fork. The exit status | |
642 | is STATUS if supplied, otherwise zero. | |
643 | ||
e2d6569c | 644 | *** procedure: times |
6afcd3b2 GH |
645 | Returns an object with information about real and processor time. |
646 | The following procedures accept such an object as an argument and | |
647 | return a selected component: | |
648 | ||
649 | `tms:clock' | |
650 | The current real time, expressed as time units relative to an | |
651 | arbitrary base. | |
652 | ||
653 | `tms:utime' | |
654 | The CPU time units used by the calling process. | |
655 | ||
656 | `tms:stime' | |
657 | The CPU time units used by the system on behalf of the | |
658 | calling process. | |
659 | ||
660 | `tms:cutime' | |
661 | The CPU time units used by terminated child processes of the | |
662 | calling process, whose status has been collected (e.g., using | |
663 | `waitpid'). | |
664 | ||
665 | `tms:cstime' | |
666 | Similarly, the CPU times units used by the system on behalf of | |
667 | terminated child processes. | |
7ad3c1e7 | 668 | |
e2d6569c JB |
669 | ** Removed: list-length |
670 | ** Removed: list-append, list-append! | |
671 | ** Removed: list-reverse, list-reverse! | |
672 | ||
673 | ** array-map renamed to array-map! | |
674 | ||
675 | ** serial-array-map renamed to serial-array-map! | |
676 | ||
660f41fa MD |
677 | ** catch doesn't take #f as first argument any longer |
678 | ||
679 | Previously, it was possible to pass #f instead of a key to `catch'. | |
680 | That would cause `catch' to pass a jump buffer object to the procedure | |
681 | passed as second argument. The procedure could then use this jump | |
682 | buffer objekt as an argument to throw. | |
683 | ||
684 | This mechanism has been removed since its utility doesn't motivate the | |
685 | extra complexity it introduces. | |
686 | ||
332d00f6 JB |
687 | ** The `#/' notation for lists now provokes a warning message from Guile. |
688 | This syntax will be removed from Guile in the near future. | |
689 | ||
690 | To disable the warning message, set the GUILE_HUSH environment | |
691 | variable to any non-empty value. | |
692 | ||
8cd57bd0 JB |
693 | ** The newline character now prints as `#\newline', following the |
694 | normal Scheme notation, not `#\nl'. | |
695 | ||
c484bf7f JB |
696 | * Changes to the gh_ interface |
697 | ||
8986901b JB |
698 | ** The gh_enter function now takes care of loading the Guile startup files. |
699 | gh_enter works by calling scm_boot_guile; see the remarks below. | |
700 | ||
5424b4f7 MD |
701 | ** Function: void gh_write (SCM x) |
702 | ||
703 | Write the printed representation of the scheme object x to the current | |
704 | output port. Corresponds to the scheme level `write'. | |
705 | ||
3a97e020 MD |
706 | ** gh_list_length renamed to gh_length. |
707 | ||
8d6787b6 MG |
708 | ** vector handling routines |
709 | ||
710 | Several major changes. In particular, gh_vector() now resembles | |
711 | (vector ...) (with a caveat -- see manual), and gh_make_vector() now | |
956328d2 MG |
712 | exists and behaves like (make-vector ...). gh_vset() and gh_vref() |
713 | have been renamed gh_vector_set_x() and gh_vector_ref(). Some missing | |
8d6787b6 MG |
714 | vector-related gh_ functions have been implemented. |
715 | ||
7fee59bd MG |
716 | ** pair and list routines |
717 | ||
718 | Implemented several of the R4RS pair and list functions that were | |
719 | missing. | |
720 | ||
171422a9 MD |
721 | ** gh_scm2doubles, gh_doubles2scm, gh_doubles2dvect |
722 | ||
723 | New function. Converts double arrays back and forth between Scheme | |
724 | and C. | |
725 | ||
c484bf7f JB |
726 | * Changes to the scm_ interface |
727 | ||
8986901b JB |
728 | ** The function scm_boot_guile now takes care of loading the startup files. |
729 | ||
730 | Guile's primary initialization function, scm_boot_guile, now takes | |
731 | care of loading `boot-9.scm', in the `ice-9' module, to initialize | |
732 | Guile, define the module system, and put together some standard | |
733 | bindings. It also loads `init.scm', which is intended to hold | |
734 | site-specific initialization code. | |
735 | ||
736 | Since Guile cannot operate properly until boot-9.scm is loaded, there | |
737 | is no reason to separate loading boot-9.scm from Guile's other | |
738 | initialization processes. | |
739 | ||
740 | This job used to be done by scm_compile_shell_switches, which didn't | |
741 | make much sense; in particular, it meant that people using Guile for | |
742 | non-shell-like applications had to jump through hoops to get Guile | |
743 | initialized properly. | |
744 | ||
745 | ** The function scm_compile_shell_switches no longer loads the startup files. | |
746 | Now, Guile always loads the startup files, whenever it is initialized; | |
747 | see the notes above for scm_boot_guile and scm_load_startup_files. | |
748 | ||
749 | ** Function: scm_load_startup_files | |
750 | This new function takes care of loading Guile's initialization file | |
751 | (`boot-9.scm'), and the site initialization file, `init.scm'. Since | |
752 | this is always called by the Guile initialization process, it's | |
753 | probably not too useful to call this yourself, but it's there anyway. | |
754 | ||
87148d9e JB |
755 | ** The semantics of smob marking have changed slightly. |
756 | ||
757 | The smob marking function (the `mark' member of the scm_smobfuns | |
758 | structure) is no longer responsible for setting the mark bit on the | |
759 | smob. The generic smob handling code in the garbage collector will | |
760 | set this bit. The mark function need only ensure that any other | |
761 | objects the smob refers to get marked. | |
762 | ||
763 | Note that this change means that the smob's GC8MARK bit is typically | |
764 | already set upon entry to the mark function. Thus, marking functions | |
765 | which look like this: | |
766 | ||
767 | { | |
768 | if (SCM_GC8MARKP (ptr)) | |
769 | return SCM_BOOL_F; | |
770 | SCM_SETGC8MARK (ptr); | |
771 | ... mark objects to which the smob refers ... | |
772 | } | |
773 | ||
774 | are now incorrect, since they will return early, and fail to mark any | |
775 | other objects the smob refers to. Some code in the Guile library used | |
776 | to work this way. | |
777 | ||
1cf84ea5 JB |
778 | ** The semantics of the I/O port functions in scm_ptobfuns have changed. |
779 | ||
780 | If you have implemented your own I/O port type, by writing the | |
781 | functions required by the scm_ptobfuns and then calling scm_newptob, | |
782 | you will need to change your functions slightly. | |
783 | ||
784 | The functions in a scm_ptobfuns structure now expect the port itself | |
785 | as their argument; they used to expect the `stream' member of the | |
786 | port's scm_port_table structure. This allows functions in an | |
787 | scm_ptobfuns structure to easily access the port's cell (and any flags | |
788 | it its CAR), and the port's scm_port_table structure. | |
789 | ||
790 | Guile now passes the I/O port itself as the `port' argument in the | |
791 | following scm_ptobfuns functions: | |
792 | ||
793 | int (*free) (SCM port); | |
794 | int (*fputc) (int, SCM port); | |
795 | int (*fputs) (char *, SCM port); | |
796 | scm_sizet (*fwrite) SCM_P ((char *ptr, | |
797 | scm_sizet size, | |
798 | scm_sizet nitems, | |
799 | SCM port)); | |
800 | int (*fflush) (SCM port); | |
801 | int (*fgetc) (SCM port); | |
802 | int (*fclose) (SCM port); | |
803 | ||
804 | The interfaces to the `mark', `print', `equalp', and `fgets' methods | |
805 | are unchanged. | |
806 | ||
807 | If you have existing code which defines its own port types, it is easy | |
808 | to convert your code to the new interface; simply apply SCM_STREAM to | |
809 | the port argument to yield the value you code used to expect. | |
810 | ||
811 | Note that since both the port and the stream have the same type in the | |
812 | C code --- they are both SCM values --- the C compiler will not remind | |
813 | you if you forget to update your scm_ptobfuns functions. | |
814 | ||
815 | ||
933a7411 MD |
816 | ** Function: int scm_internal_select (int fds, |
817 | SELECT_TYPE *rfds, | |
818 | SELECT_TYPE *wfds, | |
819 | SELECT_TYPE *efds, | |
820 | struct timeval *timeout); | |
821 | ||
822 | This is a replacement for the `select' function provided by the OS. | |
823 | It enables I/O blocking and sleeping to happen for one cooperative | |
824 | thread without blocking other threads. It also avoids busy-loops in | |
825 | these situations. It is intended that all I/O blocking and sleeping | |
826 | will finally go through this function. Currently, this function is | |
827 | only available on systems providing `gettimeofday' and `select'. | |
828 | ||
5424b4f7 MD |
829 | ** Function: SCM scm_internal_stack_catch (SCM tag, |
830 | scm_catch_body_t body, | |
831 | void *body_data, | |
832 | scm_catch_handler_t handler, | |
833 | void *handler_data) | |
834 | ||
835 | A new sibling to the other two C level `catch' functions | |
836 | scm_internal_catch and scm_internal_lazy_catch. Use it if you want | |
837 | the stack to be saved automatically into the variable `the-last-stack' | |
838 | (scm_the_last_stack_var) on error. This is necessary if you want to | |
839 | use advanced error reporting, such as calling scm_display_error and | |
840 | scm_display_backtrace. (They both take a stack object as argument.) | |
841 | ||
df366c26 MD |
842 | ** Function: SCM scm_spawn_thread (scm_catch_body_t body, |
843 | void *body_data, | |
844 | scm_catch_handler_t handler, | |
845 | void *handler_data) | |
846 | ||
847 | Spawns a new thread. It does a job similar to | |
848 | scm_call_with_new_thread but takes arguments more suitable when | |
849 | spawning threads from application C code. | |
850 | ||
88482b31 MD |
851 | ** The hook scm_error_callback has been removed. It was originally |
852 | intended as a way for the user to install his own error handler. But | |
853 | that method works badly since it intervenes between throw and catch, | |
854 | thereby changing the semantics of expressions like (catch #t ...). | |
855 | The correct way to do it is to use one of the C level catch functions | |
856 | in throw.c: scm_internal_catch/lazy_catch/stack_catch. | |
857 | ||
3a97e020 MD |
858 | ** Removed functions: |
859 | ||
860 | scm_obj_length, scm_list_length, scm_list_append, scm_list_append_x, | |
861 | scm_list_reverse, scm_list_reverse_x | |
862 | ||
863 | ** New macros: SCM_LISTn where n is one of the integers 0-9. | |
864 | ||
865 | These can be used for pretty list creation from C. The idea is taken | |
866 | from Erick Gallesio's STk. | |
867 | ||
298aa6e3 MD |
868 | ** scm_array_map renamed to scm_array_map_x |
869 | ||
527da704 MD |
870 | ** mbstrings are now removed |
871 | ||
872 | This means that the type codes scm_tc7_mb_string and | |
873 | scm_tc7_mb_substring has been removed. | |
874 | ||
8cd57bd0 JB |
875 | ** scm_gen_putc, scm_gen_puts, scm_gen_write, and scm_gen_getc have changed. |
876 | ||
877 | Since we no longer support multi-byte strings, these I/O functions | |
878 | have been simplified, and renamed. Here are their old names, and | |
879 | their new names and arguments: | |
880 | ||
881 | scm_gen_putc -> void scm_putc (int c, SCM port); | |
882 | scm_gen_puts -> void scm_puts (char *s, SCM port); | |
883 | scm_gen_write -> void scm_lfwrite (char *ptr, scm_sizet size, SCM port); | |
884 | scm_gen_getc -> void scm_getc (SCM port); | |
885 | ||
886 | ||
527da704 MD |
887 | ** The macros SCM_TYP7D and SCM_TYP7SD has been removed. |
888 | ||
889 | ** The macro SCM_TYP7S has taken the role of the old SCM_TYP7D | |
890 | ||
891 | SCM_TYP7S now masks away the bit which distinguishes substrings from | |
892 | strings. | |
893 | ||
660f41fa MD |
894 | ** scm_catch_body_t: Backward incompatible change! |
895 | ||
896 | Body functions to scm_internal_catch and friends do not any longer | |
897 | take a second argument. This is because it is no longer possible to | |
898 | pass a #f arg to catch. | |
899 | ||
a8e05009 JB |
900 | ** Calls to scm_protect_object and scm_unprotect now nest properly. |
901 | ||
902 | The function scm_protect_object protects its argument from being freed | |
903 | by the garbage collector. scm_unprotect_object removes that | |
904 | protection. | |
905 | ||
906 | These functions now nest properly. That is, for every object O, there | |
907 | is a counter which scm_protect_object(O) increments and | |
908 | scm_unprotect_object(O) decrements, if the counter is greater than | |
909 | zero. Every object's counter is zero when it is first created. If an | |
910 | object's counter is greater than zero, the garbage collector will not | |
911 | reclaim its storage. | |
912 | ||
913 | This allows you to use scm_protect_object in your code without | |
914 | worrying that some other function you call will call | |
915 | scm_unprotect_object, and allow it to be freed. Assuming that the | |
916 | functions you call are well-behaved, and unprotect only those objects | |
917 | they protect, you can follow the same rule and have confidence that | |
918 | objects will be freed only at appropriate times. | |
919 | ||
c484bf7f JB |
920 | \f |
921 | Changes in Guile 1.2 (released Tuesday, June 24 1997): | |
cf78e9e8 | 922 | |
737c9113 JB |
923 | * Changes to the distribution |
924 | ||
832b09ed JB |
925 | ** Nightly snapshots are now available from ftp.red-bean.com. |
926 | The old server, ftp.cyclic.com, has been relinquished to its rightful | |
927 | owner. | |
928 | ||
929 | Nightly snapshots of the Guile development sources are now available via | |
930 | anonymous FTP from ftp.red-bean.com, as /pub/guile/guile-snap.tar.gz. | |
931 | ||
932 | Via the web, that's: ftp://ftp.red-bean.com/pub/guile/guile-snap.tar.gz | |
933 | For getit, that's: ftp.red-bean.com:/pub/guile/guile-snap.tar.gz | |
934 | ||
0fcab5ed JB |
935 | ** To run Guile without installing it, the procedure has changed a bit. |
936 | ||
937 | If you used a separate build directory to compile Guile, you'll need | |
938 | to include the build directory in SCHEME_LOAD_PATH, as well as the | |
939 | source directory. See the `INSTALL' file for examples. | |
940 | ||
737c9113 JB |
941 | * Changes to the procedure for linking libguile with your programs |
942 | ||
94982a4e JB |
943 | ** The standard Guile load path for Scheme code now includes |
944 | $(datadir)/guile (usually /usr/local/share/guile). This means that | |
945 | you can install your own Scheme files there, and Guile will find them. | |
946 | (Previous versions of Guile only checked a directory whose name | |
947 | contained the Guile version number, so you had to re-install or move | |
948 | your Scheme sources each time you installed a fresh version of Guile.) | |
949 | ||
950 | The load path also includes $(datadir)/guile/site; we recommend | |
951 | putting individual Scheme files there. If you want to install a | |
952 | package with multiple source files, create a directory for them under | |
953 | $(datadir)/guile. | |
954 | ||
955 | ** Guile 1.2 will now use the Rx regular expression library, if it is | |
956 | installed on your system. When you are linking libguile into your own | |
957 | programs, this means you will have to link against -lguile, -lqt (if | |
958 | you configured Guile with thread support), and -lrx. | |
27590f82 JB |
959 | |
960 | If you are using autoconf to generate configuration scripts for your | |
961 | application, the following lines should suffice to add the appropriate | |
962 | libraries to your link command: | |
963 | ||
964 | ### Find Rx, quickthreads and libguile. | |
965 | AC_CHECK_LIB(rx, main) | |
966 | AC_CHECK_LIB(qt, main) | |
967 | AC_CHECK_LIB(guile, scm_shell) | |
968 | ||
94982a4e JB |
969 | The Guile 1.2 distribution does not contain sources for the Rx |
970 | library, as Guile 1.0 did. If you want to use Rx, you'll need to | |
971 | retrieve it from a GNU FTP site and install it separately. | |
972 | ||
b83b8bee JB |
973 | * Changes to Scheme functions and syntax |
974 | ||
e035e7e6 MV |
975 | ** The dynamic linking features of Guile are now enabled by default. |
976 | You can disable them by giving the `--disable-dynamic-linking' option | |
977 | to configure. | |
978 | ||
e035e7e6 MV |
979 | (dynamic-link FILENAME) |
980 | ||
981 | Find the object file denoted by FILENAME (a string) and link it | |
982 | into the running Guile application. When everything works out, | |
983 | return a Scheme object suitable for representing the linked object | |
984 | file. Otherwise an error is thrown. How object files are | |
985 | searched is system dependent. | |
986 | ||
987 | (dynamic-object? VAL) | |
988 | ||
989 | Determine whether VAL represents a dynamically linked object file. | |
990 | ||
991 | (dynamic-unlink DYNOBJ) | |
992 | ||
993 | Unlink the indicated object file from the application. DYNOBJ | |
994 | should be one of the values returned by `dynamic-link'. | |
995 | ||
996 | (dynamic-func FUNCTION DYNOBJ) | |
997 | ||
998 | Search the C function indicated by FUNCTION (a string or symbol) | |
999 | in DYNOBJ and return some Scheme object that can later be used | |
1000 | with `dynamic-call' to actually call this function. Right now, | |
1001 | these Scheme objects are formed by casting the address of the | |
1002 | function to `long' and converting this number to its Scheme | |
1003 | representation. | |
1004 | ||
1005 | (dynamic-call FUNCTION DYNOBJ) | |
1006 | ||
1007 | Call the C function indicated by FUNCTION and DYNOBJ. The | |
1008 | function is passed no arguments and its return value is ignored. | |
1009 | When FUNCTION is something returned by `dynamic-func', call that | |
1010 | function and ignore DYNOBJ. When FUNCTION is a string (or symbol, | |
1011 | etc.), look it up in DYNOBJ; this is equivalent to | |
1012 | ||
1013 | (dynamic-call (dynamic-func FUNCTION DYNOBJ) #f) | |
1014 | ||
1015 | Interrupts are deferred while the C function is executing (with | |
1016 | SCM_DEFER_INTS/SCM_ALLOW_INTS). | |
1017 | ||
1018 | (dynamic-args-call FUNCTION DYNOBJ ARGS) | |
1019 | ||
1020 | Call the C function indicated by FUNCTION and DYNOBJ, but pass it | |
1021 | some arguments and return its return value. The C function is | |
1022 | expected to take two arguments and return an `int', just like | |
1023 | `main': | |
1024 | ||
1025 | int c_func (int argc, char **argv); | |
1026 | ||
1027 | ARGS must be a list of strings and is converted into an array of | |
1028 | `char *'. The array is passed in ARGV and its size in ARGC. The | |
1029 | return value is converted to a Scheme number and returned from the | |
1030 | call to `dynamic-args-call'. | |
1031 | ||
0fcab5ed JB |
1032 | When dynamic linking is disabled or not supported on your system, |
1033 | the above functions throw errors, but they are still available. | |
1034 | ||
e035e7e6 MV |
1035 | Here is a small example that works on GNU/Linux: |
1036 | ||
1037 | (define libc-obj (dynamic-link "libc.so")) | |
1038 | (dynamic-args-call 'rand libc-obj '()) | |
1039 | ||
1040 | See the file `libguile/DYNAMIC-LINKING' for additional comments. | |
1041 | ||
27590f82 JB |
1042 | ** The #/ syntax for module names is depreciated, and will be removed |
1043 | in a future version of Guile. Instead of | |
1044 | ||
1045 | #/foo/bar/baz | |
1046 | ||
1047 | instead write | |
1048 | ||
1049 | (foo bar baz) | |
1050 | ||
1051 | The latter syntax is more consistent with existing Lisp practice. | |
1052 | ||
5dade857 MV |
1053 | ** Guile now does fancier printing of structures. Structures are the |
1054 | underlying implementation for records, which in turn are used to | |
1055 | implement modules, so all of these object now print differently and in | |
1056 | a more informative way. | |
1057 | ||
161029df JB |
1058 | The Scheme printer will examine the builtin variable *struct-printer* |
1059 | whenever it needs to print a structure object. When this variable is | |
1060 | not `#f' it is deemed to be a procedure and will be applied to the | |
1061 | structure object and the output port. When *struct-printer* is `#f' | |
1062 | or the procedure return `#f' the structure object will be printed in | |
1063 | the boring #<struct 80458270> form. | |
5dade857 MV |
1064 | |
1065 | This hook is used by some routines in ice-9/boot-9.scm to implement | |
1066 | type specific printing routines. Please read the comments there about | |
1067 | "printing structs". | |
1068 | ||
1069 | One of the more specific uses of structs are records. The printing | |
1070 | procedure that could be passed to MAKE-RECORD-TYPE is now actually | |
1071 | called. It should behave like a *struct-printer* procedure (described | |
1072 | above). | |
1073 | ||
b83b8bee JB |
1074 | ** Guile now supports a new R4RS-compliant syntax for keywords. A |
1075 | token of the form #:NAME, where NAME has the same syntax as a Scheme | |
1076 | symbol, is the external representation of the keyword named NAME. | |
1077 | Keyword objects print using this syntax as well, so values containing | |
1e5afba0 JB |
1078 | keyword objects can be read back into Guile. When used in an |
1079 | expression, keywords are self-quoting objects. | |
b83b8bee JB |
1080 | |
1081 | Guile suports this read syntax, and uses this print syntax, regardless | |
1082 | of the current setting of the `keyword' read option. The `keyword' | |
1083 | read option only controls whether Guile recognizes the `:NAME' syntax, | |
1084 | which is incompatible with R4RS. (R4RS says such token represent | |
1085 | symbols.) | |
737c9113 JB |
1086 | |
1087 | ** Guile has regular expression support again. Guile 1.0 included | |
1088 | functions for matching regular expressions, based on the Rx library. | |
1089 | In Guile 1.1, the Guile/Rx interface was removed to simplify the | |
1090 | distribution, and thus Guile had no regular expression support. Guile | |
94982a4e JB |
1091 | 1.2 again supports the most commonly used functions, and supports all |
1092 | of SCSH's regular expression functions. | |
2409cdfa | 1093 | |
94982a4e JB |
1094 | If your system does not include a POSIX regular expression library, |
1095 | and you have not linked Guile with a third-party regexp library such as | |
1096 | Rx, these functions will not be available. You can tell whether your | |
1097 | Guile installation includes regular expression support by checking | |
1098 | whether the `*features*' list includes the `regex' symbol. | |
737c9113 | 1099 | |
94982a4e | 1100 | *** regexp functions |
161029df | 1101 | |
94982a4e JB |
1102 | By default, Guile supports POSIX extended regular expressions. That |
1103 | means that the characters `(', `)', `+' and `?' are special, and must | |
1104 | be escaped if you wish to match the literal characters. | |
e1a191a8 | 1105 | |
94982a4e JB |
1106 | This regular expression interface was modeled after that implemented |
1107 | by SCSH, the Scheme Shell. It is intended to be upwardly compatible | |
1108 | with SCSH regular expressions. | |
1109 | ||
1110 | **** Function: string-match PATTERN STR [START] | |
1111 | Compile the string PATTERN into a regular expression and compare | |
1112 | it with STR. The optional numeric argument START specifies the | |
1113 | position of STR at which to begin matching. | |
1114 | ||
1115 | `string-match' returns a "match structure" which describes what, | |
1116 | if anything, was matched by the regular expression. *Note Match | |
1117 | Structures::. If STR does not match PATTERN at all, | |
1118 | `string-match' returns `#f'. | |
1119 | ||
1120 | Each time `string-match' is called, it must compile its PATTERN | |
1121 | argument into a regular expression structure. This operation is | |
1122 | expensive, which makes `string-match' inefficient if the same regular | |
1123 | expression is used several times (for example, in a loop). For better | |
1124 | performance, you can compile a regular expression in advance and then | |
1125 | match strings against the compiled regexp. | |
1126 | ||
1127 | **** Function: make-regexp STR [FLAGS] | |
1128 | Compile the regular expression described by STR, and return the | |
1129 | compiled regexp structure. If STR does not describe a legal | |
1130 | regular expression, `make-regexp' throws a | |
1131 | `regular-expression-syntax' error. | |
1132 | ||
1133 | FLAGS may be the bitwise-or of one or more of the following: | |
1134 | ||
1135 | **** Constant: regexp/extended | |
1136 | Use POSIX Extended Regular Expression syntax when interpreting | |
1137 | STR. If not set, POSIX Basic Regular Expression syntax is used. | |
1138 | If the FLAGS argument is omitted, we assume regexp/extended. | |
1139 | ||
1140 | **** Constant: regexp/icase | |
1141 | Do not differentiate case. Subsequent searches using the | |
1142 | returned regular expression will be case insensitive. | |
1143 | ||
1144 | **** Constant: regexp/newline | |
1145 | Match-any-character operators don't match a newline. | |
1146 | ||
1147 | A non-matching list ([^...]) not containing a newline matches a | |
1148 | newline. | |
1149 | ||
1150 | Match-beginning-of-line operator (^) matches the empty string | |
1151 | immediately after a newline, regardless of whether the FLAGS | |
1152 | passed to regexp-exec contain regexp/notbol. | |
1153 | ||
1154 | Match-end-of-line operator ($) matches the empty string | |
1155 | immediately before a newline, regardless of whether the FLAGS | |
1156 | passed to regexp-exec contain regexp/noteol. | |
1157 | ||
1158 | **** Function: regexp-exec REGEXP STR [START [FLAGS]] | |
1159 | Match the compiled regular expression REGEXP against `str'. If | |
1160 | the optional integer START argument is provided, begin matching | |
1161 | from that position in the string. Return a match structure | |
1162 | describing the results of the match, or `#f' if no match could be | |
1163 | found. | |
1164 | ||
1165 | FLAGS may be the bitwise-or of one or more of the following: | |
1166 | ||
1167 | **** Constant: regexp/notbol | |
1168 | The match-beginning-of-line operator always fails to match (but | |
1169 | see the compilation flag regexp/newline above) This flag may be | |
1170 | used when different portions of a string are passed to | |
1171 | regexp-exec and the beginning of the string should not be | |
1172 | interpreted as the beginning of the line. | |
1173 | ||
1174 | **** Constant: regexp/noteol | |
1175 | The match-end-of-line operator always fails to match (but see the | |
1176 | compilation flag regexp/newline above) | |
1177 | ||
1178 | **** Function: regexp? OBJ | |
1179 | Return `#t' if OBJ is a compiled regular expression, or `#f' | |
1180 | otherwise. | |
1181 | ||
1182 | Regular expressions are commonly used to find patterns in one string | |
1183 | and replace them with the contents of another string. | |
1184 | ||
1185 | **** Function: regexp-substitute PORT MATCH [ITEM...] | |
1186 | Write to the output port PORT selected contents of the match | |
1187 | structure MATCH. Each ITEM specifies what should be written, and | |
1188 | may be one of the following arguments: | |
1189 | ||
1190 | * A string. String arguments are written out verbatim. | |
1191 | ||
1192 | * An integer. The submatch with that number is written. | |
1193 | ||
1194 | * The symbol `pre'. The portion of the matched string preceding | |
1195 | the regexp match is written. | |
1196 | ||
1197 | * The symbol `post'. The portion of the matched string | |
1198 | following the regexp match is written. | |
1199 | ||
1200 | PORT may be `#f', in which case nothing is written; instead, | |
1201 | `regexp-substitute' constructs a string from the specified ITEMs | |
1202 | and returns that. | |
1203 | ||
1204 | **** Function: regexp-substitute/global PORT REGEXP TARGET [ITEM...] | |
1205 | Similar to `regexp-substitute', but can be used to perform global | |
1206 | substitutions on STR. Instead of taking a match structure as an | |
1207 | argument, `regexp-substitute/global' takes two string arguments: a | |
1208 | REGEXP string describing a regular expression, and a TARGET string | |
1209 | which should be matched against this regular expression. | |
1210 | ||
1211 | Each ITEM behaves as in REGEXP-SUBSTITUTE, with the following | |
1212 | exceptions: | |
1213 | ||
1214 | * A function may be supplied. When this function is called, it | |
1215 | will be passed one argument: a match structure for a given | |
1216 | regular expression match. It should return a string to be | |
1217 | written out to PORT. | |
1218 | ||
1219 | * The `post' symbol causes `regexp-substitute/global' to recurse | |
1220 | on the unmatched portion of STR. This *must* be supplied in | |
1221 | order to perform global search-and-replace on STR; if it is | |
1222 | not present among the ITEMs, then `regexp-substitute/global' | |
1223 | will return after processing a single match. | |
1224 | ||
1225 | *** Match Structures | |
1226 | ||
1227 | A "match structure" is the object returned by `string-match' and | |
1228 | `regexp-exec'. It describes which portion of a string, if any, matched | |
1229 | the given regular expression. Match structures include: a reference to | |
1230 | the string that was checked for matches; the starting and ending | |
1231 | positions of the regexp match; and, if the regexp included any | |
1232 | parenthesized subexpressions, the starting and ending positions of each | |
1233 | submatch. | |
1234 | ||
1235 | In each of the regexp match functions described below, the `match' | |
1236 | argument must be a match structure returned by a previous call to | |
1237 | `string-match' or `regexp-exec'. Most of these functions return some | |
1238 | information about the original target string that was matched against a | |
1239 | regular expression; we will call that string TARGET for easy reference. | |
1240 | ||
1241 | **** Function: regexp-match? OBJ | |
1242 | Return `#t' if OBJ is a match structure returned by a previous | |
1243 | call to `regexp-exec', or `#f' otherwise. | |
1244 | ||
1245 | **** Function: match:substring MATCH [N] | |
1246 | Return the portion of TARGET matched by subexpression number N. | |
1247 | Submatch 0 (the default) represents the entire regexp match. If | |
1248 | the regular expression as a whole matched, but the subexpression | |
1249 | number N did not match, return `#f'. | |
1250 | ||
1251 | **** Function: match:start MATCH [N] | |
1252 | Return the starting position of submatch number N. | |
1253 | ||
1254 | **** Function: match:end MATCH [N] | |
1255 | Return the ending position of submatch number N. | |
1256 | ||
1257 | **** Function: match:prefix MATCH | |
1258 | Return the unmatched portion of TARGET preceding the regexp match. | |
1259 | ||
1260 | **** Function: match:suffix MATCH | |
1261 | Return the unmatched portion of TARGET following the regexp match. | |
1262 | ||
1263 | **** Function: match:count MATCH | |
1264 | Return the number of parenthesized subexpressions from MATCH. | |
1265 | Note that the entire regular expression match itself counts as a | |
1266 | subexpression, and failed submatches are included in the count. | |
1267 | ||
1268 | **** Function: match:string MATCH | |
1269 | Return the original TARGET string. | |
1270 | ||
1271 | *** Backslash Escapes | |
1272 | ||
1273 | Sometimes you will want a regexp to match characters like `*' or `$' | |
1274 | exactly. For example, to check whether a particular string represents | |
1275 | a menu entry from an Info node, it would be useful to match it against | |
1276 | a regexp like `^* [^:]*::'. However, this won't work; because the | |
1277 | asterisk is a metacharacter, it won't match the `*' at the beginning of | |
1278 | the string. In this case, we want to make the first asterisk un-magic. | |
1279 | ||
1280 | You can do this by preceding the metacharacter with a backslash | |
1281 | character `\'. (This is also called "quoting" the metacharacter, and | |
1282 | is known as a "backslash escape".) When Guile sees a backslash in a | |
1283 | regular expression, it considers the following glyph to be an ordinary | |
1284 | character, no matter what special meaning it would ordinarily have. | |
1285 | Therefore, we can make the above example work by changing the regexp to | |
1286 | `^\* [^:]*::'. The `\*' sequence tells the regular expression engine | |
1287 | to match only a single asterisk in the target string. | |
1288 | ||
1289 | Since the backslash is itself a metacharacter, you may force a | |
1290 | regexp to match a backslash in the target string by preceding the | |
1291 | backslash with itself. For example, to find variable references in a | |
1292 | TeX program, you might want to find occurrences of the string `\let\' | |
1293 | followed by any number of alphabetic characters. The regular expression | |
1294 | `\\let\\[A-Za-z]*' would do this: the double backslashes in the regexp | |
1295 | each match a single backslash in the target string. | |
1296 | ||
1297 | **** Function: regexp-quote STR | |
1298 | Quote each special character found in STR with a backslash, and | |
1299 | return the resulting string. | |
1300 | ||
1301 | *Very important:* Using backslash escapes in Guile source code (as | |
1302 | in Emacs Lisp or C) can be tricky, because the backslash character has | |
1303 | special meaning for the Guile reader. For example, if Guile encounters | |
1304 | the character sequence `\n' in the middle of a string while processing | |
1305 | Scheme code, it replaces those characters with a newline character. | |
1306 | Similarly, the character sequence `\t' is replaced by a horizontal tab. | |
1307 | Several of these "escape sequences" are processed by the Guile reader | |
1308 | before your code is executed. Unrecognized escape sequences are | |
1309 | ignored: if the characters `\*' appear in a string, they will be | |
1310 | translated to the single character `*'. | |
1311 | ||
1312 | This translation is obviously undesirable for regular expressions, | |
1313 | since we want to be able to include backslashes in a string in order to | |
1314 | escape regexp metacharacters. Therefore, to make sure that a backslash | |
1315 | is preserved in a string in your Guile program, you must use *two* | |
1316 | consecutive backslashes: | |
1317 | ||
1318 | (define Info-menu-entry-pattern (make-regexp "^\\* [^:]*")) | |
1319 | ||
1320 | The string in this example is preprocessed by the Guile reader before | |
1321 | any code is executed. The resulting argument to `make-regexp' is the | |
1322 | string `^\* [^:]*', which is what we really want. | |
1323 | ||
1324 | This also means that in order to write a regular expression that | |
1325 | matches a single backslash character, the regular expression string in | |
1326 | the source code must include *four* backslashes. Each consecutive pair | |
1327 | of backslashes gets translated by the Guile reader to a single | |
1328 | backslash, and the resulting double-backslash is interpreted by the | |
1329 | regexp engine as matching a single backslash character. Hence: | |
1330 | ||
1331 | (define tex-variable-pattern (make-regexp "\\\\let\\\\=[A-Za-z]*")) | |
1332 | ||
1333 | The reason for the unwieldiness of this syntax is historical. Both | |
1334 | regular expression pattern matchers and Unix string processing systems | |
1335 | have traditionally used backslashes with the special meanings described | |
1336 | above. The POSIX regular expression specification and ANSI C standard | |
1337 | both require these semantics. Attempting to abandon either convention | |
1338 | would cause other kinds of compatibility problems, possibly more severe | |
1339 | ones. Therefore, without extending the Scheme reader to support | |
1340 | strings with different quoting conventions (an ungainly and confusing | |
1341 | extension when implemented in other languages), we must adhere to this | |
1342 | cumbersome escape syntax. | |
1343 | ||
7ad3c1e7 GH |
1344 | * Changes to the gh_ interface |
1345 | ||
1346 | * Changes to the scm_ interface | |
1347 | ||
1348 | * Changes to system call interfaces: | |
94982a4e | 1349 | |
7ad3c1e7 | 1350 | ** The value returned by `raise' is now unspecified. It throws an exception |
e1a191a8 GH |
1351 | if an error occurs. |
1352 | ||
94982a4e | 1353 | *** A new procedure `sigaction' can be used to install signal handlers |
115b09a5 GH |
1354 | |
1355 | (sigaction signum [action] [flags]) | |
1356 | ||
1357 | signum is the signal number, which can be specified using the value | |
1358 | of SIGINT etc. | |
1359 | ||
1360 | If action is omitted, sigaction returns a pair: the CAR is the current | |
1361 | signal hander, which will be either an integer with the value SIG_DFL | |
1362 | (default action) or SIG_IGN (ignore), or the Scheme procedure which | |
1363 | handles the signal, or #f if a non-Scheme procedure handles the | |
1364 | signal. The CDR contains the current sigaction flags for the handler. | |
1365 | ||
1366 | If action is provided, it is installed as the new handler for signum. | |
1367 | action can be a Scheme procedure taking one argument, or the value of | |
1368 | SIG_DFL (default action) or SIG_IGN (ignore), or #f to restore | |
1369 | whatever signal handler was installed before sigaction was first used. | |
1370 | Flags can optionally be specified for the new handler (SA_RESTART is | |
1371 | always used if the system provides it, so need not be specified.) The | |
1372 | return value is a pair with information about the old handler as | |
1373 | described above. | |
1374 | ||
1375 | This interface does not provide access to the "signal blocking" | |
1376 | facility. Maybe this is not needed, since the thread support may | |
1377 | provide solutions to the problem of consistent access to data | |
1378 | structures. | |
e1a191a8 | 1379 | |
94982a4e | 1380 | *** A new procedure `flush-all-ports' is equivalent to running |
89ea5b7c GH |
1381 | `force-output' on every port open for output. |
1382 | ||
94982a4e JB |
1383 | ** Guile now provides information on how it was built, via the new |
1384 | global variable, %guile-build-info. This variable records the values | |
1385 | of the standard GNU makefile directory variables as an assocation | |
1386 | list, mapping variable names (symbols) onto directory paths (strings). | |
1387 | For example, to find out where the Guile link libraries were | |
1388 | installed, you can say: | |
1389 | ||
1390 | guile -c "(display (assq-ref %guile-build-info 'libdir)) (newline)" | |
1391 | ||
1392 | ||
1393 | * Changes to the scm_ interface | |
1394 | ||
1395 | ** The new function scm_handle_by_message_noexit is just like the | |
1396 | existing scm_handle_by_message function, except that it doesn't call | |
1397 | exit to terminate the process. Instead, it prints a message and just | |
1398 | returns #f. This might be a more appropriate catch-all handler for | |
1399 | new dynamic roots and threads. | |
1400 | ||
cf78e9e8 | 1401 | \f |
c484bf7f | 1402 | Changes in Guile 1.1 (released Friday, May 16 1997): |
f3b1485f JB |
1403 | |
1404 | * Changes to the distribution. | |
1405 | ||
1406 | The Guile 1.0 distribution has been split up into several smaller | |
1407 | pieces: | |
1408 | guile-core --- the Guile interpreter itself. | |
1409 | guile-tcltk --- the interface between the Guile interpreter and | |
1410 | Tcl/Tk; Tcl is an interpreter for a stringy language, and Tk | |
1411 | is a toolkit for building graphical user interfaces. | |
1412 | guile-rgx-ctax --- the interface between Guile and the Rx regular | |
1413 | expression matcher, and the translator for the Ctax | |
1414 | programming language. These are packaged together because the | |
1415 | Ctax translator uses Rx to parse Ctax source code. | |
1416 | ||
095936d2 JB |
1417 | This NEWS file describes the changes made to guile-core since the 1.0 |
1418 | release. | |
1419 | ||
48d224d7 JB |
1420 | We no longer distribute the documentation, since it was either out of |
1421 | date, or incomplete. As soon as we have current documentation, we | |
1422 | will distribute it. | |
1423 | ||
0fcab5ed JB |
1424 | |
1425 | ||
f3b1485f JB |
1426 | * Changes to the stand-alone interpreter |
1427 | ||
48d224d7 JB |
1428 | ** guile now accepts command-line arguments compatible with SCSH, Olin |
1429 | Shivers' Scheme Shell. | |
1430 | ||
1431 | In general, arguments are evaluated from left to right, but there are | |
1432 | exceptions. The following switches stop argument processing, and | |
1433 | stash all remaining command-line arguments as the value returned by | |
1434 | the (command-line) function. | |
1435 | -s SCRIPT load Scheme source code from FILE, and exit | |
1436 | -c EXPR evalute Scheme expression EXPR, and exit | |
1437 | -- stop scanning arguments; run interactively | |
1438 | ||
1439 | The switches below are processed as they are encountered. | |
1440 | -l FILE load Scheme source code from FILE | |
1441 | -e FUNCTION after reading script, apply FUNCTION to | |
1442 | command line arguments | |
1443 | -ds do -s script at this point | |
1444 | --emacs enable Emacs protocol (experimental) | |
1445 | -h, --help display this help and exit | |
1446 | -v, --version display version information and exit | |
1447 | \ read arguments from following script lines | |
1448 | ||
1449 | So, for example, here is a Guile script named `ekko' (thanks, Olin) | |
1450 | which re-implements the traditional "echo" command: | |
1451 | ||
1452 | #!/usr/local/bin/guile -s | |
1453 | !# | |
1454 | (define (main args) | |
1455 | (map (lambda (arg) (display arg) (display " ")) | |
1456 | (cdr args)) | |
1457 | (newline)) | |
1458 | ||
1459 | (main (command-line)) | |
1460 | ||
1461 | Suppose we invoke this script as follows: | |
1462 | ||
1463 | ekko a speckled gecko | |
1464 | ||
1465 | Through the magic of Unix script processing (triggered by the `#!' | |
1466 | token at the top of the file), /usr/local/bin/guile receives the | |
1467 | following list of command-line arguments: | |
1468 | ||
1469 | ("-s" "./ekko" "a" "speckled" "gecko") | |
1470 | ||
1471 | Unix inserts the name of the script after the argument specified on | |
1472 | the first line of the file (in this case, "-s"), and then follows that | |
1473 | with the arguments given to the script. Guile loads the script, which | |
1474 | defines the `main' function, and then applies it to the list of | |
1475 | remaining command-line arguments, ("a" "speckled" "gecko"). | |
1476 | ||
095936d2 JB |
1477 | In Unix, the first line of a script file must take the following form: |
1478 | ||
1479 | #!INTERPRETER ARGUMENT | |
1480 | ||
1481 | where INTERPRETER is the absolute filename of the interpreter | |
1482 | executable, and ARGUMENT is a single command-line argument to pass to | |
1483 | the interpreter. | |
1484 | ||
1485 | You may only pass one argument to the interpreter, and its length is | |
1486 | limited. These restrictions can be annoying to work around, so Guile | |
1487 | provides a general mechanism (borrowed from, and compatible with, | |
1488 | SCSH) for circumventing them. | |
1489 | ||
1490 | If the ARGUMENT in a Guile script is a single backslash character, | |
1491 | `\', Guile will open the script file, parse arguments from its second | |
1492 | and subsequent lines, and replace the `\' with them. So, for example, | |
1493 | here is another implementation of the `ekko' script: | |
1494 | ||
1495 | #!/usr/local/bin/guile \ | |
1496 | -e main -s | |
1497 | !# | |
1498 | (define (main args) | |
1499 | (for-each (lambda (arg) (display arg) (display " ")) | |
1500 | (cdr args)) | |
1501 | (newline)) | |
1502 | ||
1503 | If the user invokes this script as follows: | |
1504 | ||
1505 | ekko a speckled gecko | |
1506 | ||
1507 | Unix expands this into | |
1508 | ||
1509 | /usr/local/bin/guile \ ekko a speckled gecko | |
1510 | ||
1511 | When Guile sees the `\' argument, it replaces it with the arguments | |
1512 | read from the second line of the script, producing: | |
1513 | ||
1514 | /usr/local/bin/guile -e main -s ekko a speckled gecko | |
1515 | ||
1516 | This tells Guile to load the `ekko' script, and apply the function | |
1517 | `main' to the argument list ("a" "speckled" "gecko"). | |
1518 | ||
1519 | Here is how Guile parses the command-line arguments: | |
1520 | - Each space character terminates an argument. This means that two | |
1521 | spaces in a row introduce an empty-string argument. | |
1522 | - The tab character is not permitted (unless you quote it with the | |
1523 | backslash character, as described below), to avoid confusion. | |
1524 | - The newline character terminates the sequence of arguments, and will | |
1525 | also terminate a final non-empty argument. (However, a newline | |
1526 | following a space will not introduce a final empty-string argument; | |
1527 | it only terminates the argument list.) | |
1528 | - The backslash character is the escape character. It escapes | |
1529 | backslash, space, tab, and newline. The ANSI C escape sequences | |
1530 | like \n and \t are also supported. These produce argument | |
1531 | constituents; the two-character combination \n doesn't act like a | |
1532 | terminating newline. The escape sequence \NNN for exactly three | |
1533 | octal digits reads as the character whose ASCII code is NNN. As | |
1534 | above, characters produced this way are argument constituents. | |
1535 | Backslash followed by other characters is not allowed. | |
1536 | ||
48d224d7 JB |
1537 | * Changes to the procedure for linking libguile with your programs |
1538 | ||
1539 | ** Guile now builds and installs a shared guile library, if your | |
1540 | system support shared libraries. (It still builds a static library on | |
1541 | all systems.) Guile automatically detects whether your system | |
1542 | supports shared libraries. To prevent Guile from buildisg shared | |
1543 | libraries, pass the `--disable-shared' flag to the configure script. | |
1544 | ||
1545 | Guile takes longer to compile when it builds shared libraries, because | |
1546 | it must compile every file twice --- once to produce position- | |
1547 | independent object code, and once to produce normal object code. | |
1548 | ||
1549 | ** The libthreads library has been merged into libguile. | |
1550 | ||
1551 | To link a program against Guile, you now need only link against | |
1552 | -lguile and -lqt; -lthreads is no longer needed. If you are using | |
1553 | autoconf to generate configuration scripts for your application, the | |
1554 | following lines should suffice to add the appropriate libraries to | |
1555 | your link command: | |
1556 | ||
1557 | ### Find quickthreads and libguile. | |
1558 | AC_CHECK_LIB(qt, main) | |
1559 | AC_CHECK_LIB(guile, scm_shell) | |
f3b1485f JB |
1560 | |
1561 | * Changes to Scheme functions | |
1562 | ||
095936d2 JB |
1563 | ** Guile Scheme's special syntax for keyword objects is now optional, |
1564 | and disabled by default. | |
1565 | ||
1566 | The syntax variation from R4RS made it difficult to port some | |
1567 | interesting packages to Guile. The routines which accepted keyword | |
1568 | arguments (mostly in the module system) have been modified to also | |
1569 | accept symbols whose names begin with `:'. | |
1570 | ||
1571 | To change the keyword syntax, you must first import the (ice-9 debug) | |
1572 | module: | |
1573 | (use-modules (ice-9 debug)) | |
1574 | ||
1575 | Then you can enable the keyword syntax as follows: | |
1576 | (read-set! keywords 'prefix) | |
1577 | ||
1578 | To disable keyword syntax, do this: | |
1579 | (read-set! keywords #f) | |
1580 | ||
1581 | ** Many more primitive functions accept shared substrings as | |
1582 | arguments. In the past, these functions required normal, mutable | |
1583 | strings as arguments, although they never made use of this | |
1584 | restriction. | |
1585 | ||
1586 | ** The uniform array functions now operate on byte vectors. These | |
1587 | functions are `array-fill!', `serial-array-copy!', `array-copy!', | |
1588 | `serial-array-map', `array-map', `array-for-each', and | |
1589 | `array-index-map!'. | |
1590 | ||
1591 | ** The new functions `trace' and `untrace' implement simple debugging | |
1592 | support for Scheme functions. | |
1593 | ||
1594 | The `trace' function accepts any number of procedures as arguments, | |
1595 | and tells the Guile interpreter to display each procedure's name and | |
1596 | arguments each time the procedure is invoked. When invoked with no | |
1597 | arguments, `trace' returns the list of procedures currently being | |
1598 | traced. | |
1599 | ||
1600 | The `untrace' function accepts any number of procedures as arguments, | |
1601 | and tells the Guile interpreter not to trace them any more. When | |
1602 | invoked with no arguments, `untrace' untraces all curretly traced | |
1603 | procedures. | |
1604 | ||
1605 | The tracing in Guile has an advantage over most other systems: we | |
1606 | don't create new procedure objects, but mark the procedure objects | |
1607 | themselves. This means that anonymous and internal procedures can be | |
1608 | traced. | |
1609 | ||
1610 | ** The function `assert-repl-prompt' has been renamed to | |
1611 | `set-repl-prompt!'. It takes one argument, PROMPT. | |
1612 | - If PROMPT is #f, the Guile read-eval-print loop will not prompt. | |
1613 | - If PROMPT is a string, we use it as a prompt. | |
1614 | - If PROMPT is a procedure accepting no arguments, we call it, and | |
1615 | display the result as a prompt. | |
1616 | - Otherwise, we display "> ". | |
1617 | ||
1618 | ** The new function `eval-string' reads Scheme expressions from a | |
1619 | string and evaluates them, returning the value of the last expression | |
1620 | in the string. If the string contains no expressions, it returns an | |
1621 | unspecified value. | |
1622 | ||
1623 | ** The new function `thunk?' returns true iff its argument is a | |
1624 | procedure of zero arguments. | |
1625 | ||
1626 | ** `defined?' is now a builtin function, instead of syntax. This | |
1627 | means that its argument should be quoted. It returns #t iff its | |
1628 | argument is bound in the current module. | |
1629 | ||
1630 | ** The new syntax `use-modules' allows you to add new modules to your | |
1631 | environment without re-typing a complete `define-module' form. It | |
1632 | accepts any number of module names as arguments, and imports their | |
1633 | public bindings into the current module. | |
1634 | ||
1635 | ** The new function (module-defined? NAME MODULE) returns true iff | |
1636 | NAME, a symbol, is defined in MODULE, a module object. | |
1637 | ||
1638 | ** The new function `builtin-bindings' creates and returns a hash | |
1639 | table containing copies of all the root module's bindings. | |
1640 | ||
1641 | ** The new function `builtin-weak-bindings' does the same as | |
1642 | `builtin-bindings', but creates a doubly-weak hash table. | |
1643 | ||
1644 | ** The `equal?' function now considers variable objects to be | |
1645 | equivalent if they have the same name and the same value. | |
1646 | ||
1647 | ** The new function `command-line' returns the command-line arguments | |
1648 | given to Guile, as a list of strings. | |
1649 | ||
1650 | When using guile as a script interpreter, `command-line' returns the | |
1651 | script's arguments; those processed by the interpreter (like `-s' or | |
1652 | `-c') are omitted. (In other words, you get the normal, expected | |
1653 | behavior.) Any application that uses scm_shell to process its | |
1654 | command-line arguments gets this behavior as well. | |
1655 | ||
1656 | ** The new function `load-user-init' looks for a file called `.guile' | |
1657 | in the user's home directory, and loads it if it exists. This is | |
1658 | mostly for use by the code generated by scm_compile_shell_switches, | |
1659 | but we thought it might also be useful in other circumstances. | |
1660 | ||
1661 | ** The new function `log10' returns the base-10 logarithm of its | |
1662 | argument. | |
1663 | ||
1664 | ** Changes to I/O functions | |
1665 | ||
1666 | *** The functions `read', `primitive-load', `read-and-eval!', and | |
1667 | `primitive-load-path' no longer take optional arguments controlling | |
1668 | case insensitivity and a `#' parser. | |
1669 | ||
1670 | Case sensitivity is now controlled by a read option called | |
1671 | `case-insensitive'. The user can add new `#' syntaxes with the | |
1672 | `read-hash-extend' function (see below). | |
1673 | ||
1674 | *** The new function `read-hash-extend' allows the user to change the | |
1675 | syntax of Guile Scheme in a somewhat controlled way. | |
1676 | ||
1677 | (read-hash-extend CHAR PROC) | |
1678 | When parsing S-expressions, if we read a `#' character followed by | |
1679 | the character CHAR, use PROC to parse an object from the stream. | |
1680 | If PROC is #f, remove any parsing procedure registered for CHAR. | |
1681 | ||
1682 | The reader applies PROC to two arguments: CHAR and an input port. | |
1683 | ||
1684 | *** The new functions read-delimited and read-delimited! provide a | |
1685 | general mechanism for doing delimited input on streams. | |
1686 | ||
1687 | (read-delimited DELIMS [PORT HANDLE-DELIM]) | |
1688 | Read until we encounter one of the characters in DELIMS (a string), | |
1689 | or end-of-file. PORT is the input port to read from; it defaults to | |
1690 | the current input port. The HANDLE-DELIM parameter determines how | |
1691 | the terminating character is handled; it should be one of the | |
1692 | following symbols: | |
1693 | ||
1694 | 'trim omit delimiter from result | |
1695 | 'peek leave delimiter character in input stream | |
1696 | 'concat append delimiter character to returned value | |
1697 | 'split return a pair: (RESULT . TERMINATOR) | |
1698 | ||
1699 | HANDLE-DELIM defaults to 'peek. | |
1700 | ||
1701 | (read-delimited! DELIMS BUF [PORT HANDLE-DELIM START END]) | |
1702 | A side-effecting variant of `read-delimited'. | |
1703 | ||
1704 | The data is written into the string BUF at the indices in the | |
1705 | half-open interval [START, END); the default interval is the whole | |
1706 | string: START = 0 and END = (string-length BUF). The values of | |
1707 | START and END must specify a well-defined interval in BUF, i.e. | |
1708 | 0 <= START <= END <= (string-length BUF). | |
1709 | ||
1710 | It returns NBYTES, the number of bytes read. If the buffer filled | |
1711 | up without a delimiter character being found, it returns #f. If the | |
1712 | port is at EOF when the read starts, it returns the EOF object. | |
1713 | ||
1714 | If an integer is returned (i.e., the read is successfully terminated | |
1715 | by reading a delimiter character), then the HANDLE-DELIM parameter | |
1716 | determines how to handle the terminating character. It is described | |
1717 | above, and defaults to 'peek. | |
1718 | ||
1719 | (The descriptions of these functions were borrowed from the SCSH | |
1720 | manual, by Olin Shivers and Brian Carlstrom.) | |
1721 | ||
1722 | *** The `%read-delimited!' function is the primitive used to implement | |
1723 | `read-delimited' and `read-delimited!'. | |
1724 | ||
1725 | (%read-delimited! DELIMS BUF GOBBLE? [PORT START END]) | |
1726 | ||
1727 | This returns a pair of values: (TERMINATOR . NUM-READ). | |
1728 | - TERMINATOR describes why the read was terminated. If it is a | |
1729 | character or the eof object, then that is the value that terminated | |
1730 | the read. If it is #f, the function filled the buffer without finding | |
1731 | a delimiting character. | |
1732 | - NUM-READ is the number of characters read into BUF. | |
1733 | ||
1734 | If the read is successfully terminated by reading a delimiter | |
1735 | character, then the gobble? parameter determines what to do with the | |
1736 | terminating character. If true, the character is removed from the | |
1737 | input stream; if false, the character is left in the input stream | |
1738 | where a subsequent read operation will retrieve it. In either case, | |
1739 | the character is also the first value returned by the procedure call. | |
1740 | ||
1741 | (The descriptions of this function was borrowed from the SCSH manual, | |
1742 | by Olin Shivers and Brian Carlstrom.) | |
1743 | ||
1744 | *** The `read-line' and `read-line!' functions have changed; they now | |
1745 | trim the terminator by default; previously they appended it to the | |
1746 | returned string. For the old behavior, use (read-line PORT 'concat). | |
1747 | ||
1748 | *** The functions `uniform-array-read!' and `uniform-array-write!' now | |
1749 | take new optional START and END arguments, specifying the region of | |
1750 | the array to read and write. | |
1751 | ||
f348c807 JB |
1752 | *** The `ungetc-char-ready?' function has been removed. We feel it's |
1753 | inappropriate for an interface to expose implementation details this | |
1754 | way. | |
095936d2 JB |
1755 | |
1756 | ** Changes to the Unix library and system call interface | |
1757 | ||
1758 | *** The new fcntl function provides access to the Unix `fcntl' system | |
1759 | call. | |
1760 | ||
1761 | (fcntl PORT COMMAND VALUE) | |
1762 | Apply COMMAND to PORT's file descriptor, with VALUE as an argument. | |
1763 | Values for COMMAND are: | |
1764 | ||
1765 | F_DUPFD duplicate a file descriptor | |
1766 | F_GETFD read the descriptor's close-on-exec flag | |
1767 | F_SETFD set the descriptor's close-on-exec flag to VALUE | |
1768 | F_GETFL read the descriptor's flags, as set on open | |
1769 | F_SETFL set the descriptor's flags, as set on open to VALUE | |
1770 | F_GETOWN return the process ID of a socket's owner, for SIGIO | |
1771 | F_SETOWN set the process that owns a socket to VALUE, for SIGIO | |
1772 | FD_CLOEXEC not sure what this is | |
1773 | ||
1774 | For details, see the documentation for the fcntl system call. | |
1775 | ||
1776 | *** The arguments to `select' have changed, for compatibility with | |
1777 | SCSH. The TIMEOUT parameter may now be non-integral, yielding the | |
1778 | expected behavior. The MILLISECONDS parameter has been changed to | |
1779 | MICROSECONDS, to more closely resemble the underlying system call. | |
1780 | The RVEC, WVEC, and EVEC arguments can now be vectors; the type of the | |
1781 | corresponding return set will be the same. | |
1782 | ||
1783 | *** The arguments to the `mknod' system call have changed. They are | |
1784 | now: | |
1785 | ||
1786 | (mknod PATH TYPE PERMS DEV) | |
1787 | Create a new file (`node') in the file system. PATH is the name of | |
1788 | the file to create. TYPE is the kind of file to create; it should | |
1789 | be 'fifo, 'block-special, or 'char-special. PERMS specifies the | |
1790 | permission bits to give the newly created file. If TYPE is | |
1791 | 'block-special or 'char-special, DEV specifies which device the | |
1792 | special file refers to; its interpretation depends on the kind of | |
1793 | special file being created. | |
1794 | ||
1795 | *** The `fork' function has been renamed to `primitive-fork', to avoid | |
1796 | clashing with various SCSH forks. | |
1797 | ||
1798 | *** The `recv' and `recvfrom' functions have been renamed to `recv!' | |
1799 | and `recvfrom!'. They no longer accept a size for a second argument; | |
1800 | you must pass a string to hold the received value. They no longer | |
1801 | return the buffer. Instead, `recv' returns the length of the message | |
1802 | received, and `recvfrom' returns a pair containing the packet's length | |
1803 | and originating address. | |
1804 | ||
1805 | *** The file descriptor datatype has been removed, as have the | |
1806 | `read-fd', `write-fd', `close', `lseek', and `dup' functions. | |
1807 | We plan to replace these functions with a SCSH-compatible interface. | |
1808 | ||
1809 | *** The `create' function has been removed; it's just a special case | |
1810 | of `open'. | |
1811 | ||
1812 | *** There are new functions to break down process termination status | |
1813 | values. In the descriptions below, STATUS is a value returned by | |
1814 | `waitpid'. | |
1815 | ||
1816 | (status:exit-val STATUS) | |
1817 | If the child process exited normally, this function returns the exit | |
1818 | code for the child process (i.e., the value passed to exit, or | |
1819 | returned from main). If the child process did not exit normally, | |
1820 | this function returns #f. | |
1821 | ||
1822 | (status:stop-sig STATUS) | |
1823 | If the child process was suspended by a signal, this function | |
1824 | returns the signal that suspended the child. Otherwise, it returns | |
1825 | #f. | |
1826 | ||
1827 | (status:term-sig STATUS) | |
1828 | If the child process terminated abnormally, this function returns | |
1829 | the signal that terminated the child. Otherwise, this function | |
1830 | returns false. | |
1831 | ||
1832 | POSIX promises that exactly one of these functions will return true on | |
1833 | a valid STATUS value. | |
1834 | ||
1835 | These functions are compatible with SCSH. | |
1836 | ||
1837 | *** There are new accessors and setters for the broken-out time vectors | |
48d224d7 JB |
1838 | returned by `localtime', `gmtime', and that ilk. They are: |
1839 | ||
1840 | Component Accessor Setter | |
1841 | ========================= ============ ============ | |
1842 | seconds tm:sec set-tm:sec | |
1843 | minutes tm:min set-tm:min | |
1844 | hours tm:hour set-tm:hour | |
1845 | day of the month tm:mday set-tm:mday | |
1846 | month tm:mon set-tm:mon | |
1847 | year tm:year set-tm:year | |
1848 | day of the week tm:wday set-tm:wday | |
1849 | day in the year tm:yday set-tm:yday | |
1850 | daylight saving time tm:isdst set-tm:isdst | |
1851 | GMT offset, seconds tm:gmtoff set-tm:gmtoff | |
1852 | name of time zone tm:zone set-tm:zone | |
1853 | ||
095936d2 JB |
1854 | *** There are new accessors for the vectors returned by `uname', |
1855 | describing the host system: | |
48d224d7 JB |
1856 | |
1857 | Component Accessor | |
1858 | ============================================== ================ | |
1859 | name of the operating system implementation utsname:sysname | |
1860 | network name of this machine utsname:nodename | |
1861 | release level of the operating system utsname:release | |
1862 | version level of the operating system utsname:version | |
1863 | machine hardware platform utsname:machine | |
1864 | ||
095936d2 JB |
1865 | *** There are new accessors for the vectors returned by `getpw', |
1866 | `getpwnam', `getpwuid', and `getpwent', describing entries from the | |
1867 | system's user database: | |
1868 | ||
1869 | Component Accessor | |
1870 | ====================== ================= | |
1871 | user name passwd:name | |
1872 | user password passwd:passwd | |
1873 | user id passwd:uid | |
1874 | group id passwd:gid | |
1875 | real name passwd:gecos | |
1876 | home directory passwd:dir | |
1877 | shell program passwd:shell | |
1878 | ||
1879 | *** There are new accessors for the vectors returned by `getgr', | |
1880 | `getgrnam', `getgrgid', and `getgrent', describing entries from the | |
1881 | system's group database: | |
1882 | ||
1883 | Component Accessor | |
1884 | ======================= ============ | |
1885 | group name group:name | |
1886 | group password group:passwd | |
1887 | group id group:gid | |
1888 | group members group:mem | |
1889 | ||
1890 | *** There are new accessors for the vectors returned by `gethost', | |
1891 | `gethostbyaddr', `gethostbyname', and `gethostent', describing | |
1892 | internet hosts: | |
1893 | ||
1894 | Component Accessor | |
1895 | ========================= =============== | |
1896 | official name of host hostent:name | |
1897 | alias list hostent:aliases | |
1898 | host address type hostent:addrtype | |
1899 | length of address hostent:length | |
1900 | list of addresses hostent:addr-list | |
1901 | ||
1902 | *** There are new accessors for the vectors returned by `getnet', | |
1903 | `getnetbyaddr', `getnetbyname', and `getnetent', describing internet | |
1904 | networks: | |
1905 | ||
1906 | Component Accessor | |
1907 | ========================= =============== | |
1908 | official name of net netent:name | |
1909 | alias list netent:aliases | |
1910 | net number type netent:addrtype | |
1911 | net number netent:net | |
1912 | ||
1913 | *** There are new accessors for the vectors returned by `getproto', | |
1914 | `getprotobyname', `getprotobynumber', and `getprotoent', describing | |
1915 | internet protocols: | |
1916 | ||
1917 | Component Accessor | |
1918 | ========================= =============== | |
1919 | official protocol name protoent:name | |
1920 | alias list protoent:aliases | |
1921 | protocol number protoent:proto | |
1922 | ||
1923 | *** There are new accessors for the vectors returned by `getserv', | |
1924 | `getservbyname', `getservbyport', and `getservent', describing | |
1925 | internet protocols: | |
1926 | ||
1927 | Component Accessor | |
1928 | ========================= =============== | |
1929 | official service name servent:name | |
1930 | alias list servent:aliases | |
1931 | port number servent:port | |
1932 | protocol to use servent:proto | |
1933 | ||
1934 | *** There are new accessors for the sockaddr structures returned by | |
1935 | `accept', `getsockname', `getpeername', `recvfrom!': | |
1936 | ||
1937 | Component Accessor | |
1938 | ======================================== =============== | |
1939 | address format (`family') sockaddr:fam | |
1940 | path, for file domain addresses sockaddr:path | |
1941 | address, for internet domain addresses sockaddr:addr | |
1942 | TCP or UDP port, for internet sockaddr:port | |
1943 | ||
1944 | *** The `getpwent', `getgrent', `gethostent', `getnetent', | |
1945 | `getprotoent', and `getservent' functions now return #f at the end of | |
1946 | the user database. (They used to throw an exception.) | |
1947 | ||
1948 | Note that calling MUMBLEent function is equivalent to calling the | |
1949 | corresponding MUMBLE function with no arguments. | |
1950 | ||
1951 | *** The `setpwent', `setgrent', `sethostent', `setnetent', | |
1952 | `setprotoent', and `setservent' routines now take no arguments. | |
1953 | ||
1954 | *** The `gethost', `getproto', `getnet', and `getserv' functions now | |
1955 | provide more useful information when they throw an exception. | |
1956 | ||
1957 | *** The `lnaof' function has been renamed to `inet-lnaof'. | |
1958 | ||
1959 | *** Guile now claims to have the `current-time' feature. | |
1960 | ||
1961 | *** The `mktime' function now takes an optional second argument ZONE, | |
1962 | giving the time zone to use for the conversion. ZONE should be a | |
1963 | string, in the same format as expected for the "TZ" environment variable. | |
1964 | ||
1965 | *** The `strptime' function now returns a pair (TIME . COUNT), where | |
1966 | TIME is the parsed time as a vector, and COUNT is the number of | |
1967 | characters from the string left unparsed. This function used to | |
1968 | return the remaining characters as a string. | |
1969 | ||
1970 | *** The `gettimeofday' function has replaced the old `time+ticks' function. | |
1971 | The return value is now (SECONDS . MICROSECONDS); the fractional | |
1972 | component is no longer expressed in "ticks". | |
1973 | ||
1974 | *** The `ticks/sec' constant has been removed, in light of the above change. | |
6685dc83 | 1975 | |
ea00ecba MG |
1976 | * Changes to the gh_ interface |
1977 | ||
1978 | ** gh_eval_str() now returns an SCM object which is the result of the | |
1979 | evaluation | |
1980 | ||
aaef0d2a MG |
1981 | ** gh_scm2str() now copies the Scheme data to a caller-provided C |
1982 | array | |
1983 | ||
1984 | ** gh_scm2newstr() now makes a C array, copies the Scheme data to it, | |
1985 | and returns the array | |
1986 | ||
1987 | ** gh_scm2str0() is gone: there is no need to distinguish | |
1988 | null-terminated from non-null-terminated, since gh_scm2newstr() allows | |
1989 | the user to interpret the data both ways. | |
1990 | ||
f3b1485f JB |
1991 | * Changes to the scm_ interface |
1992 | ||
095936d2 JB |
1993 | ** The new function scm_symbol_value0 provides an easy way to get a |
1994 | symbol's value from C code: | |
1995 | ||
1996 | SCM scm_symbol_value0 (char *NAME) | |
1997 | Return the value of the symbol named by the null-terminated string | |
1998 | NAME in the current module. If the symbol named NAME is unbound in | |
1999 | the current module, return SCM_UNDEFINED. | |
2000 | ||
2001 | ** The new function scm_sysintern0 creates new top-level variables, | |
2002 | without assigning them a value. | |
2003 | ||
2004 | SCM scm_sysintern0 (char *NAME) | |
2005 | Create a new Scheme top-level variable named NAME. NAME is a | |
2006 | null-terminated string. Return the variable's value cell. | |
2007 | ||
2008 | ** The function scm_internal_catch is the guts of catch. It handles | |
2009 | all the mechanics of setting up a catch target, invoking the catch | |
2010 | body, and perhaps invoking the handler if the body does a throw. | |
2011 | ||
2012 | The function is designed to be usable from C code, but is general | |
2013 | enough to implement all the semantics Guile Scheme expects from throw. | |
2014 | ||
2015 | TAG is the catch tag. Typically, this is a symbol, but this function | |
2016 | doesn't actually care about that. | |
2017 | ||
2018 | BODY is a pointer to a C function which runs the body of the catch; | |
2019 | this is the code you can throw from. We call it like this: | |
2020 | BODY (BODY_DATA, JMPBUF) | |
2021 | where: | |
2022 | BODY_DATA is just the BODY_DATA argument we received; we pass it | |
2023 | through to BODY as its first argument. The caller can make | |
2024 | BODY_DATA point to anything useful that BODY might need. | |
2025 | JMPBUF is the Scheme jmpbuf object corresponding to this catch, | |
2026 | which we have just created and initialized. | |
2027 | ||
2028 | HANDLER is a pointer to a C function to deal with a throw to TAG, | |
2029 | should one occur. We call it like this: | |
2030 | HANDLER (HANDLER_DATA, THROWN_TAG, THROW_ARGS) | |
2031 | where | |
2032 | HANDLER_DATA is the HANDLER_DATA argument we recevied; it's the | |
2033 | same idea as BODY_DATA above. | |
2034 | THROWN_TAG is the tag that the user threw to; usually this is | |
2035 | TAG, but it could be something else if TAG was #t (i.e., a | |
2036 | catch-all), or the user threw to a jmpbuf. | |
2037 | THROW_ARGS is the list of arguments the user passed to the THROW | |
2038 | function. | |
2039 | ||
2040 | BODY_DATA is just a pointer we pass through to BODY. HANDLER_DATA | |
2041 | is just a pointer we pass through to HANDLER. We don't actually | |
2042 | use either of those pointers otherwise ourselves. The idea is | |
2043 | that, if our caller wants to communicate something to BODY or | |
2044 | HANDLER, it can pass a pointer to it as MUMBLE_DATA, which BODY and | |
2045 | HANDLER can then use. Think of it as a way to make BODY and | |
2046 | HANDLER closures, not just functions; MUMBLE_DATA points to the | |
2047 | enclosed variables. | |
2048 | ||
2049 | Of course, it's up to the caller to make sure that any data a | |
2050 | MUMBLE_DATA needs is protected from GC. A common way to do this is | |
2051 | to make MUMBLE_DATA a pointer to data stored in an automatic | |
2052 | structure variable; since the collector must scan the stack for | |
2053 | references anyway, this assures that any references in MUMBLE_DATA | |
2054 | will be found. | |
2055 | ||
2056 | ** The new function scm_internal_lazy_catch is exactly like | |
2057 | scm_internal_catch, except: | |
2058 | ||
2059 | - It does not unwind the stack (this is the major difference). | |
2060 | - If handler returns, its value is returned from the throw. | |
2061 | - BODY always receives #f as its JMPBUF argument (since there's no | |
2062 | jmpbuf associated with a lazy catch, because we don't unwind the | |
2063 | stack.) | |
2064 | ||
2065 | ** scm_body_thunk is a new body function you can pass to | |
2066 | scm_internal_catch if you want the body to be like Scheme's `catch' | |
2067 | --- a thunk, or a function of one argument if the tag is #f. | |
2068 | ||
2069 | BODY_DATA is a pointer to a scm_body_thunk_data structure, which | |
2070 | contains the Scheme procedure to invoke as the body, and the tag | |
2071 | we're catching. If the tag is #f, then we pass JMPBUF (created by | |
2072 | scm_internal_catch) to the body procedure; otherwise, the body gets | |
2073 | no arguments. | |
2074 | ||
2075 | ** scm_handle_by_proc is a new handler function you can pass to | |
2076 | scm_internal_catch if you want the handler to act like Scheme's catch | |
2077 | --- call a procedure with the tag and the throw arguments. | |
2078 | ||
2079 | If the user does a throw to this catch, this function runs a handler | |
2080 | procedure written in Scheme. HANDLER_DATA is a pointer to an SCM | |
2081 | variable holding the Scheme procedure object to invoke. It ought to | |
2082 | be a pointer to an automatic variable (i.e., one living on the stack), | |
2083 | or the procedure object should be otherwise protected from GC. | |
2084 | ||
2085 | ** scm_handle_by_message is a new handler function to use with | |
2086 | `scm_internal_catch' if you want Guile to print a message and die. | |
2087 | It's useful for dealing with throws to uncaught keys at the top level. | |
2088 | ||
2089 | HANDLER_DATA, if non-zero, is assumed to be a char * pointing to a | |
2090 | message header to print; if zero, we use "guile" instead. That | |
2091 | text is followed by a colon, then the message described by ARGS. | |
2092 | ||
2093 | ** The return type of scm_boot_guile is now void; the function does | |
2094 | not return a value, and indeed, never returns at all. | |
2095 | ||
f3b1485f JB |
2096 | ** The new function scm_shell makes it easy for user applications to |
2097 | process command-line arguments in a way that is compatible with the | |
2098 | stand-alone guile interpreter (which is in turn compatible with SCSH, | |
2099 | the Scheme shell). | |
2100 | ||
2101 | To use the scm_shell function, first initialize any guile modules | |
2102 | linked into your application, and then call scm_shell with the values | |
7ed46dc8 | 2103 | of ARGC and ARGV your `main' function received. scm_shell will add |
f3b1485f JB |
2104 | any SCSH-style meta-arguments from the top of the script file to the |
2105 | argument vector, and then process the command-line arguments. This | |
2106 | generally means loading a script file or starting up an interactive | |
2107 | command interpreter. For details, see "Changes to the stand-alone | |
2108 | interpreter" above. | |
2109 | ||
095936d2 JB |
2110 | ** The new functions scm_get_meta_args and scm_count_argv help you |
2111 | implement the SCSH-style meta-argument, `\'. | |
2112 | ||
2113 | char **scm_get_meta_args (int ARGC, char **ARGV) | |
2114 | If the second element of ARGV is a string consisting of a single | |
2115 | backslash character (i.e. "\\" in Scheme notation), open the file | |
2116 | named by the following argument, parse arguments from it, and return | |
2117 | the spliced command line. The returned array is terminated by a | |
2118 | null pointer. | |
2119 | ||
2120 | For details of argument parsing, see above, under "guile now accepts | |
2121 | command-line arguments compatible with SCSH..." | |
2122 | ||
2123 | int scm_count_argv (char **ARGV) | |
2124 | Count the arguments in ARGV, assuming it is terminated by a null | |
2125 | pointer. | |
2126 | ||
2127 | For an example of how these functions might be used, see the source | |
2128 | code for the function scm_shell in libguile/script.c. | |
2129 | ||
2130 | You will usually want to use scm_shell instead of calling this | |
2131 | function yourself. | |
2132 | ||
2133 | ** The new function scm_compile_shell_switches turns an array of | |
2134 | command-line arguments into Scheme code to carry out the actions they | |
2135 | describe. Given ARGC and ARGV, it returns a Scheme expression to | |
2136 | evaluate, and calls scm_set_program_arguments to make any remaining | |
2137 | command-line arguments available to the Scheme code. For example, | |
2138 | given the following arguments: | |
2139 | ||
2140 | -e main -s ekko a speckled gecko | |
2141 | ||
2142 | scm_set_program_arguments will return the following expression: | |
2143 | ||
2144 | (begin (load "ekko") (main (command-line)) (quit)) | |
2145 | ||
2146 | You will usually want to use scm_shell instead of calling this | |
2147 | function yourself. | |
2148 | ||
2149 | ** The function scm_shell_usage prints a usage message appropriate for | |
2150 | an interpreter that uses scm_compile_shell_switches to handle its | |
2151 | command-line arguments. | |
2152 | ||
2153 | void scm_shell_usage (int FATAL, char *MESSAGE) | |
2154 | Print a usage message to the standard error output. If MESSAGE is | |
2155 | non-zero, write it before the usage message, followed by a newline. | |
2156 | If FATAL is non-zero, exit the process, using FATAL as the | |
2157 | termination status. (If you want to be compatible with Guile, | |
2158 | always use 1 as the exit status when terminating due to command-line | |
2159 | usage problems.) | |
2160 | ||
2161 | You will usually want to use scm_shell instead of calling this | |
2162 | function yourself. | |
48d224d7 JB |
2163 | |
2164 | ** scm_eval_0str now returns SCM_UNSPECIFIED if the string contains no | |
095936d2 JB |
2165 | expressions. It used to return SCM_EOL. Earth-shattering. |
2166 | ||
2167 | ** The macros for declaring scheme objects in C code have been | |
2168 | rearranged slightly. They are now: | |
2169 | ||
2170 | SCM_SYMBOL (C_NAME, SCHEME_NAME) | |
2171 | Declare a static SCM variable named C_NAME, and initialize it to | |
2172 | point to the Scheme symbol whose name is SCHEME_NAME. C_NAME should | |
2173 | be a C identifier, and SCHEME_NAME should be a C string. | |
2174 | ||
2175 | SCM_GLOBAL_SYMBOL (C_NAME, SCHEME_NAME) | |
2176 | Just like SCM_SYMBOL, but make C_NAME globally visible. | |
2177 | ||
2178 | SCM_VCELL (C_NAME, SCHEME_NAME) | |
2179 | Create a global variable at the Scheme level named SCHEME_NAME. | |
2180 | Declare a static SCM variable named C_NAME, and initialize it to | |
2181 | point to the Scheme variable's value cell. | |
2182 | ||
2183 | SCM_GLOBAL_VCELL (C_NAME, SCHEME_NAME) | |
2184 | Just like SCM_VCELL, but make C_NAME globally visible. | |
2185 | ||
2186 | The `guile-snarf' script writes initialization code for these macros | |
2187 | to its standard output, given C source code as input. | |
2188 | ||
2189 | The SCM_GLOBAL macro is gone. | |
2190 | ||
2191 | ** The scm_read_line and scm_read_line_x functions have been replaced | |
2192 | by Scheme code based on the %read-delimited! procedure (known to C | |
2193 | code as scm_read_delimited_x). See its description above for more | |
2194 | information. | |
48d224d7 | 2195 | |
095936d2 JB |
2196 | ** The function scm_sys_open has been renamed to scm_open. It now |
2197 | returns a port instead of an FD object. | |
ea00ecba | 2198 | |
095936d2 JB |
2199 | * The dynamic linking support has changed. For more information, see |
2200 | libguile/DYNAMIC-LINKING. | |
ea00ecba | 2201 | |
f7b47737 JB |
2202 | \f |
2203 | Guile 1.0b3 | |
3065a62a | 2204 | |
f3b1485f JB |
2205 | User-visible changes from Thursday, September 5, 1996 until Guile 1.0 |
2206 | (Sun 5 Jan 1997): | |
3065a62a | 2207 | |
4b521edb | 2208 | * Changes to the 'guile' program: |
3065a62a | 2209 | |
4b521edb JB |
2210 | ** Guile now loads some new files when it starts up. Guile first |
2211 | searches the load path for init.scm, and loads it if found. Then, if | |
2212 | Guile is not being used to execute a script, and the user's home | |
2213 | directory contains a file named `.guile', Guile loads that. | |
c6486f8a | 2214 | |
4b521edb | 2215 | ** You can now use Guile as a shell script interpreter. |
3065a62a JB |
2216 | |
2217 | To paraphrase the SCSH manual: | |
2218 | ||
2219 | When Unix tries to execute an executable file whose first two | |
2220 | characters are the `#!', it treats the file not as machine code to | |
2221 | be directly executed by the native processor, but as source code | |
2222 | to be executed by some interpreter. The interpreter to use is | |
2223 | specified immediately after the #! sequence on the first line of | |
2224 | the source file. The kernel reads in the name of the interpreter, | |
2225 | and executes that instead. It passes the interpreter the source | |
2226 | filename as its first argument, with the original arguments | |
2227 | following. Consult the Unix man page for the `exec' system call | |
2228 | for more information. | |
2229 | ||
1a1945be JB |
2230 | Now you can use Guile as an interpreter, using a mechanism which is a |
2231 | compatible subset of that provided by SCSH. | |
2232 | ||
3065a62a JB |
2233 | Guile now recognizes a '-s' command line switch, whose argument is the |
2234 | name of a file of Scheme code to load. It also treats the two | |
2235 | characters `#!' as the start of a comment, terminated by `!#'. Thus, | |
2236 | to make a file of Scheme code directly executable by Unix, insert the | |
2237 | following two lines at the top of the file: | |
2238 | ||
2239 | #!/usr/local/bin/guile -s | |
2240 | !# | |
2241 | ||
2242 | Guile treats the argument of the `-s' command-line switch as the name | |
2243 | of a file of Scheme code to load, and treats the sequence `#!' as the | |
2244 | start of a block comment, terminated by `!#'. | |
2245 | ||
2246 | For example, here's a version of 'echo' written in Scheme: | |
2247 | ||
2248 | #!/usr/local/bin/guile -s | |
2249 | !# | |
2250 | (let loop ((args (cdr (program-arguments)))) | |
2251 | (if (pair? args) | |
2252 | (begin | |
2253 | (display (car args)) | |
2254 | (if (pair? (cdr args)) | |
2255 | (display " ")) | |
2256 | (loop (cdr args))))) | |
2257 | (newline) | |
2258 | ||
2259 | Why does `#!' start a block comment terminated by `!#', instead of the | |
2260 | end of the line? That is the notation SCSH uses, and although we | |
2261 | don't yet support the other SCSH features that motivate that choice, | |
2262 | we would like to be backward-compatible with any existing Guile | |
3763761c JB |
2263 | scripts once we do. Furthermore, if the path to Guile on your system |
2264 | is too long for your kernel, you can start the script with this | |
2265 | horrible hack: | |
2266 | ||
2267 | #!/bin/sh | |
2268 | exec /really/long/path/to/guile -s "$0" ${1+"$@"} | |
2269 | !# | |
3065a62a JB |
2270 | |
2271 | Note that some very old Unix systems don't support the `#!' syntax. | |
2272 | ||
c6486f8a | 2273 | |
4b521edb | 2274 | ** You can now run Guile without installing it. |
6685dc83 JB |
2275 | |
2276 | Previous versions of the interactive Guile interpreter (`guile') | |
2277 | couldn't start up unless Guile's Scheme library had been installed; | |
2278 | they used the value of the environment variable `SCHEME_LOAD_PATH' | |
2279 | later on in the startup process, but not to find the startup code | |
2280 | itself. Now Guile uses `SCHEME_LOAD_PATH' in all searches for Scheme | |
2281 | code. | |
2282 | ||
2283 | To run Guile without installing it, build it in the normal way, and | |
2284 | then set the environment variable `SCHEME_LOAD_PATH' to a | |
2285 | colon-separated list of directories, including the top-level directory | |
2286 | of the Guile sources. For example, if you unpacked Guile so that the | |
2287 | full filename of this NEWS file is /home/jimb/guile-1.0b3/NEWS, then | |
2288 | you might say | |
2289 | ||
2290 | export SCHEME_LOAD_PATH=/home/jimb/my-scheme:/home/jimb/guile-1.0b3 | |
2291 | ||
c6486f8a | 2292 | |
4b521edb JB |
2293 | ** Guile's read-eval-print loop no longer prints #<unspecified> |
2294 | results. If the user wants to see this, she can evaluate the | |
2295 | expression (assert-repl-print-unspecified #t), perhaps in her startup | |
48d224d7 | 2296 | file. |
6685dc83 | 2297 | |
4b521edb JB |
2298 | ** Guile no longer shows backtraces by default when an error occurs; |
2299 | however, it does display a message saying how to get one, and how to | |
2300 | request that they be displayed by default. After an error, evaluate | |
2301 | (backtrace) | |
2302 | to see a backtrace, and | |
2303 | (debug-enable 'backtrace) | |
2304 | to see them by default. | |
6685dc83 | 2305 | |
6685dc83 | 2306 | |
d9fb83d9 | 2307 | |
4b521edb JB |
2308 | * Changes to Guile Scheme: |
2309 | ||
2310 | ** Guile now distinguishes between #f and the empty list. | |
2311 | ||
2312 | This is for compatibility with the IEEE standard, the (possibly) | |
2313 | upcoming Revised^5 Report on Scheme, and many extant Scheme | |
2314 | implementations. | |
2315 | ||
2316 | Guile used to have #f and '() denote the same object, to make Scheme's | |
2317 | type system more compatible with Emacs Lisp's. However, the change | |
2318 | caused too much trouble for Scheme programmers, and we found another | |
2319 | way to reconcile Emacs Lisp with Scheme that didn't require this. | |
2320 | ||
2321 | ||
2322 | ** Guile's delq, delv, delete functions, and their destructive | |
c6486f8a JB |
2323 | counterparts, delq!, delv!, and delete!, now remove all matching |
2324 | elements from the list, not just the first. This matches the behavior | |
2325 | of the corresponding Emacs Lisp functions, and (I believe) the Maclisp | |
2326 | functions which inspired them. | |
2327 | ||
2328 | I recognize that this change may break code in subtle ways, but it | |
2329 | seems best to make the change before the FSF's first Guile release, | |
2330 | rather than after. | |
2331 | ||
2332 | ||
4b521edb | 2333 | ** The compiled-library-path function has been deleted from libguile. |
6685dc83 | 2334 | |
4b521edb | 2335 | ** The facilities for loading Scheme source files have changed. |
c6486f8a | 2336 | |
4b521edb | 2337 | *** The variable %load-path now tells Guile which directories to search |
6685dc83 JB |
2338 | for Scheme code. Its value is a list of strings, each of which names |
2339 | a directory. | |
2340 | ||
4b521edb JB |
2341 | *** The variable %load-extensions now tells Guile which extensions to |
2342 | try appending to a filename when searching the load path. Its value | |
2343 | is a list of strings. Its default value is ("" ".scm"). | |
2344 | ||
2345 | *** (%search-load-path FILENAME) searches the directories listed in the | |
2346 | value of the %load-path variable for a Scheme file named FILENAME, | |
2347 | with all the extensions listed in %load-extensions. If it finds a | |
2348 | match, then it returns its full filename. If FILENAME is absolute, it | |
2349 | returns it unchanged. Otherwise, it returns #f. | |
6685dc83 | 2350 | |
4b521edb JB |
2351 | %search-load-path will not return matches that refer to directories. |
2352 | ||
2353 | *** (primitive-load FILENAME :optional CASE-INSENSITIVE-P SHARP) | |
2354 | uses %seach-load-path to find a file named FILENAME, and loads it if | |
2355 | it finds it. If it can't read FILENAME for any reason, it throws an | |
2356 | error. | |
6685dc83 JB |
2357 | |
2358 | The arguments CASE-INSENSITIVE-P and SHARP are interpreted as by the | |
4b521edb JB |
2359 | `read' function. |
2360 | ||
2361 | *** load uses the same searching semantics as primitive-load. | |
2362 | ||
2363 | *** The functions %try-load, try-load-with-path, %load, load-with-path, | |
2364 | basic-try-load-with-path, basic-load-with-path, try-load-module-with- | |
2365 | path, and load-module-with-path have been deleted. The functions | |
2366 | above should serve their purposes. | |
2367 | ||
2368 | *** If the value of the variable %load-hook is a procedure, | |
2369 | `primitive-load' applies its value to the name of the file being | |
2370 | loaded (without the load path directory name prepended). If its value | |
2371 | is #f, it is ignored. Otherwise, an error occurs. | |
2372 | ||
2373 | This is mostly useful for printing load notification messages. | |
2374 | ||
2375 | ||
2376 | ** The function `eval!' is no longer accessible from the scheme level. | |
2377 | We can't allow operations which introduce glocs into the scheme level, | |
2378 | because Guile's type system can't handle these as data. Use `eval' or | |
2379 | `read-and-eval!' (see below) as replacement. | |
2380 | ||
2381 | ** The new function read-and-eval! reads an expression from PORT, | |
2382 | evaluates it, and returns the result. This is more efficient than | |
2383 | simply calling `read' and `eval', since it is not necessary to make a | |
2384 | copy of the expression for the evaluator to munge. | |
2385 | ||
2386 | Its optional arguments CASE_INSENSITIVE_P and SHARP are interpreted as | |
2387 | for the `read' function. | |
2388 | ||
2389 | ||
2390 | ** The function `int?' has been removed; its definition was identical | |
2391 | to that of `integer?'. | |
2392 | ||
2393 | ** The functions `<?', `<?', `<=?', `=?', `>?', and `>=?'. Code should | |
2394 | use the R4RS names for these functions. | |
2395 | ||
2396 | ** The function object-properties no longer returns the hash handle; | |
2397 | it simply returns the object's property list. | |
2398 | ||
2399 | ** Many functions have been changed to throw errors, instead of | |
2400 | returning #f on failure. The point of providing exception handling in | |
2401 | the language is to simplify the logic of user code, but this is less | |
2402 | useful if Guile's primitives don't throw exceptions. | |
2403 | ||
2404 | ** The function `fileno' has been renamed from `%fileno'. | |
2405 | ||
2406 | ** The function primitive-mode->fdes returns #t or #f now, not 1 or 0. | |
2407 | ||
2408 | ||
2409 | * Changes to Guile's C interface: | |
2410 | ||
2411 | ** The library's initialization procedure has been simplified. | |
2412 | scm_boot_guile now has the prototype: | |
2413 | ||
2414 | void scm_boot_guile (int ARGC, | |
2415 | char **ARGV, | |
2416 | void (*main_func) (), | |
2417 | void *closure); | |
2418 | ||
2419 | scm_boot_guile calls MAIN_FUNC, passing it CLOSURE, ARGC, and ARGV. | |
2420 | MAIN_FUNC should do all the work of the program (initializing other | |
2421 | packages, reading user input, etc.) before returning. When MAIN_FUNC | |
2422 | returns, call exit (0); this function never returns. If you want some | |
2423 | other exit value, MAIN_FUNC may call exit itself. | |
2424 | ||
2425 | scm_boot_guile arranges for program-arguments to return the strings | |
2426 | given by ARGC and ARGV. If MAIN_FUNC modifies ARGC/ARGV, should call | |
2427 | scm_set_program_arguments with the final list, so Scheme code will | |
2428 | know which arguments have been processed. | |
2429 | ||
2430 | scm_boot_guile establishes a catch-all catch handler which prints an | |
2431 | error message and exits the process. This means that Guile exits in a | |
2432 | coherent way when system errors occur and the user isn't prepared to | |
2433 | handle it. If the user doesn't like this behavior, they can establish | |
2434 | their own universal catcher in MAIN_FUNC to shadow this one. | |
2435 | ||
2436 | Why must the caller do all the real work from MAIN_FUNC? The garbage | |
2437 | collector assumes that all local variables of type SCM will be above | |
2438 | scm_boot_guile's stack frame on the stack. If you try to manipulate | |
2439 | SCM values after this function returns, it's the luck of the draw | |
2440 | whether the GC will be able to find the objects you allocate. So, | |
2441 | scm_boot_guile function exits, rather than returning, to discourage | |
2442 | people from making that mistake. | |
2443 | ||
2444 | The IN, OUT, and ERR arguments were removed; there are other | |
2445 | convenient ways to override these when desired. | |
2446 | ||
2447 | The RESULT argument was deleted; this function should never return. | |
2448 | ||
2449 | The BOOT_CMD argument was deleted; the MAIN_FUNC argument is more | |
2450 | general. | |
2451 | ||
2452 | ||
2453 | ** Guile's header files should no longer conflict with your system's | |
2454 | header files. | |
2455 | ||
2456 | In order to compile code which #included <libguile.h>, previous | |
2457 | versions of Guile required you to add a directory containing all the | |
2458 | Guile header files to your #include path. This was a problem, since | |
2459 | Guile's header files have names which conflict with many systems' | |
2460 | header files. | |
2461 | ||
2462 | Now only <libguile.h> need appear in your #include path; you must | |
2463 | refer to all Guile's other header files as <libguile/mumble.h>. | |
2464 | Guile's installation procedure puts libguile.h in $(includedir), and | |
2465 | the rest in $(includedir)/libguile. | |
2466 | ||
2467 | ||
2468 | ** Two new C functions, scm_protect_object and scm_unprotect_object, | |
2469 | have been added to the Guile library. | |
2470 | ||
2471 | scm_protect_object (OBJ) protects OBJ from the garbage collector. | |
2472 | OBJ will not be freed, even if all other references are dropped, | |
2473 | until someone does scm_unprotect_object (OBJ). Both functions | |
2474 | return OBJ. | |
2475 | ||
2476 | Note that calls to scm_protect_object do not nest. You can call | |
2477 | scm_protect_object any number of times on a given object, and the | |
2478 | next call to scm_unprotect_object will unprotect it completely. | |
2479 | ||
2480 | Basically, scm_protect_object and scm_unprotect_object just | |
2481 | maintain a list of references to things. Since the GC knows about | |
2482 | this list, all objects it mentions stay alive. scm_protect_object | |
2483 | adds its argument to the list; scm_unprotect_object remove its | |
2484 | argument from the list. | |
2485 | ||
2486 | ||
2487 | ** scm_eval_0str now returns the value of the last expression | |
2488 | evaluated. | |
2489 | ||
2490 | ** The new function scm_read_0str reads an s-expression from a | |
2491 | null-terminated string, and returns it. | |
2492 | ||
2493 | ** The new function `scm_stdio_to_port' converts a STDIO file pointer | |
2494 | to a Scheme port object. | |
2495 | ||
2496 | ** The new function `scm_set_program_arguments' allows C code to set | |
e80c8fea | 2497 | the value returned by the Scheme `program-arguments' function. |
6685dc83 | 2498 | |
6685dc83 | 2499 | \f |
1a1945be JB |
2500 | Older changes: |
2501 | ||
2502 | * Guile no longer includes sophisticated Tcl/Tk support. | |
2503 | ||
2504 | The old Tcl/Tk support was unsatisfying to us, because it required the | |
2505 | user to link against the Tcl library, as well as Tk and Guile. The | |
2506 | interface was also un-lispy, in that it preserved Tcl/Tk's practice of | |
2507 | referring to widgets by names, rather than exporting widgets to Scheme | |
2508 | code as a special datatype. | |
2509 | ||
2510 | In the Usenix Tk Developer's Workshop held in July 1996, the Tcl/Tk | |
2511 | maintainers described some very interesting changes in progress to the | |
2512 | Tcl/Tk internals, which would facilitate clean interfaces between lone | |
2513 | Tk and other interpreters --- even for garbage-collected languages | |
2514 | like Scheme. They expected the new Tk to be publicly available in the | |
2515 | fall of 1996. | |
2516 | ||
2517 | Since it seems that Guile might soon have a new, cleaner interface to | |
2518 | lone Tk, and that the old Guile/Tk glue code would probably need to be | |
2519 | completely rewritten, we (Jim Blandy and Richard Stallman) have | |
2520 | decided not to support the old code. We'll spend the time instead on | |
2521 | a good interface to the newer Tk, as soon as it is available. | |
5c54da76 | 2522 | |
8512dea6 | 2523 | Until then, gtcltk-lib provides trivial, low-maintenance functionality. |
deb95d71 | 2524 | |
5c54da76 JB |
2525 | \f |
2526 | Copyright information: | |
2527 | ||
ea00ecba | 2528 | Copyright (C) 1996,1997 Free Software Foundation, Inc. |
5c54da76 JB |
2529 | |
2530 | Permission is granted to anyone to make or distribute verbatim copies | |
2531 | of this document as received, in any medium, provided that the | |
2532 | copyright notice and this permission notice are preserved, | |
2533 | thus giving the recipient permission to redistribute in turn. | |
2534 | ||
2535 | Permission is granted to distribute modified versions | |
2536 | of this document, or of portions of it, | |
2537 | under the above conditions, provided also that they | |
2538 | carry prominent notices stating who last changed them. | |
2539 | ||
48d224d7 JB |
2540 | \f |
2541 | Local variables: | |
2542 | mode: outline | |
2543 | paragraph-separate: "[ \f]*$" | |
2544 | end: | |
2545 |