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