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