Commit | Line | Data |
---|---|---|
f7b47737 JB |
1 | Guile NEWS --- history of user-visible changes. -*- text -*- |
2 | Copyright (C) 1996, 1997 Free Software Foundation, Inc. | |
5c54da76 JB |
3 | See the end for copying conditions. |
4 | ||
16f2ebea | 5 | Please send Guile bug reports to bug-guile@prep.ai.mit.edu. |
5c54da76 | 6 | \f |
c484bf7f JB |
7 | Changes since Guile 1.2: |
8 | ||
9 | * Changes to the distribution | |
10 | ||
11 | * Changes to the stand-alone interpreter | |
12 | ||
13 | * Changes to the procedure for linking libguile with your programs | |
14 | ||
15 | * Changes to Scheme functions and syntax | |
7ad3c1e7 | 16 | |
9c3fb66f MV |
17 | ** The detection of circular references has been extended to structs. |
18 | That is, a structure that -- in the process of being printed -- prints | |
19 | itself does not lead to infinite recursion. | |
20 | ||
04c76b58 MV |
21 | ** There is now some basic support for fluids. Please read |
22 | "libguile/fluid.h" to find out more. It is accessible from Scheme with | |
9c3fb66f MV |
23 | the following functions and macros: |
24 | ||
25 | Function: make-fluid | |
26 | ||
27 | Create a new fluid object. Fluids are not special variables or | |
28 | some other extension to the semantics of Scheme, but rather | |
29 | ordinary Scheme objects. You can store them into variables (that | |
30 | are still lexically scoped, of course) or into any other place you | |
31 | like. Every fluid has a initial value of `#f'. | |
04c76b58 | 32 | |
9c3fb66f | 33 | Function: fluid? OBJ |
04c76b58 | 34 | |
9c3fb66f | 35 | Test whether OBJ is a fluid. |
04c76b58 | 36 | |
9c3fb66f MV |
37 | Function: fluid-ref FLUID |
38 | Function: fluid-set! FLUID VAL | |
04c76b58 MV |
39 | |
40 | Access/modify the fluid FLUID. Modifications are only visible | |
41 | within the current dynamic root (that includes threads). | |
42 | ||
9c3fb66f MV |
43 | Function: with-fluids* FLUIDS VALUES THUNK |
44 | ||
45 | FLUIDS is a list of fluids and VALUES a corresponding list of | |
46 | values for these fluids. Before THUNK gets called the values are | |
47 | installed in the fluids and the old values of the fluids are | |
48 | saved in the VALUES list. When the flow of control leaves THUNK | |
49 | or reenters it, the values get swapped again. You might think of | |
50 | this as a `safe-fluid-excursion'. Note that the VALUES list is | |
51 | modified by `with-fluids*'. | |
52 | ||
53 | Macro: with-fluids ((FLUID VALUE) ...) FORM ... | |
54 | ||
55 | The same as `with-fluids*' but with a different syntax. It looks | |
56 | just like `let', but both FLUID and VALUE are evaluated. Remember, | |
57 | fluids are not special variables but ordinary objects. FLUID | |
58 | should evaluate to a fluid. | |
04c76b58 | 59 | |
64d01d13 GH |
60 | * Changes to system call interfaces: |
61 | ||
62 | ** close-port, close-input-port and close-output-port now return a | |
63 | boolean instead of an `unspecified' object. #t means that the port | |
64 | was successfully closed, while #f means it was already closed. It is | |
65 | also now possible for these procedures to raise an exception if an | |
66 | error occurs (some errors from write can be delayed until close.) | |
67 | ||
68 | ** The following new procedures have been added (most use scsh | |
69 | interfaces): | |
70 | ||
71 | ** close PORT/FD | |
72 | Similar to close-port, but also works on file descriptors. A side | |
73 | effect of closing a file descriptor is that any ports using that file | |
74 | descriptor are moved to a different file descriptor and have | |
75 | their revealed counts set to zero. | |
76 | ||
77 | The next five procedures perform a dup2 system call, if NEWFD (an | |
78 | integer) is supplied, otherwise a dup. The file descriptor to be | |
79 | duplicated can be supplied as an integer or wrapped in a port. The | |
80 | type of value returned varies depending on which procedure is used. | |
81 | ||
82 | All procedures also have the side effect when performing dup2 that any | |
83 | ports using NEWFD are moved to a different file descriptor and have | |
84 | their revealed counts set to zero. | |
85 | ||
86 | ** dup->fdes PORT/FD [NEWFD] | |
87 | Returns an integer file descriptor. | |
88 | ||
89 | ** dup->inport PORT/FD [NEWFD] | |
90 | Returns a new input port using the new file descriptor. | |
91 | ||
92 | ** dup->outport PORT/FD [NEWFD] | |
93 | Returns a new output port using the new file descriptor. | |
94 | ||
95 | ** dup PORT/FD [NEWFD] | |
96 | Returns a new port if PORT/FD is a port, with the same mode as the | |
97 | supplied port, otherwise returns an integer file descriptor. | |
98 | ||
99 | ** dup->port PORT/FD MODE [NEWFD] | |
100 | Returns a new port using the new file descriptor. MODE supplies a | |
101 | mode string for the port (as for `open-file'). | |
102 | ||
103 | ** primitive-dup PORT/FD | |
104 | Performs a dup system call on the file descriptor FD, or the file | |
105 | descriptor underlying PORT and returns a new integer file descriptor. | |
106 | ||
107 | ** primitive-dup2 PORT/FD NEWFD | |
108 | ||
109 | Performs a dup2 system call on the file descriptor FD, or the file | |
110 | descriptor underlying PORT, using NEWFD (an integer) as the target | |
111 | file descriptor. Any ports using NEWFD are moved to a different file | |
112 | descriptor and have their revealed counts set to zero. The value | |
113 | returned is NEWFD. | |
114 | ||
115 | ** port->fdes PORT | |
116 | Returns the integer file descriptor underlying PORT. As a | |
117 | side effect the revealed count of PORT is incremented. | |
118 | ||
119 | ** fdes->inport FDES | |
120 | Returns an existing input port which has FDES as its underlying file | |
121 | descriptor, if one exists, and increments its revealed count. | |
122 | Otherwise, returns a new input port with a revealed count of 1. | |
123 | ||
124 | ** fdes->outport FDES | |
125 | Returns an existing output port which has FDES as its underlying file | |
126 | descriptor, if one exists, and increments its revealed count. | |
127 | Otherwise, returns a new output port with a revealed count of 1. | |
128 | ||
956055a9 GH |
129 | ** setenv [NAME] [VALUE] |
130 | If VALUE is `#f', removes NAME from the environment. Otherwise | |
131 | adds the string NAME=VALUE to the environment, replacing any previous | |
132 | value for NAME. | |
133 | ||
64d01d13 GH |
134 | ** primitive-exit [STATUS] |
135 | Terminates the current process without unwinding the Scheme stack. | |
136 | This would usually be used after a fork. | |
7ad3c1e7 | 137 | |
c484bf7f JB |
138 | * Changes to the gh_ interface |
139 | ||
140 | * Changes to the scm_ interface | |
141 | ||
142 | \f | |
143 | Changes in Guile 1.2 (released Tuesday, June 24 1997): | |
cf78e9e8 | 144 | |
737c9113 JB |
145 | * Changes to the distribution |
146 | ||
832b09ed JB |
147 | ** Nightly snapshots are now available from ftp.red-bean.com. |
148 | The old server, ftp.cyclic.com, has been relinquished to its rightful | |
149 | owner. | |
150 | ||
151 | Nightly snapshots of the Guile development sources are now available via | |
152 | anonymous FTP from ftp.red-bean.com, as /pub/guile/guile-snap.tar.gz. | |
153 | ||
154 | Via the web, that's: ftp://ftp.red-bean.com/pub/guile/guile-snap.tar.gz | |
155 | For getit, that's: ftp.red-bean.com:/pub/guile/guile-snap.tar.gz | |
156 | ||
0fcab5ed JB |
157 | ** To run Guile without installing it, the procedure has changed a bit. |
158 | ||
159 | If you used a separate build directory to compile Guile, you'll need | |
160 | to include the build directory in SCHEME_LOAD_PATH, as well as the | |
161 | source directory. See the `INSTALL' file for examples. | |
162 | ||
737c9113 JB |
163 | * Changes to the procedure for linking libguile with your programs |
164 | ||
94982a4e JB |
165 | ** The standard Guile load path for Scheme code now includes |
166 | $(datadir)/guile (usually /usr/local/share/guile). This means that | |
167 | you can install your own Scheme files there, and Guile will find them. | |
168 | (Previous versions of Guile only checked a directory whose name | |
169 | contained the Guile version number, so you had to re-install or move | |
170 | your Scheme sources each time you installed a fresh version of Guile.) | |
171 | ||
172 | The load path also includes $(datadir)/guile/site; we recommend | |
173 | putting individual Scheme files there. If you want to install a | |
174 | package with multiple source files, create a directory for them under | |
175 | $(datadir)/guile. | |
176 | ||
177 | ** Guile 1.2 will now use the Rx regular expression library, if it is | |
178 | installed on your system. When you are linking libguile into your own | |
179 | programs, this means you will have to link against -lguile, -lqt (if | |
180 | you configured Guile with thread support), and -lrx. | |
27590f82 JB |
181 | |
182 | If you are using autoconf to generate configuration scripts for your | |
183 | application, the following lines should suffice to add the appropriate | |
184 | libraries to your link command: | |
185 | ||
186 | ### Find Rx, quickthreads and libguile. | |
187 | AC_CHECK_LIB(rx, main) | |
188 | AC_CHECK_LIB(qt, main) | |
189 | AC_CHECK_LIB(guile, scm_shell) | |
190 | ||
94982a4e JB |
191 | The Guile 1.2 distribution does not contain sources for the Rx |
192 | library, as Guile 1.0 did. If you want to use Rx, you'll need to | |
193 | retrieve it from a GNU FTP site and install it separately. | |
194 | ||
b83b8bee JB |
195 | * Changes to Scheme functions and syntax |
196 | ||
e035e7e6 MV |
197 | ** The dynamic linking features of Guile are now enabled by default. |
198 | You can disable them by giving the `--disable-dynamic-linking' option | |
199 | to configure. | |
200 | ||
e035e7e6 MV |
201 | (dynamic-link FILENAME) |
202 | ||
203 | Find the object file denoted by FILENAME (a string) and link it | |
204 | into the running Guile application. When everything works out, | |
205 | return a Scheme object suitable for representing the linked object | |
206 | file. Otherwise an error is thrown. How object files are | |
207 | searched is system dependent. | |
208 | ||
209 | (dynamic-object? VAL) | |
210 | ||
211 | Determine whether VAL represents a dynamically linked object file. | |
212 | ||
213 | (dynamic-unlink DYNOBJ) | |
214 | ||
215 | Unlink the indicated object file from the application. DYNOBJ | |
216 | should be one of the values returned by `dynamic-link'. | |
217 | ||
218 | (dynamic-func FUNCTION DYNOBJ) | |
219 | ||
220 | Search the C function indicated by FUNCTION (a string or symbol) | |
221 | in DYNOBJ and return some Scheme object that can later be used | |
222 | with `dynamic-call' to actually call this function. Right now, | |
223 | these Scheme objects are formed by casting the address of the | |
224 | function to `long' and converting this number to its Scheme | |
225 | representation. | |
226 | ||
227 | (dynamic-call FUNCTION DYNOBJ) | |
228 | ||
229 | Call the C function indicated by FUNCTION and DYNOBJ. The | |
230 | function is passed no arguments and its return value is ignored. | |
231 | When FUNCTION is something returned by `dynamic-func', call that | |
232 | function and ignore DYNOBJ. When FUNCTION is a string (or symbol, | |
233 | etc.), look it up in DYNOBJ; this is equivalent to | |
234 | ||
235 | (dynamic-call (dynamic-func FUNCTION DYNOBJ) #f) | |
236 | ||
237 | Interrupts are deferred while the C function is executing (with | |
238 | SCM_DEFER_INTS/SCM_ALLOW_INTS). | |
239 | ||
240 | (dynamic-args-call FUNCTION DYNOBJ ARGS) | |
241 | ||
242 | Call the C function indicated by FUNCTION and DYNOBJ, but pass it | |
243 | some arguments and return its return value. The C function is | |
244 | expected to take two arguments and return an `int', just like | |
245 | `main': | |
246 | ||
247 | int c_func (int argc, char **argv); | |
248 | ||
249 | ARGS must be a list of strings and is converted into an array of | |
250 | `char *'. The array is passed in ARGV and its size in ARGC. The | |
251 | return value is converted to a Scheme number and returned from the | |
252 | call to `dynamic-args-call'. | |
253 | ||
0fcab5ed JB |
254 | When dynamic linking is disabled or not supported on your system, |
255 | the above functions throw errors, but they are still available. | |
256 | ||
e035e7e6 MV |
257 | Here is a small example that works on GNU/Linux: |
258 | ||
259 | (define libc-obj (dynamic-link "libc.so")) | |
260 | (dynamic-args-call 'rand libc-obj '()) | |
261 | ||
262 | See the file `libguile/DYNAMIC-LINKING' for additional comments. | |
263 | ||
27590f82 JB |
264 | ** The #/ syntax for module names is depreciated, and will be removed |
265 | in a future version of Guile. Instead of | |
266 | ||
267 | #/foo/bar/baz | |
268 | ||
269 | instead write | |
270 | ||
271 | (foo bar baz) | |
272 | ||
273 | The latter syntax is more consistent with existing Lisp practice. | |
274 | ||
5dade857 MV |
275 | ** Guile now does fancier printing of structures. Structures are the |
276 | underlying implementation for records, which in turn are used to | |
277 | implement modules, so all of these object now print differently and in | |
278 | a more informative way. | |
279 | ||
161029df JB |
280 | The Scheme printer will examine the builtin variable *struct-printer* |
281 | whenever it needs to print a structure object. When this variable is | |
282 | not `#f' it is deemed to be a procedure and will be applied to the | |
283 | structure object and the output port. When *struct-printer* is `#f' | |
284 | or the procedure return `#f' the structure object will be printed in | |
285 | the boring #<struct 80458270> form. | |
5dade857 MV |
286 | |
287 | This hook is used by some routines in ice-9/boot-9.scm to implement | |
288 | type specific printing routines. Please read the comments there about | |
289 | "printing structs". | |
290 | ||
291 | One of the more specific uses of structs are records. The printing | |
292 | procedure that could be passed to MAKE-RECORD-TYPE is now actually | |
293 | called. It should behave like a *struct-printer* procedure (described | |
294 | above). | |
295 | ||
b83b8bee JB |
296 | ** Guile now supports a new R4RS-compliant syntax for keywords. A |
297 | token of the form #:NAME, where NAME has the same syntax as a Scheme | |
298 | symbol, is the external representation of the keyword named NAME. | |
299 | Keyword objects print using this syntax as well, so values containing | |
1e5afba0 JB |
300 | keyword objects can be read back into Guile. When used in an |
301 | expression, keywords are self-quoting objects. | |
b83b8bee JB |
302 | |
303 | Guile suports this read syntax, and uses this print syntax, regardless | |
304 | of the current setting of the `keyword' read option. The `keyword' | |
305 | read option only controls whether Guile recognizes the `:NAME' syntax, | |
306 | which is incompatible with R4RS. (R4RS says such token represent | |
307 | symbols.) | |
737c9113 JB |
308 | |
309 | ** Guile has regular expression support again. Guile 1.0 included | |
310 | functions for matching regular expressions, based on the Rx library. | |
311 | In Guile 1.1, the Guile/Rx interface was removed to simplify the | |
312 | distribution, and thus Guile had no regular expression support. Guile | |
94982a4e JB |
313 | 1.2 again supports the most commonly used functions, and supports all |
314 | of SCSH's regular expression functions. | |
2409cdfa | 315 | |
94982a4e JB |
316 | If your system does not include a POSIX regular expression library, |
317 | and you have not linked Guile with a third-party regexp library such as | |
318 | Rx, these functions will not be available. You can tell whether your | |
319 | Guile installation includes regular expression support by checking | |
320 | whether the `*features*' list includes the `regex' symbol. | |
737c9113 | 321 | |
94982a4e | 322 | *** regexp functions |
161029df | 323 | |
94982a4e JB |
324 | By default, Guile supports POSIX extended regular expressions. That |
325 | means that the characters `(', `)', `+' and `?' are special, and must | |
326 | be escaped if you wish to match the literal characters. | |
e1a191a8 | 327 | |
94982a4e JB |
328 | This regular expression interface was modeled after that implemented |
329 | by SCSH, the Scheme Shell. It is intended to be upwardly compatible | |
330 | with SCSH regular expressions. | |
331 | ||
332 | **** Function: string-match PATTERN STR [START] | |
333 | Compile the string PATTERN into a regular expression and compare | |
334 | it with STR. The optional numeric argument START specifies the | |
335 | position of STR at which to begin matching. | |
336 | ||
337 | `string-match' returns a "match structure" which describes what, | |
338 | if anything, was matched by the regular expression. *Note Match | |
339 | Structures::. If STR does not match PATTERN at all, | |
340 | `string-match' returns `#f'. | |
341 | ||
342 | Each time `string-match' is called, it must compile its PATTERN | |
343 | argument into a regular expression structure. This operation is | |
344 | expensive, which makes `string-match' inefficient if the same regular | |
345 | expression is used several times (for example, in a loop). For better | |
346 | performance, you can compile a regular expression in advance and then | |
347 | match strings against the compiled regexp. | |
348 | ||
349 | **** Function: make-regexp STR [FLAGS] | |
350 | Compile the regular expression described by STR, and return the | |
351 | compiled regexp structure. If STR does not describe a legal | |
352 | regular expression, `make-regexp' throws a | |
353 | `regular-expression-syntax' error. | |
354 | ||
355 | FLAGS may be the bitwise-or of one or more of the following: | |
356 | ||
357 | **** Constant: regexp/extended | |
358 | Use POSIX Extended Regular Expression syntax when interpreting | |
359 | STR. If not set, POSIX Basic Regular Expression syntax is used. | |
360 | If the FLAGS argument is omitted, we assume regexp/extended. | |
361 | ||
362 | **** Constant: regexp/icase | |
363 | Do not differentiate case. Subsequent searches using the | |
364 | returned regular expression will be case insensitive. | |
365 | ||
366 | **** Constant: regexp/newline | |
367 | Match-any-character operators don't match a newline. | |
368 | ||
369 | A non-matching list ([^...]) not containing a newline matches a | |
370 | newline. | |
371 | ||
372 | Match-beginning-of-line operator (^) matches the empty string | |
373 | immediately after a newline, regardless of whether the FLAGS | |
374 | passed to regexp-exec contain regexp/notbol. | |
375 | ||
376 | Match-end-of-line operator ($) matches the empty string | |
377 | immediately before a newline, regardless of whether the FLAGS | |
378 | passed to regexp-exec contain regexp/noteol. | |
379 | ||
380 | **** Function: regexp-exec REGEXP STR [START [FLAGS]] | |
381 | Match the compiled regular expression REGEXP against `str'. If | |
382 | the optional integer START argument is provided, begin matching | |
383 | from that position in the string. Return a match structure | |
384 | describing the results of the match, or `#f' if no match could be | |
385 | found. | |
386 | ||
387 | FLAGS may be the bitwise-or of one or more of the following: | |
388 | ||
389 | **** Constant: regexp/notbol | |
390 | The match-beginning-of-line operator always fails to match (but | |
391 | see the compilation flag regexp/newline above) This flag may be | |
392 | used when different portions of a string are passed to | |
393 | regexp-exec and the beginning of the string should not be | |
394 | interpreted as the beginning of the line. | |
395 | ||
396 | **** Constant: regexp/noteol | |
397 | The match-end-of-line operator always fails to match (but see the | |
398 | compilation flag regexp/newline above) | |
399 | ||
400 | **** Function: regexp? OBJ | |
401 | Return `#t' if OBJ is a compiled regular expression, or `#f' | |
402 | otherwise. | |
403 | ||
404 | Regular expressions are commonly used to find patterns in one string | |
405 | and replace them with the contents of another string. | |
406 | ||
407 | **** Function: regexp-substitute PORT MATCH [ITEM...] | |
408 | Write to the output port PORT selected contents of the match | |
409 | structure MATCH. Each ITEM specifies what should be written, and | |
410 | may be one of the following arguments: | |
411 | ||
412 | * A string. String arguments are written out verbatim. | |
413 | ||
414 | * An integer. The submatch with that number is written. | |
415 | ||
416 | * The symbol `pre'. The portion of the matched string preceding | |
417 | the regexp match is written. | |
418 | ||
419 | * The symbol `post'. The portion of the matched string | |
420 | following the regexp match is written. | |
421 | ||
422 | PORT may be `#f', in which case nothing is written; instead, | |
423 | `regexp-substitute' constructs a string from the specified ITEMs | |
424 | and returns that. | |
425 | ||
426 | **** Function: regexp-substitute/global PORT REGEXP TARGET [ITEM...] | |
427 | Similar to `regexp-substitute', but can be used to perform global | |
428 | substitutions on STR. Instead of taking a match structure as an | |
429 | argument, `regexp-substitute/global' takes two string arguments: a | |
430 | REGEXP string describing a regular expression, and a TARGET string | |
431 | which should be matched against this regular expression. | |
432 | ||
433 | Each ITEM behaves as in REGEXP-SUBSTITUTE, with the following | |
434 | exceptions: | |
435 | ||
436 | * A function may be supplied. When this function is called, it | |
437 | will be passed one argument: a match structure for a given | |
438 | regular expression match. It should return a string to be | |
439 | written out to PORT. | |
440 | ||
441 | * The `post' symbol causes `regexp-substitute/global' to recurse | |
442 | on the unmatched portion of STR. This *must* be supplied in | |
443 | order to perform global search-and-replace on STR; if it is | |
444 | not present among the ITEMs, then `regexp-substitute/global' | |
445 | will return after processing a single match. | |
446 | ||
447 | *** Match Structures | |
448 | ||
449 | A "match structure" is the object returned by `string-match' and | |
450 | `regexp-exec'. It describes which portion of a string, if any, matched | |
451 | the given regular expression. Match structures include: a reference to | |
452 | the string that was checked for matches; the starting and ending | |
453 | positions of the regexp match; and, if the regexp included any | |
454 | parenthesized subexpressions, the starting and ending positions of each | |
455 | submatch. | |
456 | ||
457 | In each of the regexp match functions described below, the `match' | |
458 | argument must be a match structure returned by a previous call to | |
459 | `string-match' or `regexp-exec'. Most of these functions return some | |
460 | information about the original target string that was matched against a | |
461 | regular expression; we will call that string TARGET for easy reference. | |
462 | ||
463 | **** Function: regexp-match? OBJ | |
464 | Return `#t' if OBJ is a match structure returned by a previous | |
465 | call to `regexp-exec', or `#f' otherwise. | |
466 | ||
467 | **** Function: match:substring MATCH [N] | |
468 | Return the portion of TARGET matched by subexpression number N. | |
469 | Submatch 0 (the default) represents the entire regexp match. If | |
470 | the regular expression as a whole matched, but the subexpression | |
471 | number N did not match, return `#f'. | |
472 | ||
473 | **** Function: match:start MATCH [N] | |
474 | Return the starting position of submatch number N. | |
475 | ||
476 | **** Function: match:end MATCH [N] | |
477 | Return the ending position of submatch number N. | |
478 | ||
479 | **** Function: match:prefix MATCH | |
480 | Return the unmatched portion of TARGET preceding the regexp match. | |
481 | ||
482 | **** Function: match:suffix MATCH | |
483 | Return the unmatched portion of TARGET following the regexp match. | |
484 | ||
485 | **** Function: match:count MATCH | |
486 | Return the number of parenthesized subexpressions from MATCH. | |
487 | Note that the entire regular expression match itself counts as a | |
488 | subexpression, and failed submatches are included in the count. | |
489 | ||
490 | **** Function: match:string MATCH | |
491 | Return the original TARGET string. | |
492 | ||
493 | *** Backslash Escapes | |
494 | ||
495 | Sometimes you will want a regexp to match characters like `*' or `$' | |
496 | exactly. For example, to check whether a particular string represents | |
497 | a menu entry from an Info node, it would be useful to match it against | |
498 | a regexp like `^* [^:]*::'. However, this won't work; because the | |
499 | asterisk is a metacharacter, it won't match the `*' at the beginning of | |
500 | the string. In this case, we want to make the first asterisk un-magic. | |
501 | ||
502 | You can do this by preceding the metacharacter with a backslash | |
503 | character `\'. (This is also called "quoting" the metacharacter, and | |
504 | is known as a "backslash escape".) When Guile sees a backslash in a | |
505 | regular expression, it considers the following glyph to be an ordinary | |
506 | character, no matter what special meaning it would ordinarily have. | |
507 | Therefore, we can make the above example work by changing the regexp to | |
508 | `^\* [^:]*::'. The `\*' sequence tells the regular expression engine | |
509 | to match only a single asterisk in the target string. | |
510 | ||
511 | Since the backslash is itself a metacharacter, you may force a | |
512 | regexp to match a backslash in the target string by preceding the | |
513 | backslash with itself. For example, to find variable references in a | |
514 | TeX program, you might want to find occurrences of the string `\let\' | |
515 | followed by any number of alphabetic characters. The regular expression | |
516 | `\\let\\[A-Za-z]*' would do this: the double backslashes in the regexp | |
517 | each match a single backslash in the target string. | |
518 | ||
519 | **** Function: regexp-quote STR | |
520 | Quote each special character found in STR with a backslash, and | |
521 | return the resulting string. | |
522 | ||
523 | *Very important:* Using backslash escapes in Guile source code (as | |
524 | in Emacs Lisp or C) can be tricky, because the backslash character has | |
525 | special meaning for the Guile reader. For example, if Guile encounters | |
526 | the character sequence `\n' in the middle of a string while processing | |
527 | Scheme code, it replaces those characters with a newline character. | |
528 | Similarly, the character sequence `\t' is replaced by a horizontal tab. | |
529 | Several of these "escape sequences" are processed by the Guile reader | |
530 | before your code is executed. Unrecognized escape sequences are | |
531 | ignored: if the characters `\*' appear in a string, they will be | |
532 | translated to the single character `*'. | |
533 | ||
534 | This translation is obviously undesirable for regular expressions, | |
535 | since we want to be able to include backslashes in a string in order to | |
536 | escape regexp metacharacters. Therefore, to make sure that a backslash | |
537 | is preserved in a string in your Guile program, you must use *two* | |
538 | consecutive backslashes: | |
539 | ||
540 | (define Info-menu-entry-pattern (make-regexp "^\\* [^:]*")) | |
541 | ||
542 | The string in this example is preprocessed by the Guile reader before | |
543 | any code is executed. The resulting argument to `make-regexp' is the | |
544 | string `^\* [^:]*', which is what we really want. | |
545 | ||
546 | This also means that in order to write a regular expression that | |
547 | matches a single backslash character, the regular expression string in | |
548 | the source code must include *four* backslashes. Each consecutive pair | |
549 | of backslashes gets translated by the Guile reader to a single | |
550 | backslash, and the resulting double-backslash is interpreted by the | |
551 | regexp engine as matching a single backslash character. Hence: | |
552 | ||
553 | (define tex-variable-pattern (make-regexp "\\\\let\\\\=[A-Za-z]*")) | |
554 | ||
555 | The reason for the unwieldiness of this syntax is historical. Both | |
556 | regular expression pattern matchers and Unix string processing systems | |
557 | have traditionally used backslashes with the special meanings described | |
558 | above. The POSIX regular expression specification and ANSI C standard | |
559 | both require these semantics. Attempting to abandon either convention | |
560 | would cause other kinds of compatibility problems, possibly more severe | |
561 | ones. Therefore, without extending the Scheme reader to support | |
562 | strings with different quoting conventions (an ungainly and confusing | |
563 | extension when implemented in other languages), we must adhere to this | |
564 | cumbersome escape syntax. | |
565 | ||
7ad3c1e7 GH |
566 | * Changes to the gh_ interface |
567 | ||
568 | * Changes to the scm_ interface | |
569 | ||
570 | * Changes to system call interfaces: | |
94982a4e | 571 | |
7ad3c1e7 | 572 | ** The value returned by `raise' is now unspecified. It throws an exception |
e1a191a8 GH |
573 | if an error occurs. |
574 | ||
94982a4e | 575 | *** A new procedure `sigaction' can be used to install signal handlers |
115b09a5 GH |
576 | |
577 | (sigaction signum [action] [flags]) | |
578 | ||
579 | signum is the signal number, which can be specified using the value | |
580 | of SIGINT etc. | |
581 | ||
582 | If action is omitted, sigaction returns a pair: the CAR is the current | |
583 | signal hander, which will be either an integer with the value SIG_DFL | |
584 | (default action) or SIG_IGN (ignore), or the Scheme procedure which | |
585 | handles the signal, or #f if a non-Scheme procedure handles the | |
586 | signal. The CDR contains the current sigaction flags for the handler. | |
587 | ||
588 | If action is provided, it is installed as the new handler for signum. | |
589 | action can be a Scheme procedure taking one argument, or the value of | |
590 | SIG_DFL (default action) or SIG_IGN (ignore), or #f to restore | |
591 | whatever signal handler was installed before sigaction was first used. | |
592 | Flags can optionally be specified for the new handler (SA_RESTART is | |
593 | always used if the system provides it, so need not be specified.) The | |
594 | return value is a pair with information about the old handler as | |
595 | described above. | |
596 | ||
597 | This interface does not provide access to the "signal blocking" | |
598 | facility. Maybe this is not needed, since the thread support may | |
599 | provide solutions to the problem of consistent access to data | |
600 | structures. | |
e1a191a8 | 601 | |
94982a4e | 602 | *** A new procedure `flush-all-ports' is equivalent to running |
89ea5b7c GH |
603 | `force-output' on every port open for output. |
604 | ||
94982a4e JB |
605 | ** Guile now provides information on how it was built, via the new |
606 | global variable, %guile-build-info. This variable records the values | |
607 | of the standard GNU makefile directory variables as an assocation | |
608 | list, mapping variable names (symbols) onto directory paths (strings). | |
609 | For example, to find out where the Guile link libraries were | |
610 | installed, you can say: | |
611 | ||
612 | guile -c "(display (assq-ref %guile-build-info 'libdir)) (newline)" | |
613 | ||
614 | ||
615 | * Changes to the scm_ interface | |
616 | ||
617 | ** The new function scm_handle_by_message_noexit is just like the | |
618 | existing scm_handle_by_message function, except that it doesn't call | |
619 | exit to terminate the process. Instead, it prints a message and just | |
620 | returns #f. This might be a more appropriate catch-all handler for | |
621 | new dynamic roots and threads. | |
622 | ||
cf78e9e8 | 623 | \f |
c484bf7f | 624 | Changes in Guile 1.1 (released Friday, May 16 1997): |
f3b1485f JB |
625 | |
626 | * Changes to the distribution. | |
627 | ||
628 | The Guile 1.0 distribution has been split up into several smaller | |
629 | pieces: | |
630 | guile-core --- the Guile interpreter itself. | |
631 | guile-tcltk --- the interface between the Guile interpreter and | |
632 | Tcl/Tk; Tcl is an interpreter for a stringy language, and Tk | |
633 | is a toolkit for building graphical user interfaces. | |
634 | guile-rgx-ctax --- the interface between Guile and the Rx regular | |
635 | expression matcher, and the translator for the Ctax | |
636 | programming language. These are packaged together because the | |
637 | Ctax translator uses Rx to parse Ctax source code. | |
638 | ||
095936d2 JB |
639 | This NEWS file describes the changes made to guile-core since the 1.0 |
640 | release. | |
641 | ||
48d224d7 JB |
642 | We no longer distribute the documentation, since it was either out of |
643 | date, or incomplete. As soon as we have current documentation, we | |
644 | will distribute it. | |
645 | ||
0fcab5ed JB |
646 | |
647 | ||
f3b1485f JB |
648 | * Changes to the stand-alone interpreter |
649 | ||
48d224d7 JB |
650 | ** guile now accepts command-line arguments compatible with SCSH, Olin |
651 | Shivers' Scheme Shell. | |
652 | ||
653 | In general, arguments are evaluated from left to right, but there are | |
654 | exceptions. The following switches stop argument processing, and | |
655 | stash all remaining command-line arguments as the value returned by | |
656 | the (command-line) function. | |
657 | -s SCRIPT load Scheme source code from FILE, and exit | |
658 | -c EXPR evalute Scheme expression EXPR, and exit | |
659 | -- stop scanning arguments; run interactively | |
660 | ||
661 | The switches below are processed as they are encountered. | |
662 | -l FILE load Scheme source code from FILE | |
663 | -e FUNCTION after reading script, apply FUNCTION to | |
664 | command line arguments | |
665 | -ds do -s script at this point | |
666 | --emacs enable Emacs protocol (experimental) | |
667 | -h, --help display this help and exit | |
668 | -v, --version display version information and exit | |
669 | \ read arguments from following script lines | |
670 | ||
671 | So, for example, here is a Guile script named `ekko' (thanks, Olin) | |
672 | which re-implements the traditional "echo" command: | |
673 | ||
674 | #!/usr/local/bin/guile -s | |
675 | !# | |
676 | (define (main args) | |
677 | (map (lambda (arg) (display arg) (display " ")) | |
678 | (cdr args)) | |
679 | (newline)) | |
680 | ||
681 | (main (command-line)) | |
682 | ||
683 | Suppose we invoke this script as follows: | |
684 | ||
685 | ekko a speckled gecko | |
686 | ||
687 | Through the magic of Unix script processing (triggered by the `#!' | |
688 | token at the top of the file), /usr/local/bin/guile receives the | |
689 | following list of command-line arguments: | |
690 | ||
691 | ("-s" "./ekko" "a" "speckled" "gecko") | |
692 | ||
693 | Unix inserts the name of the script after the argument specified on | |
694 | the first line of the file (in this case, "-s"), and then follows that | |
695 | with the arguments given to the script. Guile loads the script, which | |
696 | defines the `main' function, and then applies it to the list of | |
697 | remaining command-line arguments, ("a" "speckled" "gecko"). | |
698 | ||
095936d2 JB |
699 | In Unix, the first line of a script file must take the following form: |
700 | ||
701 | #!INTERPRETER ARGUMENT | |
702 | ||
703 | where INTERPRETER is the absolute filename of the interpreter | |
704 | executable, and ARGUMENT is a single command-line argument to pass to | |
705 | the interpreter. | |
706 | ||
707 | You may only pass one argument to the interpreter, and its length is | |
708 | limited. These restrictions can be annoying to work around, so Guile | |
709 | provides a general mechanism (borrowed from, and compatible with, | |
710 | SCSH) for circumventing them. | |
711 | ||
712 | If the ARGUMENT in a Guile script is a single backslash character, | |
713 | `\', Guile will open the script file, parse arguments from its second | |
714 | and subsequent lines, and replace the `\' with them. So, for example, | |
715 | here is another implementation of the `ekko' script: | |
716 | ||
717 | #!/usr/local/bin/guile \ | |
718 | -e main -s | |
719 | !# | |
720 | (define (main args) | |
721 | (for-each (lambda (arg) (display arg) (display " ")) | |
722 | (cdr args)) | |
723 | (newline)) | |
724 | ||
725 | If the user invokes this script as follows: | |
726 | ||
727 | ekko a speckled gecko | |
728 | ||
729 | Unix expands this into | |
730 | ||
731 | /usr/local/bin/guile \ ekko a speckled gecko | |
732 | ||
733 | When Guile sees the `\' argument, it replaces it with the arguments | |
734 | read from the second line of the script, producing: | |
735 | ||
736 | /usr/local/bin/guile -e main -s ekko a speckled gecko | |
737 | ||
738 | This tells Guile to load the `ekko' script, and apply the function | |
739 | `main' to the argument list ("a" "speckled" "gecko"). | |
740 | ||
741 | Here is how Guile parses the command-line arguments: | |
742 | - Each space character terminates an argument. This means that two | |
743 | spaces in a row introduce an empty-string argument. | |
744 | - The tab character is not permitted (unless you quote it with the | |
745 | backslash character, as described below), to avoid confusion. | |
746 | - The newline character terminates the sequence of arguments, and will | |
747 | also terminate a final non-empty argument. (However, a newline | |
748 | following a space will not introduce a final empty-string argument; | |
749 | it only terminates the argument list.) | |
750 | - The backslash character is the escape character. It escapes | |
751 | backslash, space, tab, and newline. The ANSI C escape sequences | |
752 | like \n and \t are also supported. These produce argument | |
753 | constituents; the two-character combination \n doesn't act like a | |
754 | terminating newline. The escape sequence \NNN for exactly three | |
755 | octal digits reads as the character whose ASCII code is NNN. As | |
756 | above, characters produced this way are argument constituents. | |
757 | Backslash followed by other characters is not allowed. | |
758 | ||
48d224d7 JB |
759 | * Changes to the procedure for linking libguile with your programs |
760 | ||
761 | ** Guile now builds and installs a shared guile library, if your | |
762 | system support shared libraries. (It still builds a static library on | |
763 | all systems.) Guile automatically detects whether your system | |
764 | supports shared libraries. To prevent Guile from buildisg shared | |
765 | libraries, pass the `--disable-shared' flag to the configure script. | |
766 | ||
767 | Guile takes longer to compile when it builds shared libraries, because | |
768 | it must compile every file twice --- once to produce position- | |
769 | independent object code, and once to produce normal object code. | |
770 | ||
771 | ** The libthreads library has been merged into libguile. | |
772 | ||
773 | To link a program against Guile, you now need only link against | |
774 | -lguile and -lqt; -lthreads is no longer needed. If you are using | |
775 | autoconf to generate configuration scripts for your application, the | |
776 | following lines should suffice to add the appropriate libraries to | |
777 | your link command: | |
778 | ||
779 | ### Find quickthreads and libguile. | |
780 | AC_CHECK_LIB(qt, main) | |
781 | AC_CHECK_LIB(guile, scm_shell) | |
f3b1485f JB |
782 | |
783 | * Changes to Scheme functions | |
784 | ||
095936d2 JB |
785 | ** Guile Scheme's special syntax for keyword objects is now optional, |
786 | and disabled by default. | |
787 | ||
788 | The syntax variation from R4RS made it difficult to port some | |
789 | interesting packages to Guile. The routines which accepted keyword | |
790 | arguments (mostly in the module system) have been modified to also | |
791 | accept symbols whose names begin with `:'. | |
792 | ||
793 | To change the keyword syntax, you must first import the (ice-9 debug) | |
794 | module: | |
795 | (use-modules (ice-9 debug)) | |
796 | ||
797 | Then you can enable the keyword syntax as follows: | |
798 | (read-set! keywords 'prefix) | |
799 | ||
800 | To disable keyword syntax, do this: | |
801 | (read-set! keywords #f) | |
802 | ||
803 | ** Many more primitive functions accept shared substrings as | |
804 | arguments. In the past, these functions required normal, mutable | |
805 | strings as arguments, although they never made use of this | |
806 | restriction. | |
807 | ||
808 | ** The uniform array functions now operate on byte vectors. These | |
809 | functions are `array-fill!', `serial-array-copy!', `array-copy!', | |
810 | `serial-array-map', `array-map', `array-for-each', and | |
811 | `array-index-map!'. | |
812 | ||
813 | ** The new functions `trace' and `untrace' implement simple debugging | |
814 | support for Scheme functions. | |
815 | ||
816 | The `trace' function accepts any number of procedures as arguments, | |
817 | and tells the Guile interpreter to display each procedure's name and | |
818 | arguments each time the procedure is invoked. When invoked with no | |
819 | arguments, `trace' returns the list of procedures currently being | |
820 | traced. | |
821 | ||
822 | The `untrace' function accepts any number of procedures as arguments, | |
823 | and tells the Guile interpreter not to trace them any more. When | |
824 | invoked with no arguments, `untrace' untraces all curretly traced | |
825 | procedures. | |
826 | ||
827 | The tracing in Guile has an advantage over most other systems: we | |
828 | don't create new procedure objects, but mark the procedure objects | |
829 | themselves. This means that anonymous and internal procedures can be | |
830 | traced. | |
831 | ||
832 | ** The function `assert-repl-prompt' has been renamed to | |
833 | `set-repl-prompt!'. It takes one argument, PROMPT. | |
834 | - If PROMPT is #f, the Guile read-eval-print loop will not prompt. | |
835 | - If PROMPT is a string, we use it as a prompt. | |
836 | - If PROMPT is a procedure accepting no arguments, we call it, and | |
837 | display the result as a prompt. | |
838 | - Otherwise, we display "> ". | |
839 | ||
840 | ** The new function `eval-string' reads Scheme expressions from a | |
841 | string and evaluates them, returning the value of the last expression | |
842 | in the string. If the string contains no expressions, it returns an | |
843 | unspecified value. | |
844 | ||
845 | ** The new function `thunk?' returns true iff its argument is a | |
846 | procedure of zero arguments. | |
847 | ||
848 | ** `defined?' is now a builtin function, instead of syntax. This | |
849 | means that its argument should be quoted. It returns #t iff its | |
850 | argument is bound in the current module. | |
851 | ||
852 | ** The new syntax `use-modules' allows you to add new modules to your | |
853 | environment without re-typing a complete `define-module' form. It | |
854 | accepts any number of module names as arguments, and imports their | |
855 | public bindings into the current module. | |
856 | ||
857 | ** The new function (module-defined? NAME MODULE) returns true iff | |
858 | NAME, a symbol, is defined in MODULE, a module object. | |
859 | ||
860 | ** The new function `builtin-bindings' creates and returns a hash | |
861 | table containing copies of all the root module's bindings. | |
862 | ||
863 | ** The new function `builtin-weak-bindings' does the same as | |
864 | `builtin-bindings', but creates a doubly-weak hash table. | |
865 | ||
866 | ** The `equal?' function now considers variable objects to be | |
867 | equivalent if they have the same name and the same value. | |
868 | ||
869 | ** The new function `command-line' returns the command-line arguments | |
870 | given to Guile, as a list of strings. | |
871 | ||
872 | When using guile as a script interpreter, `command-line' returns the | |
873 | script's arguments; those processed by the interpreter (like `-s' or | |
874 | `-c') are omitted. (In other words, you get the normal, expected | |
875 | behavior.) Any application that uses scm_shell to process its | |
876 | command-line arguments gets this behavior as well. | |
877 | ||
878 | ** The new function `load-user-init' looks for a file called `.guile' | |
879 | in the user's home directory, and loads it if it exists. This is | |
880 | mostly for use by the code generated by scm_compile_shell_switches, | |
881 | but we thought it might also be useful in other circumstances. | |
882 | ||
883 | ** The new function `log10' returns the base-10 logarithm of its | |
884 | argument. | |
885 | ||
886 | ** Changes to I/O functions | |
887 | ||
888 | *** The functions `read', `primitive-load', `read-and-eval!', and | |
889 | `primitive-load-path' no longer take optional arguments controlling | |
890 | case insensitivity and a `#' parser. | |
891 | ||
892 | Case sensitivity is now controlled by a read option called | |
893 | `case-insensitive'. The user can add new `#' syntaxes with the | |
894 | `read-hash-extend' function (see below). | |
895 | ||
896 | *** The new function `read-hash-extend' allows the user to change the | |
897 | syntax of Guile Scheme in a somewhat controlled way. | |
898 | ||
899 | (read-hash-extend CHAR PROC) | |
900 | When parsing S-expressions, if we read a `#' character followed by | |
901 | the character CHAR, use PROC to parse an object from the stream. | |
902 | If PROC is #f, remove any parsing procedure registered for CHAR. | |
903 | ||
904 | The reader applies PROC to two arguments: CHAR and an input port. | |
905 | ||
906 | *** The new functions read-delimited and read-delimited! provide a | |
907 | general mechanism for doing delimited input on streams. | |
908 | ||
909 | (read-delimited DELIMS [PORT HANDLE-DELIM]) | |
910 | Read until we encounter one of the characters in DELIMS (a string), | |
911 | or end-of-file. PORT is the input port to read from; it defaults to | |
912 | the current input port. The HANDLE-DELIM parameter determines how | |
913 | the terminating character is handled; it should be one of the | |
914 | following symbols: | |
915 | ||
916 | 'trim omit delimiter from result | |
917 | 'peek leave delimiter character in input stream | |
918 | 'concat append delimiter character to returned value | |
919 | 'split return a pair: (RESULT . TERMINATOR) | |
920 | ||
921 | HANDLE-DELIM defaults to 'peek. | |
922 | ||
923 | (read-delimited! DELIMS BUF [PORT HANDLE-DELIM START END]) | |
924 | A side-effecting variant of `read-delimited'. | |
925 | ||
926 | The data is written into the string BUF at the indices in the | |
927 | half-open interval [START, END); the default interval is the whole | |
928 | string: START = 0 and END = (string-length BUF). The values of | |
929 | START and END must specify a well-defined interval in BUF, i.e. | |
930 | 0 <= START <= END <= (string-length BUF). | |
931 | ||
932 | It returns NBYTES, the number of bytes read. If the buffer filled | |
933 | up without a delimiter character being found, it returns #f. If the | |
934 | port is at EOF when the read starts, it returns the EOF object. | |
935 | ||
936 | If an integer is returned (i.e., the read is successfully terminated | |
937 | by reading a delimiter character), then the HANDLE-DELIM parameter | |
938 | determines how to handle the terminating character. It is described | |
939 | above, and defaults to 'peek. | |
940 | ||
941 | (The descriptions of these functions were borrowed from the SCSH | |
942 | manual, by Olin Shivers and Brian Carlstrom.) | |
943 | ||
944 | *** The `%read-delimited!' function is the primitive used to implement | |
945 | `read-delimited' and `read-delimited!'. | |
946 | ||
947 | (%read-delimited! DELIMS BUF GOBBLE? [PORT START END]) | |
948 | ||
949 | This returns a pair of values: (TERMINATOR . NUM-READ). | |
950 | - TERMINATOR describes why the read was terminated. If it is a | |
951 | character or the eof object, then that is the value that terminated | |
952 | the read. If it is #f, the function filled the buffer without finding | |
953 | a delimiting character. | |
954 | - NUM-READ is the number of characters read into BUF. | |
955 | ||
956 | If the read is successfully terminated by reading a delimiter | |
957 | character, then the gobble? parameter determines what to do with the | |
958 | terminating character. If true, the character is removed from the | |
959 | input stream; if false, the character is left in the input stream | |
960 | where a subsequent read operation will retrieve it. In either case, | |
961 | the character is also the first value returned by the procedure call. | |
962 | ||
963 | (The descriptions of this function was borrowed from the SCSH manual, | |
964 | by Olin Shivers and Brian Carlstrom.) | |
965 | ||
966 | *** The `read-line' and `read-line!' functions have changed; they now | |
967 | trim the terminator by default; previously they appended it to the | |
968 | returned string. For the old behavior, use (read-line PORT 'concat). | |
969 | ||
970 | *** The functions `uniform-array-read!' and `uniform-array-write!' now | |
971 | take new optional START and END arguments, specifying the region of | |
972 | the array to read and write. | |
973 | ||
f348c807 JB |
974 | *** The `ungetc-char-ready?' function has been removed. We feel it's |
975 | inappropriate for an interface to expose implementation details this | |
976 | way. | |
095936d2 JB |
977 | |
978 | ** Changes to the Unix library and system call interface | |
979 | ||
980 | *** The new fcntl function provides access to the Unix `fcntl' system | |
981 | call. | |
982 | ||
983 | (fcntl PORT COMMAND VALUE) | |
984 | Apply COMMAND to PORT's file descriptor, with VALUE as an argument. | |
985 | Values for COMMAND are: | |
986 | ||
987 | F_DUPFD duplicate a file descriptor | |
988 | F_GETFD read the descriptor's close-on-exec flag | |
989 | F_SETFD set the descriptor's close-on-exec flag to VALUE | |
990 | F_GETFL read the descriptor's flags, as set on open | |
991 | F_SETFL set the descriptor's flags, as set on open to VALUE | |
992 | F_GETOWN return the process ID of a socket's owner, for SIGIO | |
993 | F_SETOWN set the process that owns a socket to VALUE, for SIGIO | |
994 | FD_CLOEXEC not sure what this is | |
995 | ||
996 | For details, see the documentation for the fcntl system call. | |
997 | ||
998 | *** The arguments to `select' have changed, for compatibility with | |
999 | SCSH. The TIMEOUT parameter may now be non-integral, yielding the | |
1000 | expected behavior. The MILLISECONDS parameter has been changed to | |
1001 | MICROSECONDS, to more closely resemble the underlying system call. | |
1002 | The RVEC, WVEC, and EVEC arguments can now be vectors; the type of the | |
1003 | corresponding return set will be the same. | |
1004 | ||
1005 | *** The arguments to the `mknod' system call have changed. They are | |
1006 | now: | |
1007 | ||
1008 | (mknod PATH TYPE PERMS DEV) | |
1009 | Create a new file (`node') in the file system. PATH is the name of | |
1010 | the file to create. TYPE is the kind of file to create; it should | |
1011 | be 'fifo, 'block-special, or 'char-special. PERMS specifies the | |
1012 | permission bits to give the newly created file. If TYPE is | |
1013 | 'block-special or 'char-special, DEV specifies which device the | |
1014 | special file refers to; its interpretation depends on the kind of | |
1015 | special file being created. | |
1016 | ||
1017 | *** The `fork' function has been renamed to `primitive-fork', to avoid | |
1018 | clashing with various SCSH forks. | |
1019 | ||
1020 | *** The `recv' and `recvfrom' functions have been renamed to `recv!' | |
1021 | and `recvfrom!'. They no longer accept a size for a second argument; | |
1022 | you must pass a string to hold the received value. They no longer | |
1023 | return the buffer. Instead, `recv' returns the length of the message | |
1024 | received, and `recvfrom' returns a pair containing the packet's length | |
1025 | and originating address. | |
1026 | ||
1027 | *** The file descriptor datatype has been removed, as have the | |
1028 | `read-fd', `write-fd', `close', `lseek', and `dup' functions. | |
1029 | We plan to replace these functions with a SCSH-compatible interface. | |
1030 | ||
1031 | *** The `create' function has been removed; it's just a special case | |
1032 | of `open'. | |
1033 | ||
1034 | *** There are new functions to break down process termination status | |
1035 | values. In the descriptions below, STATUS is a value returned by | |
1036 | `waitpid'. | |
1037 | ||
1038 | (status:exit-val STATUS) | |
1039 | If the child process exited normally, this function returns the exit | |
1040 | code for the child process (i.e., the value passed to exit, or | |
1041 | returned from main). If the child process did not exit normally, | |
1042 | this function returns #f. | |
1043 | ||
1044 | (status:stop-sig STATUS) | |
1045 | If the child process was suspended by a signal, this function | |
1046 | returns the signal that suspended the child. Otherwise, it returns | |
1047 | #f. | |
1048 | ||
1049 | (status:term-sig STATUS) | |
1050 | If the child process terminated abnormally, this function returns | |
1051 | the signal that terminated the child. Otherwise, this function | |
1052 | returns false. | |
1053 | ||
1054 | POSIX promises that exactly one of these functions will return true on | |
1055 | a valid STATUS value. | |
1056 | ||
1057 | These functions are compatible with SCSH. | |
1058 | ||
1059 | *** There are new accessors and setters for the broken-out time vectors | |
48d224d7 JB |
1060 | returned by `localtime', `gmtime', and that ilk. They are: |
1061 | ||
1062 | Component Accessor Setter | |
1063 | ========================= ============ ============ | |
1064 | seconds tm:sec set-tm:sec | |
1065 | minutes tm:min set-tm:min | |
1066 | hours tm:hour set-tm:hour | |
1067 | day of the month tm:mday set-tm:mday | |
1068 | month tm:mon set-tm:mon | |
1069 | year tm:year set-tm:year | |
1070 | day of the week tm:wday set-tm:wday | |
1071 | day in the year tm:yday set-tm:yday | |
1072 | daylight saving time tm:isdst set-tm:isdst | |
1073 | GMT offset, seconds tm:gmtoff set-tm:gmtoff | |
1074 | name of time zone tm:zone set-tm:zone | |
1075 | ||
095936d2 JB |
1076 | *** There are new accessors for the vectors returned by `uname', |
1077 | describing the host system: | |
48d224d7 JB |
1078 | |
1079 | Component Accessor | |
1080 | ============================================== ================ | |
1081 | name of the operating system implementation utsname:sysname | |
1082 | network name of this machine utsname:nodename | |
1083 | release level of the operating system utsname:release | |
1084 | version level of the operating system utsname:version | |
1085 | machine hardware platform utsname:machine | |
1086 | ||
095936d2 JB |
1087 | *** There are new accessors for the vectors returned by `getpw', |
1088 | `getpwnam', `getpwuid', and `getpwent', describing entries from the | |
1089 | system's user database: | |
1090 | ||
1091 | Component Accessor | |
1092 | ====================== ================= | |
1093 | user name passwd:name | |
1094 | user password passwd:passwd | |
1095 | user id passwd:uid | |
1096 | group id passwd:gid | |
1097 | real name passwd:gecos | |
1098 | home directory passwd:dir | |
1099 | shell program passwd:shell | |
1100 | ||
1101 | *** There are new accessors for the vectors returned by `getgr', | |
1102 | `getgrnam', `getgrgid', and `getgrent', describing entries from the | |
1103 | system's group database: | |
1104 | ||
1105 | Component Accessor | |
1106 | ======================= ============ | |
1107 | group name group:name | |
1108 | group password group:passwd | |
1109 | group id group:gid | |
1110 | group members group:mem | |
1111 | ||
1112 | *** There are new accessors for the vectors returned by `gethost', | |
1113 | `gethostbyaddr', `gethostbyname', and `gethostent', describing | |
1114 | internet hosts: | |
1115 | ||
1116 | Component Accessor | |
1117 | ========================= =============== | |
1118 | official name of host hostent:name | |
1119 | alias list hostent:aliases | |
1120 | host address type hostent:addrtype | |
1121 | length of address hostent:length | |
1122 | list of addresses hostent:addr-list | |
1123 | ||
1124 | *** There are new accessors for the vectors returned by `getnet', | |
1125 | `getnetbyaddr', `getnetbyname', and `getnetent', describing internet | |
1126 | networks: | |
1127 | ||
1128 | Component Accessor | |
1129 | ========================= =============== | |
1130 | official name of net netent:name | |
1131 | alias list netent:aliases | |
1132 | net number type netent:addrtype | |
1133 | net number netent:net | |
1134 | ||
1135 | *** There are new accessors for the vectors returned by `getproto', | |
1136 | `getprotobyname', `getprotobynumber', and `getprotoent', describing | |
1137 | internet protocols: | |
1138 | ||
1139 | Component Accessor | |
1140 | ========================= =============== | |
1141 | official protocol name protoent:name | |
1142 | alias list protoent:aliases | |
1143 | protocol number protoent:proto | |
1144 | ||
1145 | *** There are new accessors for the vectors returned by `getserv', | |
1146 | `getservbyname', `getservbyport', and `getservent', describing | |
1147 | internet protocols: | |
1148 | ||
1149 | Component Accessor | |
1150 | ========================= =============== | |
1151 | official service name servent:name | |
1152 | alias list servent:aliases | |
1153 | port number servent:port | |
1154 | protocol to use servent:proto | |
1155 | ||
1156 | *** There are new accessors for the sockaddr structures returned by | |
1157 | `accept', `getsockname', `getpeername', `recvfrom!': | |
1158 | ||
1159 | Component Accessor | |
1160 | ======================================== =============== | |
1161 | address format (`family') sockaddr:fam | |
1162 | path, for file domain addresses sockaddr:path | |
1163 | address, for internet domain addresses sockaddr:addr | |
1164 | TCP or UDP port, for internet sockaddr:port | |
1165 | ||
1166 | *** The `getpwent', `getgrent', `gethostent', `getnetent', | |
1167 | `getprotoent', and `getservent' functions now return #f at the end of | |
1168 | the user database. (They used to throw an exception.) | |
1169 | ||
1170 | Note that calling MUMBLEent function is equivalent to calling the | |
1171 | corresponding MUMBLE function with no arguments. | |
1172 | ||
1173 | *** The `setpwent', `setgrent', `sethostent', `setnetent', | |
1174 | `setprotoent', and `setservent' routines now take no arguments. | |
1175 | ||
1176 | *** The `gethost', `getproto', `getnet', and `getserv' functions now | |
1177 | provide more useful information when they throw an exception. | |
1178 | ||
1179 | *** The `lnaof' function has been renamed to `inet-lnaof'. | |
1180 | ||
1181 | *** Guile now claims to have the `current-time' feature. | |
1182 | ||
1183 | *** The `mktime' function now takes an optional second argument ZONE, | |
1184 | giving the time zone to use for the conversion. ZONE should be a | |
1185 | string, in the same format as expected for the "TZ" environment variable. | |
1186 | ||
1187 | *** The `strptime' function now returns a pair (TIME . COUNT), where | |
1188 | TIME is the parsed time as a vector, and COUNT is the number of | |
1189 | characters from the string left unparsed. This function used to | |
1190 | return the remaining characters as a string. | |
1191 | ||
1192 | *** The `gettimeofday' function has replaced the old `time+ticks' function. | |
1193 | The return value is now (SECONDS . MICROSECONDS); the fractional | |
1194 | component is no longer expressed in "ticks". | |
1195 | ||
1196 | *** The `ticks/sec' constant has been removed, in light of the above change. | |
6685dc83 | 1197 | |
ea00ecba MG |
1198 | * Changes to the gh_ interface |
1199 | ||
1200 | ** gh_eval_str() now returns an SCM object which is the result of the | |
1201 | evaluation | |
1202 | ||
aaef0d2a MG |
1203 | ** gh_scm2str() now copies the Scheme data to a caller-provided C |
1204 | array | |
1205 | ||
1206 | ** gh_scm2newstr() now makes a C array, copies the Scheme data to it, | |
1207 | and returns the array | |
1208 | ||
1209 | ** gh_scm2str0() is gone: there is no need to distinguish | |
1210 | null-terminated from non-null-terminated, since gh_scm2newstr() allows | |
1211 | the user to interpret the data both ways. | |
1212 | ||
f3b1485f JB |
1213 | * Changes to the scm_ interface |
1214 | ||
095936d2 JB |
1215 | ** The new function scm_symbol_value0 provides an easy way to get a |
1216 | symbol's value from C code: | |
1217 | ||
1218 | SCM scm_symbol_value0 (char *NAME) | |
1219 | Return the value of the symbol named by the null-terminated string | |
1220 | NAME in the current module. If the symbol named NAME is unbound in | |
1221 | the current module, return SCM_UNDEFINED. | |
1222 | ||
1223 | ** The new function scm_sysintern0 creates new top-level variables, | |
1224 | without assigning them a value. | |
1225 | ||
1226 | SCM scm_sysintern0 (char *NAME) | |
1227 | Create a new Scheme top-level variable named NAME. NAME is a | |
1228 | null-terminated string. Return the variable's value cell. | |
1229 | ||
1230 | ** The function scm_internal_catch is the guts of catch. It handles | |
1231 | all the mechanics of setting up a catch target, invoking the catch | |
1232 | body, and perhaps invoking the handler if the body does a throw. | |
1233 | ||
1234 | The function is designed to be usable from C code, but is general | |
1235 | enough to implement all the semantics Guile Scheme expects from throw. | |
1236 | ||
1237 | TAG is the catch tag. Typically, this is a symbol, but this function | |
1238 | doesn't actually care about that. | |
1239 | ||
1240 | BODY is a pointer to a C function which runs the body of the catch; | |
1241 | this is the code you can throw from. We call it like this: | |
1242 | BODY (BODY_DATA, JMPBUF) | |
1243 | where: | |
1244 | BODY_DATA is just the BODY_DATA argument we received; we pass it | |
1245 | through to BODY as its first argument. The caller can make | |
1246 | BODY_DATA point to anything useful that BODY might need. | |
1247 | JMPBUF is the Scheme jmpbuf object corresponding to this catch, | |
1248 | which we have just created and initialized. | |
1249 | ||
1250 | HANDLER is a pointer to a C function to deal with a throw to TAG, | |
1251 | should one occur. We call it like this: | |
1252 | HANDLER (HANDLER_DATA, THROWN_TAG, THROW_ARGS) | |
1253 | where | |
1254 | HANDLER_DATA is the HANDLER_DATA argument we recevied; it's the | |
1255 | same idea as BODY_DATA above. | |
1256 | THROWN_TAG is the tag that the user threw to; usually this is | |
1257 | TAG, but it could be something else if TAG was #t (i.e., a | |
1258 | catch-all), or the user threw to a jmpbuf. | |
1259 | THROW_ARGS is the list of arguments the user passed to the THROW | |
1260 | function. | |
1261 | ||
1262 | BODY_DATA is just a pointer we pass through to BODY. HANDLER_DATA | |
1263 | is just a pointer we pass through to HANDLER. We don't actually | |
1264 | use either of those pointers otherwise ourselves. The idea is | |
1265 | that, if our caller wants to communicate something to BODY or | |
1266 | HANDLER, it can pass a pointer to it as MUMBLE_DATA, which BODY and | |
1267 | HANDLER can then use. Think of it as a way to make BODY and | |
1268 | HANDLER closures, not just functions; MUMBLE_DATA points to the | |
1269 | enclosed variables. | |
1270 | ||
1271 | Of course, it's up to the caller to make sure that any data a | |
1272 | MUMBLE_DATA needs is protected from GC. A common way to do this is | |
1273 | to make MUMBLE_DATA a pointer to data stored in an automatic | |
1274 | structure variable; since the collector must scan the stack for | |
1275 | references anyway, this assures that any references in MUMBLE_DATA | |
1276 | will be found. | |
1277 | ||
1278 | ** The new function scm_internal_lazy_catch is exactly like | |
1279 | scm_internal_catch, except: | |
1280 | ||
1281 | - It does not unwind the stack (this is the major difference). | |
1282 | - If handler returns, its value is returned from the throw. | |
1283 | - BODY always receives #f as its JMPBUF argument (since there's no | |
1284 | jmpbuf associated with a lazy catch, because we don't unwind the | |
1285 | stack.) | |
1286 | ||
1287 | ** scm_body_thunk is a new body function you can pass to | |
1288 | scm_internal_catch if you want the body to be like Scheme's `catch' | |
1289 | --- a thunk, or a function of one argument if the tag is #f. | |
1290 | ||
1291 | BODY_DATA is a pointer to a scm_body_thunk_data structure, which | |
1292 | contains the Scheme procedure to invoke as the body, and the tag | |
1293 | we're catching. If the tag is #f, then we pass JMPBUF (created by | |
1294 | scm_internal_catch) to the body procedure; otherwise, the body gets | |
1295 | no arguments. | |
1296 | ||
1297 | ** scm_handle_by_proc is a new handler function you can pass to | |
1298 | scm_internal_catch if you want the handler to act like Scheme's catch | |
1299 | --- call a procedure with the tag and the throw arguments. | |
1300 | ||
1301 | If the user does a throw to this catch, this function runs a handler | |
1302 | procedure written in Scheme. HANDLER_DATA is a pointer to an SCM | |
1303 | variable holding the Scheme procedure object to invoke. It ought to | |
1304 | be a pointer to an automatic variable (i.e., one living on the stack), | |
1305 | or the procedure object should be otherwise protected from GC. | |
1306 | ||
1307 | ** scm_handle_by_message is a new handler function to use with | |
1308 | `scm_internal_catch' if you want Guile to print a message and die. | |
1309 | It's useful for dealing with throws to uncaught keys at the top level. | |
1310 | ||
1311 | HANDLER_DATA, if non-zero, is assumed to be a char * pointing to a | |
1312 | message header to print; if zero, we use "guile" instead. That | |
1313 | text is followed by a colon, then the message described by ARGS. | |
1314 | ||
1315 | ** The return type of scm_boot_guile is now void; the function does | |
1316 | not return a value, and indeed, never returns at all. | |
1317 | ||
f3b1485f JB |
1318 | ** The new function scm_shell makes it easy for user applications to |
1319 | process command-line arguments in a way that is compatible with the | |
1320 | stand-alone guile interpreter (which is in turn compatible with SCSH, | |
1321 | the Scheme shell). | |
1322 | ||
1323 | To use the scm_shell function, first initialize any guile modules | |
1324 | linked into your application, and then call scm_shell with the values | |
1325 | of ARGC and ARGV your `main' function received. scm_shell will adding | |
1326 | any SCSH-style meta-arguments from the top of the script file to the | |
1327 | argument vector, and then process the command-line arguments. This | |
1328 | generally means loading a script file or starting up an interactive | |
1329 | command interpreter. For details, see "Changes to the stand-alone | |
1330 | interpreter" above. | |
1331 | ||
095936d2 JB |
1332 | ** The new functions scm_get_meta_args and scm_count_argv help you |
1333 | implement the SCSH-style meta-argument, `\'. | |
1334 | ||
1335 | char **scm_get_meta_args (int ARGC, char **ARGV) | |
1336 | If the second element of ARGV is a string consisting of a single | |
1337 | backslash character (i.e. "\\" in Scheme notation), open the file | |
1338 | named by the following argument, parse arguments from it, and return | |
1339 | the spliced command line. The returned array is terminated by a | |
1340 | null pointer. | |
1341 | ||
1342 | For details of argument parsing, see above, under "guile now accepts | |
1343 | command-line arguments compatible with SCSH..." | |
1344 | ||
1345 | int scm_count_argv (char **ARGV) | |
1346 | Count the arguments in ARGV, assuming it is terminated by a null | |
1347 | pointer. | |
1348 | ||
1349 | For an example of how these functions might be used, see the source | |
1350 | code for the function scm_shell in libguile/script.c. | |
1351 | ||
1352 | You will usually want to use scm_shell instead of calling this | |
1353 | function yourself. | |
1354 | ||
1355 | ** The new function scm_compile_shell_switches turns an array of | |
1356 | command-line arguments into Scheme code to carry out the actions they | |
1357 | describe. Given ARGC and ARGV, it returns a Scheme expression to | |
1358 | evaluate, and calls scm_set_program_arguments to make any remaining | |
1359 | command-line arguments available to the Scheme code. For example, | |
1360 | given the following arguments: | |
1361 | ||
1362 | -e main -s ekko a speckled gecko | |
1363 | ||
1364 | scm_set_program_arguments will return the following expression: | |
1365 | ||
1366 | (begin (load "ekko") (main (command-line)) (quit)) | |
1367 | ||
1368 | You will usually want to use scm_shell instead of calling this | |
1369 | function yourself. | |
1370 | ||
1371 | ** The function scm_shell_usage prints a usage message appropriate for | |
1372 | an interpreter that uses scm_compile_shell_switches to handle its | |
1373 | command-line arguments. | |
1374 | ||
1375 | void scm_shell_usage (int FATAL, char *MESSAGE) | |
1376 | Print a usage message to the standard error output. If MESSAGE is | |
1377 | non-zero, write it before the usage message, followed by a newline. | |
1378 | If FATAL is non-zero, exit the process, using FATAL as the | |
1379 | termination status. (If you want to be compatible with Guile, | |
1380 | always use 1 as the exit status when terminating due to command-line | |
1381 | usage problems.) | |
1382 | ||
1383 | You will usually want to use scm_shell instead of calling this | |
1384 | function yourself. | |
48d224d7 JB |
1385 | |
1386 | ** scm_eval_0str now returns SCM_UNSPECIFIED if the string contains no | |
095936d2 JB |
1387 | expressions. It used to return SCM_EOL. Earth-shattering. |
1388 | ||
1389 | ** The macros for declaring scheme objects in C code have been | |
1390 | rearranged slightly. They are now: | |
1391 | ||
1392 | SCM_SYMBOL (C_NAME, SCHEME_NAME) | |
1393 | Declare a static SCM variable named C_NAME, and initialize it to | |
1394 | point to the Scheme symbol whose name is SCHEME_NAME. C_NAME should | |
1395 | be a C identifier, and SCHEME_NAME should be a C string. | |
1396 | ||
1397 | SCM_GLOBAL_SYMBOL (C_NAME, SCHEME_NAME) | |
1398 | Just like SCM_SYMBOL, but make C_NAME globally visible. | |
1399 | ||
1400 | SCM_VCELL (C_NAME, SCHEME_NAME) | |
1401 | Create a global variable at the Scheme level named SCHEME_NAME. | |
1402 | Declare a static SCM variable named C_NAME, and initialize it to | |
1403 | point to the Scheme variable's value cell. | |
1404 | ||
1405 | SCM_GLOBAL_VCELL (C_NAME, SCHEME_NAME) | |
1406 | Just like SCM_VCELL, but make C_NAME globally visible. | |
1407 | ||
1408 | The `guile-snarf' script writes initialization code for these macros | |
1409 | to its standard output, given C source code as input. | |
1410 | ||
1411 | The SCM_GLOBAL macro is gone. | |
1412 | ||
1413 | ** The scm_read_line and scm_read_line_x functions have been replaced | |
1414 | by Scheme code based on the %read-delimited! procedure (known to C | |
1415 | code as scm_read_delimited_x). See its description above for more | |
1416 | information. | |
48d224d7 | 1417 | |
095936d2 JB |
1418 | ** The function scm_sys_open has been renamed to scm_open. It now |
1419 | returns a port instead of an FD object. | |
ea00ecba | 1420 | |
095936d2 JB |
1421 | * The dynamic linking support has changed. For more information, see |
1422 | libguile/DYNAMIC-LINKING. | |
ea00ecba | 1423 | |
f7b47737 JB |
1424 | \f |
1425 | Guile 1.0b3 | |
3065a62a | 1426 | |
f3b1485f JB |
1427 | User-visible changes from Thursday, September 5, 1996 until Guile 1.0 |
1428 | (Sun 5 Jan 1997): | |
3065a62a | 1429 | |
4b521edb | 1430 | * Changes to the 'guile' program: |
3065a62a | 1431 | |
4b521edb JB |
1432 | ** Guile now loads some new files when it starts up. Guile first |
1433 | searches the load path for init.scm, and loads it if found. Then, if | |
1434 | Guile is not being used to execute a script, and the user's home | |
1435 | directory contains a file named `.guile', Guile loads that. | |
c6486f8a | 1436 | |
4b521edb | 1437 | ** You can now use Guile as a shell script interpreter. |
3065a62a JB |
1438 | |
1439 | To paraphrase the SCSH manual: | |
1440 | ||
1441 | When Unix tries to execute an executable file whose first two | |
1442 | characters are the `#!', it treats the file not as machine code to | |
1443 | be directly executed by the native processor, but as source code | |
1444 | to be executed by some interpreter. The interpreter to use is | |
1445 | specified immediately after the #! sequence on the first line of | |
1446 | the source file. The kernel reads in the name of the interpreter, | |
1447 | and executes that instead. It passes the interpreter the source | |
1448 | filename as its first argument, with the original arguments | |
1449 | following. Consult the Unix man page for the `exec' system call | |
1450 | for more information. | |
1451 | ||
1a1945be JB |
1452 | Now you can use Guile as an interpreter, using a mechanism which is a |
1453 | compatible subset of that provided by SCSH. | |
1454 | ||
3065a62a JB |
1455 | Guile now recognizes a '-s' command line switch, whose argument is the |
1456 | name of a file of Scheme code to load. It also treats the two | |
1457 | characters `#!' as the start of a comment, terminated by `!#'. Thus, | |
1458 | to make a file of Scheme code directly executable by Unix, insert the | |
1459 | following two lines at the top of the file: | |
1460 | ||
1461 | #!/usr/local/bin/guile -s | |
1462 | !# | |
1463 | ||
1464 | Guile treats the argument of the `-s' command-line switch as the name | |
1465 | of a file of Scheme code to load, and treats the sequence `#!' as the | |
1466 | start of a block comment, terminated by `!#'. | |
1467 | ||
1468 | For example, here's a version of 'echo' written in Scheme: | |
1469 | ||
1470 | #!/usr/local/bin/guile -s | |
1471 | !# | |
1472 | (let loop ((args (cdr (program-arguments)))) | |
1473 | (if (pair? args) | |
1474 | (begin | |
1475 | (display (car args)) | |
1476 | (if (pair? (cdr args)) | |
1477 | (display " ")) | |
1478 | (loop (cdr args))))) | |
1479 | (newline) | |
1480 | ||
1481 | Why does `#!' start a block comment terminated by `!#', instead of the | |
1482 | end of the line? That is the notation SCSH uses, and although we | |
1483 | don't yet support the other SCSH features that motivate that choice, | |
1484 | we would like to be backward-compatible with any existing Guile | |
3763761c JB |
1485 | scripts once we do. Furthermore, if the path to Guile on your system |
1486 | is too long for your kernel, you can start the script with this | |
1487 | horrible hack: | |
1488 | ||
1489 | #!/bin/sh | |
1490 | exec /really/long/path/to/guile -s "$0" ${1+"$@"} | |
1491 | !# | |
3065a62a JB |
1492 | |
1493 | Note that some very old Unix systems don't support the `#!' syntax. | |
1494 | ||
c6486f8a | 1495 | |
4b521edb | 1496 | ** You can now run Guile without installing it. |
6685dc83 JB |
1497 | |
1498 | Previous versions of the interactive Guile interpreter (`guile') | |
1499 | couldn't start up unless Guile's Scheme library had been installed; | |
1500 | they used the value of the environment variable `SCHEME_LOAD_PATH' | |
1501 | later on in the startup process, but not to find the startup code | |
1502 | itself. Now Guile uses `SCHEME_LOAD_PATH' in all searches for Scheme | |
1503 | code. | |
1504 | ||
1505 | To run Guile without installing it, build it in the normal way, and | |
1506 | then set the environment variable `SCHEME_LOAD_PATH' to a | |
1507 | colon-separated list of directories, including the top-level directory | |
1508 | of the Guile sources. For example, if you unpacked Guile so that the | |
1509 | full filename of this NEWS file is /home/jimb/guile-1.0b3/NEWS, then | |
1510 | you might say | |
1511 | ||
1512 | export SCHEME_LOAD_PATH=/home/jimb/my-scheme:/home/jimb/guile-1.0b3 | |
1513 | ||
c6486f8a | 1514 | |
4b521edb JB |
1515 | ** Guile's read-eval-print loop no longer prints #<unspecified> |
1516 | results. If the user wants to see this, she can evaluate the | |
1517 | expression (assert-repl-print-unspecified #t), perhaps in her startup | |
48d224d7 | 1518 | file. |
6685dc83 | 1519 | |
4b521edb JB |
1520 | ** Guile no longer shows backtraces by default when an error occurs; |
1521 | however, it does display a message saying how to get one, and how to | |
1522 | request that they be displayed by default. After an error, evaluate | |
1523 | (backtrace) | |
1524 | to see a backtrace, and | |
1525 | (debug-enable 'backtrace) | |
1526 | to see them by default. | |
6685dc83 | 1527 | |
6685dc83 | 1528 | |
d9fb83d9 | 1529 | |
4b521edb JB |
1530 | * Changes to Guile Scheme: |
1531 | ||
1532 | ** Guile now distinguishes between #f and the empty list. | |
1533 | ||
1534 | This is for compatibility with the IEEE standard, the (possibly) | |
1535 | upcoming Revised^5 Report on Scheme, and many extant Scheme | |
1536 | implementations. | |
1537 | ||
1538 | Guile used to have #f and '() denote the same object, to make Scheme's | |
1539 | type system more compatible with Emacs Lisp's. However, the change | |
1540 | caused too much trouble for Scheme programmers, and we found another | |
1541 | way to reconcile Emacs Lisp with Scheme that didn't require this. | |
1542 | ||
1543 | ||
1544 | ** Guile's delq, delv, delete functions, and their destructive | |
c6486f8a JB |
1545 | counterparts, delq!, delv!, and delete!, now remove all matching |
1546 | elements from the list, not just the first. This matches the behavior | |
1547 | of the corresponding Emacs Lisp functions, and (I believe) the Maclisp | |
1548 | functions which inspired them. | |
1549 | ||
1550 | I recognize that this change may break code in subtle ways, but it | |
1551 | seems best to make the change before the FSF's first Guile release, | |
1552 | rather than after. | |
1553 | ||
1554 | ||
4b521edb | 1555 | ** The compiled-library-path function has been deleted from libguile. |
6685dc83 | 1556 | |
4b521edb | 1557 | ** The facilities for loading Scheme source files have changed. |
c6486f8a | 1558 | |
4b521edb | 1559 | *** The variable %load-path now tells Guile which directories to search |
6685dc83 JB |
1560 | for Scheme code. Its value is a list of strings, each of which names |
1561 | a directory. | |
1562 | ||
4b521edb JB |
1563 | *** The variable %load-extensions now tells Guile which extensions to |
1564 | try appending to a filename when searching the load path. Its value | |
1565 | is a list of strings. Its default value is ("" ".scm"). | |
1566 | ||
1567 | *** (%search-load-path FILENAME) searches the directories listed in the | |
1568 | value of the %load-path variable for a Scheme file named FILENAME, | |
1569 | with all the extensions listed in %load-extensions. If it finds a | |
1570 | match, then it returns its full filename. If FILENAME is absolute, it | |
1571 | returns it unchanged. Otherwise, it returns #f. | |
6685dc83 | 1572 | |
4b521edb JB |
1573 | %search-load-path will not return matches that refer to directories. |
1574 | ||
1575 | *** (primitive-load FILENAME :optional CASE-INSENSITIVE-P SHARP) | |
1576 | uses %seach-load-path to find a file named FILENAME, and loads it if | |
1577 | it finds it. If it can't read FILENAME for any reason, it throws an | |
1578 | error. | |
6685dc83 JB |
1579 | |
1580 | The arguments CASE-INSENSITIVE-P and SHARP are interpreted as by the | |
4b521edb JB |
1581 | `read' function. |
1582 | ||
1583 | *** load uses the same searching semantics as primitive-load. | |
1584 | ||
1585 | *** The functions %try-load, try-load-with-path, %load, load-with-path, | |
1586 | basic-try-load-with-path, basic-load-with-path, try-load-module-with- | |
1587 | path, and load-module-with-path have been deleted. The functions | |
1588 | above should serve their purposes. | |
1589 | ||
1590 | *** If the value of the variable %load-hook is a procedure, | |
1591 | `primitive-load' applies its value to the name of the file being | |
1592 | loaded (without the load path directory name prepended). If its value | |
1593 | is #f, it is ignored. Otherwise, an error occurs. | |
1594 | ||
1595 | This is mostly useful for printing load notification messages. | |
1596 | ||
1597 | ||
1598 | ** The function `eval!' is no longer accessible from the scheme level. | |
1599 | We can't allow operations which introduce glocs into the scheme level, | |
1600 | because Guile's type system can't handle these as data. Use `eval' or | |
1601 | `read-and-eval!' (see below) as replacement. | |
1602 | ||
1603 | ** The new function read-and-eval! reads an expression from PORT, | |
1604 | evaluates it, and returns the result. This is more efficient than | |
1605 | simply calling `read' and `eval', since it is not necessary to make a | |
1606 | copy of the expression for the evaluator to munge. | |
1607 | ||
1608 | Its optional arguments CASE_INSENSITIVE_P and SHARP are interpreted as | |
1609 | for the `read' function. | |
1610 | ||
1611 | ||
1612 | ** The function `int?' has been removed; its definition was identical | |
1613 | to that of `integer?'. | |
1614 | ||
1615 | ** The functions `<?', `<?', `<=?', `=?', `>?', and `>=?'. Code should | |
1616 | use the R4RS names for these functions. | |
1617 | ||
1618 | ** The function object-properties no longer returns the hash handle; | |
1619 | it simply returns the object's property list. | |
1620 | ||
1621 | ** Many functions have been changed to throw errors, instead of | |
1622 | returning #f on failure. The point of providing exception handling in | |
1623 | the language is to simplify the logic of user code, but this is less | |
1624 | useful if Guile's primitives don't throw exceptions. | |
1625 | ||
1626 | ** The function `fileno' has been renamed from `%fileno'. | |
1627 | ||
1628 | ** The function primitive-mode->fdes returns #t or #f now, not 1 or 0. | |
1629 | ||
1630 | ||
1631 | * Changes to Guile's C interface: | |
1632 | ||
1633 | ** The library's initialization procedure has been simplified. | |
1634 | scm_boot_guile now has the prototype: | |
1635 | ||
1636 | void scm_boot_guile (int ARGC, | |
1637 | char **ARGV, | |
1638 | void (*main_func) (), | |
1639 | void *closure); | |
1640 | ||
1641 | scm_boot_guile calls MAIN_FUNC, passing it CLOSURE, ARGC, and ARGV. | |
1642 | MAIN_FUNC should do all the work of the program (initializing other | |
1643 | packages, reading user input, etc.) before returning. When MAIN_FUNC | |
1644 | returns, call exit (0); this function never returns. If you want some | |
1645 | other exit value, MAIN_FUNC may call exit itself. | |
1646 | ||
1647 | scm_boot_guile arranges for program-arguments to return the strings | |
1648 | given by ARGC and ARGV. If MAIN_FUNC modifies ARGC/ARGV, should call | |
1649 | scm_set_program_arguments with the final list, so Scheme code will | |
1650 | know which arguments have been processed. | |
1651 | ||
1652 | scm_boot_guile establishes a catch-all catch handler which prints an | |
1653 | error message and exits the process. This means that Guile exits in a | |
1654 | coherent way when system errors occur and the user isn't prepared to | |
1655 | handle it. If the user doesn't like this behavior, they can establish | |
1656 | their own universal catcher in MAIN_FUNC to shadow this one. | |
1657 | ||
1658 | Why must the caller do all the real work from MAIN_FUNC? The garbage | |
1659 | collector assumes that all local variables of type SCM will be above | |
1660 | scm_boot_guile's stack frame on the stack. If you try to manipulate | |
1661 | SCM values after this function returns, it's the luck of the draw | |
1662 | whether the GC will be able to find the objects you allocate. So, | |
1663 | scm_boot_guile function exits, rather than returning, to discourage | |
1664 | people from making that mistake. | |
1665 | ||
1666 | The IN, OUT, and ERR arguments were removed; there are other | |
1667 | convenient ways to override these when desired. | |
1668 | ||
1669 | The RESULT argument was deleted; this function should never return. | |
1670 | ||
1671 | The BOOT_CMD argument was deleted; the MAIN_FUNC argument is more | |
1672 | general. | |
1673 | ||
1674 | ||
1675 | ** Guile's header files should no longer conflict with your system's | |
1676 | header files. | |
1677 | ||
1678 | In order to compile code which #included <libguile.h>, previous | |
1679 | versions of Guile required you to add a directory containing all the | |
1680 | Guile header files to your #include path. This was a problem, since | |
1681 | Guile's header files have names which conflict with many systems' | |
1682 | header files. | |
1683 | ||
1684 | Now only <libguile.h> need appear in your #include path; you must | |
1685 | refer to all Guile's other header files as <libguile/mumble.h>. | |
1686 | Guile's installation procedure puts libguile.h in $(includedir), and | |
1687 | the rest in $(includedir)/libguile. | |
1688 | ||
1689 | ||
1690 | ** Two new C functions, scm_protect_object and scm_unprotect_object, | |
1691 | have been added to the Guile library. | |
1692 | ||
1693 | scm_protect_object (OBJ) protects OBJ from the garbage collector. | |
1694 | OBJ will not be freed, even if all other references are dropped, | |
1695 | until someone does scm_unprotect_object (OBJ). Both functions | |
1696 | return OBJ. | |
1697 | ||
1698 | Note that calls to scm_protect_object do not nest. You can call | |
1699 | scm_protect_object any number of times on a given object, and the | |
1700 | next call to scm_unprotect_object will unprotect it completely. | |
1701 | ||
1702 | Basically, scm_protect_object and scm_unprotect_object just | |
1703 | maintain a list of references to things. Since the GC knows about | |
1704 | this list, all objects it mentions stay alive. scm_protect_object | |
1705 | adds its argument to the list; scm_unprotect_object remove its | |
1706 | argument from the list. | |
1707 | ||
1708 | ||
1709 | ** scm_eval_0str now returns the value of the last expression | |
1710 | evaluated. | |
1711 | ||
1712 | ** The new function scm_read_0str reads an s-expression from a | |
1713 | null-terminated string, and returns it. | |
1714 | ||
1715 | ** The new function `scm_stdio_to_port' converts a STDIO file pointer | |
1716 | to a Scheme port object. | |
1717 | ||
1718 | ** The new function `scm_set_program_arguments' allows C code to set | |
1719 | the value teruturned by the Scheme `program-arguments' function. | |
6685dc83 | 1720 | |
6685dc83 | 1721 | \f |
1a1945be JB |
1722 | Older changes: |
1723 | ||
1724 | * Guile no longer includes sophisticated Tcl/Tk support. | |
1725 | ||
1726 | The old Tcl/Tk support was unsatisfying to us, because it required the | |
1727 | user to link against the Tcl library, as well as Tk and Guile. The | |
1728 | interface was also un-lispy, in that it preserved Tcl/Tk's practice of | |
1729 | referring to widgets by names, rather than exporting widgets to Scheme | |
1730 | code as a special datatype. | |
1731 | ||
1732 | In the Usenix Tk Developer's Workshop held in July 1996, the Tcl/Tk | |
1733 | maintainers described some very interesting changes in progress to the | |
1734 | Tcl/Tk internals, which would facilitate clean interfaces between lone | |
1735 | Tk and other interpreters --- even for garbage-collected languages | |
1736 | like Scheme. They expected the new Tk to be publicly available in the | |
1737 | fall of 1996. | |
1738 | ||
1739 | Since it seems that Guile might soon have a new, cleaner interface to | |
1740 | lone Tk, and that the old Guile/Tk glue code would probably need to be | |
1741 | completely rewritten, we (Jim Blandy and Richard Stallman) have | |
1742 | decided not to support the old code. We'll spend the time instead on | |
1743 | a good interface to the newer Tk, as soon as it is available. | |
5c54da76 | 1744 | |
8512dea6 | 1745 | Until then, gtcltk-lib provides trivial, low-maintenance functionality. |
deb95d71 | 1746 | |
5c54da76 JB |
1747 | \f |
1748 | Copyright information: | |
1749 | ||
ea00ecba | 1750 | Copyright (C) 1996,1997 Free Software Foundation, Inc. |
5c54da76 JB |
1751 | |
1752 | Permission is granted to anyone to make or distribute verbatim copies | |
1753 | of this document as received, in any medium, provided that the | |
1754 | copyright notice and this permission notice are preserved, | |
1755 | thus giving the recipient permission to redistribute in turn. | |
1756 | ||
1757 | Permission is granted to distribute modified versions | |
1758 | of this document, or of portions of it, | |
1759 | under the above conditions, provided also that they | |
1760 | carry prominent notices stating who last changed them. | |
1761 | ||
48d224d7 JB |
1762 | \f |
1763 | Local variables: | |
1764 | mode: outline | |
1765 | paragraph-separate: "[ \f]*$" | |
1766 | end: | |
1767 |