caused too much trouble for Scheme programmers, and we found another
way to reconcile Emacs Lisp with Scheme that didn't require this.
+
* You can now use Guile as a shell script interpreter.
To paraphrase the SCSH manual:
end of the line? That is the notation SCSH uses, and although we
don't yet support the other SCSH features that motivate that choice,
we would like to be backward-compatible with any existing Guile
-scripts once we do.
+scripts once we do. Furthermore, if the path to Guile on your system
+is too long for your kernel, you can start the script with this
+horrible hack:
+
+#!/bin/sh
+exec /really/long/path/to/guile -s "$0" ${1+"$@"}
+!#
Note that some very old Unix systems don't support the `#!' syntax.
+
* You can now run Guile without installing it.
Previous versions of the interactive Guile interpreter (`guile')
export SCHEME_LOAD_PATH=/home/jimb/my-scheme:/home/jimb/guile-1.0b3
+
* Guile's header files should no longer conflict with your system's
header files.
Guile's installation procedure puts libguile.h in $(includedir), and
the rest in $(includedir)/libguile.
+* Guile's delq, delv, delete functions, and their destructive
+counterparts, delq!, delv!, and delete!, now remove all matching
+elements from the list, not just the first. This matches the behavior
+of the corresponding Emacs Lisp functions, and (I believe) the Maclisp
+functions which inspired them.
+
+I recognize that this change may break code in subtle ways, but it
+seems best to make the change before the FSF's first Guile release,
+rather than after.
+
+
* The compiled-library-path function has been deleted from libguile.
+
* A variable and two new functions have been added to libguile:
** The variable %load-path now tells Guile which directories to search
decided not to support the old code. We'll spend the time instead on
a good interface to the newer Tk, as soon as it is available.
+Until then, gtcltk-lib provides trivial, low-maintenance functionality.
+
\f
Copyright information: