*** empty log message ***

[bpt/guile.git] / NEWS

diff --git a/NEWS b/NEWS
index 19a1b8a..ba4fc7b 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -20,9 +20,15 @@ anonymous FTP from ftp.red-bean.com, as /pub/guile/guile-snap.tar.gz.
 Via the web, that's:  ftp://ftp.red-bean.com/pub/guile/guile-snap.tar.gz
 For getit, that's:    ftp.red-bean.com:/pub/guile/guile-snap.tar.gz
 
+** To run Guile without installing it, the procedure has changed a bit.
+
+If you used a separate build directory to compile Guile, you'll need
+to include the build directory in SCHEME_LOAD_PATH, as well as the
+source directory.  See the `INSTALL' file for examples.
+
 * Changes to the procedure for linking libguile with your programs
 
-** Like Guile 1.1, Guile 1.2 will now use the Rx regular expression
+** Like Guile 1.0, Guile 1.2 will now use the Rx regular expression
 library, if it is installed on your system.  When you are linking
 libguile into your own programs, this means you will have to link
 against -lguile, -lqt (if you configured Guile with thread support),
@@ -43,9 +49,6 @@ AC_CHECK_LIB(guile, scm_shell)
 You can disable them by giving the `--disable-dynamic-linking' option
 to configure.
 
-When dynamic linking is disabled or not supported on your system,
-the following functions throw errors, but they are still available.
-
   (dynamic-link FILENAME)
 
     Find the object file denoted by FILENAME (a string) and link it
@@ -99,6 +102,9 @@ the following functions throw errors, but they are still available.
     return value is converted to a Scheme number and returned from the
     call to `dynamic-args-call'.
 
+When dynamic linking is disabled or not supported on your system,
+the above functions throw errors, but they are still available.
+
 Here is a small example that works on GNU/Linux:
 
   (define libc-obj (dynamic-link "libc.so"))
@@ -122,12 +128,12 @@ underlying implementation for records, which in turn are used to
 implement modules, so all of these object now print differently and in
 a more informative way.
 
-The Scheme printer will examine the builtin variable
-*struct-printer* whenever it needs to print a structure object.  When
-this variable is not `#f' it is deemed to be a procedure and will be
-applied to the structure object and the output port.  When
-*struct-printer* is `#f' or the procedure return `#f' the structure
-object will be printed in the boring #<struct 80458270> form.
+The Scheme printer will examine the builtin variable *struct-printer*
+whenever it needs to print a structure object.  When this variable is
+not `#f' it is deemed to be a procedure and will be applied to the
+structure object and the output port.  When *struct-printer* is `#f'
+or the procedure return `#f' the structure object will be printed in
+the boring #<struct 80458270> form.
 
 This hook is used by some routines in ice-9/boot-9.scm to implement
 type specific printing routines.  Please read the comments there about
@@ -164,6 +170,12 @@ of SCSH's regular expression functions.  They are:
 
 * Changes to the scm_ interface
 
+** The new function scm_handle_by_message_noexit is just like the
+existing scm_handle_by_message function, except that it doesn't call
+exit to terminate the process.  Instead, it prints a message and just
+returns #f.  This might be a more appropriate catch-all handler for
+new dynamic roots and threads.
+
 * Changes to system call interfaces:
 
 ** The value returned by `raise' is now unspecified.  It throws an exception
@@ -222,6 +234,8 @@ We no longer distribute the documentation, since it was either out of
 date, or incomplete.  As soon as we have current documentation, we
 will distribute it.
 
+
+
 * Changes to the stand-alone interpreter
 
 ** guile now accepts command-line arguments compatible with SCSH, Olin