execution platform that can be linked in as a library when building
extensible programs.
-Please send bug reports to bug-guile@prep.ai.mit.edu.
+Please send bug reports to bug-guile@gnu.org.
+About Snapshots ======================================================
-Important Facts About Snapshots ======================================
-Please keep in mind that these sources are strictly experimental; they
-will usually not be well-tested, and may not even compile on some
-systems. They may contain interfaces which will change. They will
-usually not be of sufficient quality for use by people not comfortable
-hacking the innards of Guile. Caveat!
+Each night, we make the current Guile sources available via anonymous
+FTP. Please keep in mind that these sources are strictly
+experimental; they will usually not be well-tested, and may not even
+compile on some systems. They may contain interfaces which will
+change. They will usually not be of sufficient quality for use by
+people not comfortable hacking the innards of Guile. Caveat!
However, we're providing them anyway for several reasons. We'd like
to encourage people to get involved in developing Guile. People
And it allows us to start testing features earlier.
Nightly snapshots of the Guile development sources are available via
-anonymous FTP from ftp.cyclic.com, as /pub/guile/guile-snap.tar.gz.
+anonymous FTP from ftp.red-bean.com, as /pub/guile/guile-core-snap.tar.gz.
-Via the web, that's: ftp://ftp.cyclic.com/pub/guile/guile-snap.tar.gz
-For getit, that's: ftp.cyclic.com:/pub/guile/guile-snap.tar.gz
+Via the web, that's: ftp://ftp.red-bean.com/pub/guile/guile-core-snap.tar.gz
+For getit, that's: ftp.red-bean.com:/pub/guile/guile-core-snap.tar.gz
-
-The latest official Guile release is available via anonymous FTP from
-prep.ai.mit.edu, as /pub/gnu/guile-1.0.tar.gz.
-
-Via the web, that's: ftp://prep.ai.mit.edu/pub/gnu/guile-1.0.tar.gz
-For getit, that's: prep.ai.mit.edu:/pub/gnu/guile-1.0.tar.gz
-
-The mailing list `guile@cygnus.com' carries discussions, questions,
-and often answers, about Guile. To subscribe, send mail to
-guile-request@cygnus.com. Of course, please send bug reports (and
-fixes!) to bug-guile@prep.ai.mit.edu.
+The snapshot FTP site is mirrored at the following locations:
+ Austria: ftp://ftp.aec.at/pub/guile
+ Japan: ftp://ftp.jaist.ac.jp/pub/lang/scheme/guile
About This Distribution ==============================================
libguile.a --- an object library containing the Guile interpreter,
usually installed in /usr/local/lib. You can use Guile in
your own programs by linking against this.
+libqt.a --- an object library containing the QuickThreads primitives.
+ If you enabled thread support when you configured Guile, you
+ will need to link your code against this too.
<libguile.h>, <libguile/*.h> --- header files for libguile.a, usually
installed in /usr/local/include.
-
+ice-9, ice-9/*.scm --- run-time support for Guile: the module
+ system, read-eval-print loop, some R4RS code and other
+ infrastructure. Usually installed in
+ /usr/local/share/guile/<version>.
Interesting files include:
- INSTALL, which contains instructions on building and installing Guile.
The Guile source tree is laid out as follows:
-doc: Documentation for Guile, in Texinfo form. (At the moment, these
- manuals are incomplete and are currently being revised.)
libguile:
The Guile Scheme interpreter --- both the object library
for you to link with your programs, and the executable you can run.
library, found in this directory. Qt is under a separate
copyright; see `qt/README' for more details.
+(The present release doesn't include any documentation; the Guile
+manual is incomplete, and is currently being revised.)
+
Hacking It Yourself ==================================================
find it helpful to have the tools we use to develop Guile. They
are the following:
-Autoconf 2.12 --- a system for automatically generate `configure'
+Autoconf 2.12 --- a system for automatically generating `configure'
scripts from templates which list the non-portable features a
program would like to use. Available in
"ftp://prep.ai.mit.edu/pub/gnu".
-Automake 1.1n --- a system for automatically generating Makefiles that
+Automake 1.2d --- a system for automatically generating Makefiles that
conform to the (rather Byzantine) GNU coding standards. The
nice thing is that it takes care of hairy targets like 'make
dist' and 'make distclean', and automatically generates
- Makefile dependencies. Available in
+ Makefile dependencies. Automake is available in
"ftp://ftp.cygnus.com/pub/tromey".
-libtool 0.9d --- a system for managing the zillion hairy options needed
+ Before using automake, you may need to copy `threads.m4' and
+ `guile.m4' from the top directory of the Guile core disty to
+ `/usr/local/share/aclocal.
+
+libtool 1.0e --- a system for managing the zillion hairy options needed
on various systems to produce shared libraries. Available in
- "ftp://alpha.gnu.ai.mit.edu/gnu".
+ "ftp://alpha.gnu.org/gnu".
You are lost in a little maze of automatically generated files, all
different.
>
+Obtaining Guile ======================================================
+
+The latest official Guile release is available via anonymous FTP from
+prep.ai.mit.edu, as /pub/gnu/guile-1.2.tar.gz.
+
+Via the web, that's: ftp://prep.ai.mit.edu/pub/gnu/guile-1.2.tar.gz
+For getit, that's: prep.ai.mit.edu:/pub/gnu/guile-1.2.tar.gz
+
+The mailing list `guile@cygnus.com' carries discussions, questions,
+and often answers, about Guile. To subscribe, send mail to
+guile-request@cygnus.com. Of course, please send bug reports (and
+fixes!) to bug-guile@gnu.org.
+
+
Authors And Contributors =============================================
Many people have generously contributed to Guile. However, any errors
* stack overflow detection,
* the GDB patches to support debugging mixed Scheme/C code,
* the original implementation of weak hash tables,
-* the `threads' interface (rewriting Anthony Green's work), and
+* enhancements to the `threads' interface (based on Anthony Green's
+ work), and
* detection of circular references during printing.
Mark Galassi contributed the Guile high-level functions (gh_*), and
Anthony Green wrote the original version of `threads', the interface
between Guile and qt.
-Gary Houston wrote the Unix system call support, including the socket
-support, and did a lot of work on the error handling code.
+Gary Houston wrote much of the Unix system call support, including the
+socket support, and did a lot of work on the error handling code.
Tom Lord librarified SCM, yielding Guile. He wrote Guile's operating
system, Ice-9, and connected Guile to Tcl/Tk and the `rx' regular
expression matcher.
-Aubrey Jaffer seriously tuned performance and added features. He
-designed many hairy but beautiful parts of the tag system and
-evaluator.
+Aubrey Jaffer is the author of SCM upon which Guile is based. Guile
+started from SCM version 4e1 in November -94 and is still largely
+composed of the original SCM code.
George Carrette wrote SIOD, a stand-alone scheme interpreter.
Although most of this code as been rewritten or replaced over time,
HCoop / bpt / guile.git / blobdiff