From ae2b295c7deaf2d7c18ad1ed9b6050970e56bae7 Mon Sep 17 00:00:00 2001 From: Bryan Newbold Date: Mon, 20 Feb 2017 00:05:31 -0800 Subject: Import Upstream version 5e2 --- scm.info | 4483 +++++++++++++++++++++++++++++++------------------------------- 1 file changed, 2243 insertions(+), 2240 deletions(-) (limited to 'scm.info') diff --git a/scm.info b/scm.info index f554663..59f4f8a 100644 --- a/scm.info +++ b/scm.info @@ -1,4 +1,4 @@ -This is scm.info, produced by makeinfo version 4.7 from scm.texi. | +This is scm.info, produced by makeinfo version 4.7 from scm.texi. INFO-DIR-SECTION The Algorithmic Language Scheme START-INFO-DIR-ENTRY @@ -9,10 +9,10 @@ END-INFO-DIR-ENTRY File: scm.info, Node: Top, Next: Overview, Prev: (dir), Up: (dir) This manual documents the SCM Scheme implementation. SCM version -5e1 was released June 2005. The most recent information about SCM can | -be found on SCM's "WWW" home page: | +5e2 was released February 2006. The most recent information about SCM | +can be found on SCM's "WWW" home page: | - `http://swiss.csail.mit.edu/~jaffer/SCM' | + `http://swiss.csail.mit.edu/~jaffer/SCM' Copyright (C) 1990-1999 Free Software Foundation @@ -43,8 +43,8 @@ approved by the author.  File: scm.info, Node: Overview, Next: Installing SCM, Prev: Top, Up: Top -1 Overview | -********** | +1 Overview +********** Scm is a portable Scheme implementation written in C. Scm provides a machine independent platform for [JACAL], a symbolic algebra system. @@ -59,8 +59,8 @@ machine independent platform for [JACAL], a symbolic algebra system.  File: scm.info, Node: SCM Features, Next: SCM Authors, Prev: Overview, Up: Overview -1.1 Features | -============ | +1.1 Features +============ * Conforms to Revised^5 Report on the Algorithmic Language Scheme [R5RS] and the [IEEE] P1178 specification. @@ -109,8 +109,8 @@ File: scm.info, Node: SCM Features, Next: SCM Authors, Prev: Overview, Up: O  File: scm.info, Node: SCM Authors, Next: Copying, Prev: SCM Features, Up: Overview -1.2 Authors | -=========== | +1.2 Authors +=========== Aubrey Jaffer (agj @ alum.mit.edu) Most of SCM. @@ -138,70 +138,70 @@ file `ChangeLog', a log of changes that have been made to scm.  File: scm.info, Node: Copying, Next: Bibliography, Prev: SCM Authors, Up: Overview -1.3 Copyright | -============= | +1.3 Copyright +============= Authors have assigned their SCM copyrights to: Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111, USA -* Menu: | - | -* The SCM License:: | -* SIOD copyright:: | - | +* Menu: + +* The SCM License:: +* SIOD copyright:: +  File: scm.info, Node: The SCM License, Next: SIOD copyright, Prev: Copying, Up: Copying - | -1.3.1 The SCM License | ---------------------- | - | -The license of SCM consists of the GNU GPL plus a special statement | -giving blanket permission to link with non-free software. This is the | -license statement as found in any individual file that it applies to: | - | - This program is free software; you can redistribute it and/or | - modify it under the terms of the GNU General Public License as | - published by the Free Software Foundation; either version 2, or | - (at your option) any later version. | - | - This program is distributed in the hope that it will be useful, but | - WITHOUT ANY WARRANTY; without even the implied warranty of | - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU | - General Public License for more details. | - | - You should have received a copy of the GNU General Public License | - along with this software; see the file COPYING. If not, write to | - the Free Software Foundation, Inc., 59 Temple Place, Suite 330, | - Boston, MA 02111-1307 USA | - | - As a special exception, the Free Software Foundation gives | - permission for additional uses of the text contained in its | - release of SCM. | - | - The exception is that, if you link the SCM library with other | - files to produce an executable, this does not by itself cause the | - resulting executable to be covered by the GNU General Public | - License. Your use of that executable is in no way restricted on | - account of linking the SCM library code into it. | - | - This exception does not however invalidate any other reasons why | - the executable file might be covered by the GNU General Public | - License. | - | - This exception applies only to the code released by the Free | - Software Foundation under the name SCM. If you copy code from | - other Free Software Foundation releases into a copy of SCM, as the | - General Public License permits, the exception does not apply to | - the code that you add in this way. To avoid misleading anyone as | - to the status of such modified files, you must delete this | - exception notice from them. | - | - If you write modifications of your own for SCM, it is your choice | - whether to permit this exception to apply to your modifications. | - If you do not wish that, delete this exception notice. | - | + +1.3.1 The SCM License +--------------------- + +The license of SCM consists of the GNU GPL plus a special statement +giving blanket permission to link with non-free software. This is the +license statement as found in any individual file that it applies to: + + This program is free software; you can redistribute it and/or + modify it under the terms of the GNU General Public License as + published by the Free Software Foundation; either version 2, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, but + WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this software; see the file COPYING. If not, write to + the Free Software Foundation, Inc., 59 Temple Place, Suite 330, + Boston, MA 02111-1307 USA + + As a special exception, the Free Software Foundation gives + permission for additional uses of the text contained in its + release of SCM. + + The exception is that, if you link the SCM library with other + files to produce an executable, this does not by itself cause the + resulting executable to be covered by the GNU General Public + License. Your use of that executable is in no way restricted on + account of linking the SCM library code into it. + + This exception does not however invalidate any other reasons why + the executable file might be covered by the GNU General Public + License. + + This exception applies only to the code released by the Free + Software Foundation under the name SCM. If you copy code from + other Free Software Foundation releases into a copy of SCM, as the + General Public License permits, the exception does not apply to + the code that you add in this way. To avoid misleading anyone as + to the status of such modified files, you must delete this + exception notice from them. + + If you write modifications of your own for SCM, it is your choice + whether to permit this exception to apply to your modifications. + If you do not wish that, delete this exception notice. + Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that @@ -232,9 +232,9 @@ OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.  File: scm.info, Node: SIOD copyright, Prev: The SCM License, Up: Copying - | -1.3.2 SIOD copyright | --------------------- | + +1.3.2 SIOD copyright +-------------------- COPYRIGHT (c) 1989 BY @@ -267,8 +267,8 @@ Cambridge, MA 02138  File: scm.info, Node: Bibliography, Prev: Copying, Up: Overview -1.4 Bibliography | -================ | +1.4 Bibliography +================ [IEEE] `IEEE Standard 1178-1990. IEEE Standard for the Scheme @@ -331,8 +331,8 @@ File: scm.info, Node: Bibliography, Prev: Copying, Up: Overview  File: scm.info, Node: Installing SCM, Next: Operational Features, Prev: Overview, Up: Top -2 Installing SCM | -**************** | +2 Installing SCM +**************** * Menu: @@ -352,8 +352,8 @@ File: scm.info, Node: Installing SCM, Next: Operational Features, Prev: Overv  File: scm.info, Node: Making SCM, Next: SLIB, Prev: Installing SCM, Up: Installing SCM -2.1 Making SCM | -============== | +2.1 Making SCM +============== The SCM distribution has "Makefile" which contains rules for making "scmlit", a "bare-bones" version of SCM sufficient for running `build'. @@ -364,7 +364,7 @@ Makefiles are not portable to the majority of platforms. If `Makefile' works for you, good; If not, I don't want to hear about it. If you need to compile SCM without build, there are several ways to proceed: - * Use the build (http://swiss.csail.mit.edu/~jaffer/buildscm.html) | + * Use the build (http://swiss.csail.mit.edu/~jaffer/buildscm.html) web page to create custom batch scripts for compiling SCM. * Use SCM on a different platform to run `build' to create a script @@ -378,8 +378,8 @@ need to compile SCM without build, there are several ways to proceed:  File: scm.info, Node: SLIB, Next: Building SCM, Prev: Making SCM, Up: Installing SCM -2.2 SLIB | -======== | +2.2 SLIB +======== [SLIB] is a portable Scheme library meant to provide compatibility and utility functions for all standard Scheme implementations. Although @@ -387,18 +387,18 @@ SLIB is not _neccessary_ to run SCM, I strongly suggest you obtain and install it. Bug reports about running SCM without SLIB have very low priority. SLIB is available from the same sites as SCM: - * swiss.csail.mit.edu:/pub/scm/slib3a2.tar.gz | + * swiss.csail.mit.edu:/pub/scm/slib3a3.tar.gz | - * ftp.gnu.org:/pub/gnu/jacal/slib3a2.tar.gz | + * ftp.gnu.org:/pub/gnu/jacal/slib3a3.tar.gz | - * ftp.cs.indiana.edu:/pub/scheme-repository/imp/slib3a2.tar.gz | + * ftp.cs.indiana.edu:/pub/scheme-repository/imp/slib3a3.tar.gz | -Unpack SLIB (`tar xzf slib3a2.tar.gz' or `unzip -ao slib3a2.zip') in an | +Unpack SLIB (`tar xzf slib3a3.tar.gz' or `unzip -ao slib3a3.zip') in an | appropriate directory for your system; both `tar' and `unzip' will create the directory `slib'. Then create a file `require.scm' in the SCM "implementation-vicinity" -(this is the same directory as where the file `Init5e1.scm' is | +(this is the same directory as where the file `Init5e2.scm' is | installed). `require.scm' should have the contents: (define (library-vicinity) "/usr/local/lib/slib/") @@ -422,8 +422,8 @@ overrides `require.scm'. Again, absolute pathnames are recommended.  File: scm.info, Node: Building SCM, Next: Installing Dynamic Linking, Prev: SLIB, Up: Installing SCM -2.3 Building SCM | -================ | +2.3 Building SCM +================ The file "build" loads the file "build.scm", which constructs a relational database of how to compile and link SCM executables. @@ -441,8 +441,8 @@ ai.mit.edu.  File: scm.info, Node: Invoking Build, Next: Build Options, Prev: Building SCM, Up: Building SCM -2.3.1 Invoking Build | --------------------- | +2.3.1 Invoking Build +-------------------- The _all_ method will also work for MS-DOS and unix. Use the _all_ method if you encounter problems with `build'. @@ -470,7 +470,7 @@ script with the `arrays', `inexact', and `bignums' options as defaults. # unix (linux) script created by SLIB/batch # ================ Write file with C defines rm -f scmflags.h - echo '#define IMPLINIT "Init5e1.scm"'>>scmflags.h | + echo '#define IMPLINIT "Init5e2.scm"'>>scmflags.h | echo '#define BIGNUMS'>>scmflags.h echo '#define FLOATS'>>scmflags.h echo '#define ARRAYS'>>scmflags.h @@ -489,7 +489,7 @@ in the `-p' or `--platform=' option. # unix (darwin) script created by SLIB/batch # ================ Write file with C defines rm -f scmflags.h - echo '#define IMPLINIT "Init5e1.scm"'>>scmflags.h | + echo '#define IMPLINIT "Init5e2.scm"'>>scmflags.h | # ================ Compile C source files cc -O3 -c continue.c scm.c scmmain.c findexec.c script.c time.c repl.c scl.c eval.c sys.c subr.c debug.c unif.c rope.c # ================ Link C object files @@ -499,149 +499,149 @@ in the `-p' or `--platform=' option.  File: scm.info, Node: Build Options, Next: Compiling and Linking Custom Files, Prev: Invoking Build, Up: Building SCM -2.3.2 Build Options | -------------------- | +2.3.2 Build Options +------------------- The options to "build" specify what, where, and how to build a SCM program or dynamically linked module. These options are unrelated to the SCM command line options. - -- Build Option: -p PLATFORM-NAME | - -- Build Option: --platform=PLATFORM-NAME | + -- Build Option: -p PLATFORM-NAME + -- Build Option: --platform=PLATFORM-NAME specifies that the compilation should be for a computer/operating-system combination called PLATFORM-NAME. - _Note_ The case of PLATFORM-NAME is distinguised. The current | + _Note_ The case of PLATFORM-NAME is distinguised. The current PLATFORM-NAMEs are all lower-case. The platforms defined by table "platform" in `build.scm' are: - Table: platform | - name processor operating-system compiler | - #f processor-family operating-system #f | - symbol processor-family operating-system symbol | - symbol symbol symbol symbol | - ================= ================= ================= ================= | - *unknown* *unknown* unix cc | - acorn-unixlib acorn *unknown* cc | - aix powerpc aix cc | - alpha-elf alpha unix cc | - alpha-linux alpha linux gcc | - amiga-aztec m68000 amiga cc | - amiga-dice-c m68000 amiga dcc | - amiga-gcc m68000 amiga gcc | - amiga-sas m68000 amiga lc | - atari-st-gcc m68000 atari.st gcc | - atari-st-turbo-c m68000 atari.st tcc | - borland-c i8086 ms-dos bcc | - darwin powerpc unix cc | - djgpp i386 ms-dos gcc | - freebsd i386 unix cc | - gcc *unknown* unix gcc | - gnu-win32 i386 unix gcc | - highc i386 ms-dos hc386 | - hp-ux hp-risc hp-ux cc | - irix mips irix gcc | - linux i386 linux gcc | - linux-aout i386 linux gcc | - microsoft-c i8086 ms-dos cl | - microsoft-c-nt i386 ms-dos cl | - microsoft-quick-c i8086 ms-dos qcl | - ms-dos i8086 ms-dos cc | - netbsd *unknown* unix gcc | - openbsd *unknown* unix gcc | - os/2-cset i386 os/2 icc | - os/2-emx i386 os/2 gcc | - osf1 alpha unix cc | - plan9-8 i386 plan9 8c | - sunos sparc sunos cc | - svr4 *unknown* unix cc | - svr4-gcc-sun-ld sparc sunos gcc | - turbo-c i8086 ms-dos tcc | - unicos cray unicos cc | - unix *unknown* unix cc | - vms vax vms cc | - vms-gcc vax vms gcc | - watcom-9.0 i386 ms-dos wcc386p | - - -- Build Option: -f PATHNAME | + Table: platform + name processor operating-system compiler + #f processor-family operating-system #f + symbol processor-family operating-system symbol + symbol symbol symbol symbol + ================= ================= ================= ================= + *unknown* *unknown* unix cc + acorn-unixlib acorn *unknown* cc + aix powerpc aix cc + alpha-elf alpha unix cc + alpha-linux alpha linux gcc + amiga-aztec m68000 amiga cc + amiga-dice-c m68000 amiga dcc + amiga-gcc m68000 amiga gcc + amiga-sas m68000 amiga lc + atari-st-gcc m68000 atari.st gcc + atari-st-turbo-c m68000 atari.st tcc + borland-c i8086 ms-dos bcc + darwin powerpc unix cc + djgpp i386 ms-dos gcc + freebsd i386 unix cc + gcc *unknown* unix gcc + gnu-win32 i386 unix gcc + highc i386 ms-dos hc386 + hp-ux hp-risc hp-ux cc + irix mips irix gcc + linux i386 linux gcc + linux-aout i386 linux gcc + microsoft-c i8086 ms-dos cl + microsoft-c-nt i386 ms-dos cl + microsoft-quick-c i8086 ms-dos qcl + ms-dos i8086 ms-dos cc + netbsd *unknown* unix gcc + openbsd *unknown* unix gcc + os/2-cset i386 os/2 icc + os/2-emx i386 os/2 gcc + osf1 alpha unix cc + plan9-8 i386 plan9 8c + sunos sparc sunos cc + svr4 *unknown* unix cc + svr4-gcc-sun-ld sparc sunos gcc + turbo-c i8086 ms-dos tcc + unicos cray unicos cc + unix *unknown* unix cc + vms vax vms cc + vms-gcc vax vms gcc + watcom-9.0 i386 ms-dos wcc386p + + -- Build Option: -f PATHNAME specifies that the build options contained in PATHNAME be spliced - into the argument list at this point. The use of option files can | - separate functional features from platform-specific ones. | - - The `Makefile' calls out builds with the options in `.opt' files: | - | - `dlls.opt' | - Options for Makefile targets mydlls, myturtle, and x.so. | - | - `gdb.opt' | - Options for udgdbscm and gdbscm. | - | - `libscm.opt' | - Options for libscm.a. | - | - `pg.opt' | - Options for pgscm, which instruments C functions. | - | - `udscm4.opt' | - Options for targets udscm4 and dscm4 (scm). | - | - `udscm5.opt' | - Options for targets udscm5 and dscm5 (scm). | - | - The Makefile creates options files it depends on only if they do | - not already exist. | - | - -- Build Option: -o FILENAME | - -- Build Option: --outname=FILENAME | + into the argument list at this point. The use of option files can + separate functional features from platform-specific ones. + + The `Makefile' calls out builds with the options in `.opt' files: + + `dlls.opt' + Options for Makefile targets mydlls, myturtle, and x.so. + + `gdb.opt' + Options for udgdbscm and gdbscm. + + `libscm.opt' + Options for libscm.a. + + `pg.opt' + Options for pgscm, which instruments C functions. + + `udscm4.opt' + Options for targets udscm4 and dscm4 (scm). + + `udscm5.opt' + Options for targets udscm5 and dscm5 (scm). + + The Makefile creates options files it depends on only if they do + not already exist. + + -- Build Option: -o FILENAME + -- Build Option: --outname=FILENAME specifies that the compilation should produce an executable or object name of FILENAME. The default is `scm'. Executable suffixes will be added if neccessary, e.g. `scm' => `scm.exe'. - -- Build Option: -l LIBNAME ... | - -- Build Option: --libraries=LIBNAME | + -- Build Option: -l LIBNAME ... + -- Build Option: --libraries=LIBNAME specifies that the LIBNAME should be linked with the executable produced. If compile flags or include directories (`-I') are needed, they are automatically supplied for compilations. The `c' library is always included. SCM "features" specify any libraries they need; so you shouldn't need this option often. - -- Build Option: -D DEFINITION ... | - -- Build Option: --defines=DEFINITION | + -- Build Option: -D DEFINITION ... + -- Build Option: --defines=DEFINITION specifies that the DEFINITION should be made in any C source compilations. If compile flags or include directories (`-I') are needed, they are automatically supplied for compilations. SCM "features" specify any flags they need; so you shouldn't need this option often. - -- Build Option: --compiler-options=FLAG | + -- Build Option: --compiler-options=FLAG specifies that that FLAG will be put on compiler command-lines. - -- Build Option: --linker-options=FLAG | + -- Build Option: --linker-options=FLAG specifies that that FLAG will be put on linker command-lines. - -- Build Option: -s PATHNAME | - -- Build Option: --scheme-initial=PATHNAME | + -- Build Option: -s PATHNAME + -- Build Option: --scheme-initial=PATHNAME specifies that PATHNAME should be the default location of the SCM - initialization file `Init5e1.scm'. SCM tries several likely | + initialization file `Init5e2.scm'. SCM tries several likely | locations before resorting to PATHNAME (*note File-System Habitat::). If not specified, the current directory (where build is building) is used. - -- Build Option: -c PATHNAME ... | - -- Build Option: --c-source-files=PATHNAME | + -- Build Option: -c PATHNAME ... + -- Build Option: --c-source-files=PATHNAME specifies that the C source files PATHNAME ... are to be compiled. - -- Build Option: -j PATHNAME ... | - -- Build Option: --object-files=PATHNAME | + -- Build Option: -j PATHNAME ... + -- Build Option: --object-files=PATHNAME specifies that the object files PATHNAME ... are to be linked. - -- Build Option: -i CALL ... | - -- Build Option: --initialization=CALL | + -- Build Option: -i CALL ... + -- Build Option: --initialization=CALL specifies that the C functions CALL ... are to be invoked during initialization. - -- Build Option: -t BUILD-WHAT | - -- Build Option: --type=BUILD-WHAT | + -- Build Option: -t BUILD-WHAT + -- Build Option: --type=BUILD-WHAT specifies in general terms what sort of thing to build. The choices are: `exe' @@ -658,8 +658,8 @@ the SCM command line options. The default is to build an executable. - -- Build Option: -h BATCH-SYNTAX | - -- Build Option: -batch-dialect=BATCH-SYNTAX | + -- Build Option: -h BATCH-SYNTAX + -- Build Option: -batch-dialect=BATCH-SYNTAX specifies how to build. The default is to create a batch file for the host system. The SLIB file `batch.scm' knows how to create batch files for: @@ -680,13 +680,13 @@ the SCM command line options. This option outputs Scheme code. - -- Build Option: -w BATCH-FILENAME | - -- Build Option: -script-name=BATCH-FILENAME | + -- Build Option: -w BATCH-FILENAME + -- Build Option: -script-name=BATCH-FILENAME specifies where to write the build script. The default is to display it on `(current-output-port)'. - -- Build Option: -F FEATURE ... | - -- Build Option: --features=FEATURE | + -- Build Option: -F FEATURE ... + -- Build Option: --features=FEATURE specifies to build the given features into the executable. The defined features are: @@ -702,9 +702,9 @@ the SCM command line options. "bignums" Large precision integers. - "byte" | - Treating strings as byte-vectors. | - | + "byte" + Treating strings as byte-vectors. + "careful-interrupt-masking" Define this for extra checking of interrupt masking and some simple checks for proper use of malloc and free. This is for @@ -740,9 +740,9 @@ the SCM command line options. `careful-interrupt-masking', and `stack-limit'; uses `-g' flags for debugging SCM source code. - "differ" | - Sequence comparison | - | + "differ" + Sequence comparison + "dump" Convert a running scheme program into an executable file. @@ -827,8 +827,8 @@ the SCM command line options. numbers. "socket" - BSD "socket" interface. Socket addr functions require | - inexacts or bignums for 32-bit precision. | + BSD "socket" interface. Socket addr functions require + inexacts or bignums for 32-bit precision. "stack-limit" Use to enable checking for stack overflow. Define value of @@ -848,9 +848,9 @@ the SCM command line options. Those unix features which have not made it into the Posix specs: nice, acct, lstat, readlink, symlink, mknod and sync. - "wb" | - WB database with relational wrapper. | - | + "wb" + WB database with relational wrapper. + "windows" Microsoft Windows executable. @@ -864,8 +864,8 @@ the SCM command line options.  File: scm.info, Node: Compiling and Linking Custom Files, Prev: Build Options, Up: Building SCM -2.3.3 Compiling and Linking Custom Files | ----------------------------------------- | +2.3.3 Compiling and Linking Custom Files +---------------------------------------- A correspondent asks: @@ -875,14 +875,14 @@ A correspondent asks: build.scm or the Makefile or both? (*note Changing Scm:: has instructions describing the C code format). Suppose -a C file "foo.c" has functions you wish to add to SCM. To compile and | -link your file at compile time, use the `-c' and `-i' options to build: | +a C file "foo.c" has functions you wish to add to SCM. To compile and +link your file at compile time, use the `-c' and `-i' options to build: bash$ ./build -c foo.c -i init_foo -| #! /bin/sh rm -f scmflags.h - echo '#define IMPLINIT "/home/jaffer/scm/Init5e1.scm"'>>scmflags.h | + echo '#define IMPLINIT "/home/jaffer/scm/Init5e2.scm"'>>scmflags.h | echo '#define COMPILED_INITS init_foo();'>>scmflags.h echo '#define BIGNUMS'>>scmflags.h echo '#define FLOATS'>>scmflags.h @@ -898,7 +898,7 @@ To make a dynamically loadable object file use the `-t dll' option: -| #! /bin/sh rm -f scmflags.h - echo '#define IMPLINIT "/home/jaffer/scm/Init5e1.scm"'>>scmflags.h | + echo '#define IMPLINIT "/home/jaffer/scm/Init5e2.scm"'>>scmflags.h | echo '#define BIGNUMS'>>scmflags.h echo '#define FLOATS'>>scmflags.h echo '#define ARRAYS'>>scmflags.h @@ -914,8 +914,8 @@ add a compiled dll file to SLIB's catalog.  File: scm.info, Node: Installing Dynamic Linking, Next: Configure Module Catalog, Prev: Building SCM, Up: Installing SCM -2.4 Installing Dynamic Linking | -============================== | +2.4 Installing Dynamic Linking +============================== Dynamic linking has not been ported to all platforms. Operating systems in the BSD family (a.out binary format) can usually be ported to "DLD". @@ -954,15 +954,15 @@ These notes about using libdl on SunOS are from `gcc.info':  File: scm.info, Node: Configure Module Catalog, Next: Saving Images, Prev: Installing Dynamic Linking, Up: Installing SCM -2.5 Configure Module Catalog | -============================ | +2.5 Configure Module Catalog +============================ The SLIB module "catalog" can be extended to define other `require'-able packages by adding calls to the Scheme source file `mkimpcat.scm'. Within `mkimpcat.scm', the following procedures are defined. - -- Function: add-link feature object-file lib1 ... | + -- Function: add-link feature object-file lib1 ... FEATURE should be a symbol. OBJECT-FILE should be a string naming a file containing compiled "object-code". Each LIBn argument should be either a string naming a library file or `#f'. @@ -983,7 +983,7 @@ defined. link:able-suffix)) - -- Function: add-alias alias feature | + -- Function: add-alias alias feature ALIAS and FEATURE are symbols. The procedure `add-alias' registers ALIAS as an alias for FEATURE. An unspecified value is returned. @@ -991,7 +991,7 @@ defined. `add-alias' causes `(require 'ALIAS)' to behave like `(require 'FEATURE)'. - -- Function: add-source feature filename | + -- Function: add-source feature filename FEATURE is a symbol. FILENAME is a string naming a file containing Scheme source code. The procedure `add-source' registers FEATURE so that the first time `require' is called with @@ -1004,8 +1004,8 @@ Remember to delete the file `slibcat' after modifying the file  File: scm.info, Node: Saving Images, Next: Automatic C Preprocessor Definitions, Prev: Configure Module Catalog, Up: Installing SCM -2.6 Saving Images | -================= | +2.6 Saving Images +================= In SCM, the ability to save running program images is called "dump" (*note Dump::). In order to make `dump' available to SCM, build with @@ -1021,8 +1021,8 @@ file from emacs.  File: scm.info, Node: Automatic C Preprocessor Definitions, Next: Problems Compiling, Prev: Saving Images, Up: Installing SCM -2.7 Automatic C Preprocessor Definitions | -======================================== | +2.7 Automatic C Preprocessor Definitions +======================================== These `#defines' are automatically provided by preprocessors of various C compilers. SCM uses the presence or absence of these definitions to @@ -1037,6 +1037,7 @@ lines or add a `#define FLAG' line to `scmfig.h' or the beginning of ARM_ULIB Huw Rogers free unix library for acorn archimedes AZTEC_C Aztec_C 5.2a __CYGWIN__ Cygwin + __CYGWIN32__ Cygwin | _DCC Dice C on AMIGA __GNUC__ Gnu CC (and DJGPP) __EMX__ Gnu C port (gcc/emx 0.8e) to OS/2 2.0 @@ -1066,13 +1067,14 @@ lines or add a `#define FLAG' line to `scmfig.h' or the beginning of macintosh Macintosh (THINK_C and __MWERKS__ define) MCH_AMIGA Aztec_c 5.2a on AMIGA __MACH__ Apple Darwin + __MINGW32__ MinGW - Minimalist GNU for Windows | MSDOS Microsoft C 5.10 and 6.00A _MSDOS Microsoft CLARM and CLTHUMB compilers. __MSDOS__ Turbo C, Borland C, and DJGPP __NetBSD__ NetBSD nosve Control Data NOS/VE SVR2 System V Revision 2. - sun SunOS | + sun SunOS __SVR4 SunOS THINK_C developement environment for the Macintosh ultrix VAX with ULTRIX operating system. @@ -1091,9 +1093,9 @@ lines or add a `#define FLAG' line to `scmfig.h' or the beginning of __alpha DEC Alpha processor __alpha__ DEC Alpha processor hp9000s800 HP RISC processor - __ia64 GCC on IA64 | - __ia64__ GCC on IA64 | - _LONGLONG GCC on IA64 | + __ia64 GCC on IA64 + __ia64__ GCC on IA64 + _LONGLONG GCC on IA64 __i386__ DJGPP i386 DJGPP _M_ARM Microsoft CLARM compiler defines as 4 for ARM. @@ -1107,12 +1109,13 @@ lines or add a `#define FLAG' line to `scmfig.h' or the beginning of sequent Sequent computer tahoe CCI Tahoe processor vax VAX processor + __x86_64 AMD Opteron |  File: scm.info, Node: Problems Compiling, Next: Problems Linking, Prev: Automatic C Preprocessor Definitions, Up: Installing SCM -2.8 Problems Compiling | -====================== | +2.8 Problems Compiling +====================== FILE PROBLEM / MESSAGE HOW TO FIX *.c include file not found. Correct the status of @@ -1144,8 +1147,8 @@ scl.c syntax error. #define SYSTNAME to your system  File: scm.info, Node: Problems Linking, Next: Problems Running, Prev: Problems Compiling, Up: Installing SCM -2.9 Problems Linking | -==================== | +2.9 Problems Linking +==================== PROBLEM HOW TO FIX _sin etc. missing. Uncomment LIBS in makefile. @@ -1153,8 +1156,8 @@ _sin etc. missing. Uncomment LIBS in makefile.  File: scm.info, Node: Problems Running, Next: Testing, Prev: Problems Linking, Up: Installing SCM -2.10 Problems Running | -===================== | +2.10 Problems Running +===================== PROBLEM HOW TO FIX Opening message and then machine Change memory model option to C @@ -1173,17 +1176,17 @@ remove in scmfig.h and Do so and recompile files. recompile scm. add in scmfig.h and recompile scm. -ERROR: Init5e1.scm not found. Assign correct IMPLINIT in makefile | +ERROR: Init5e2.scm not found. Assign correct IMPLINIT in makefile | or scmfig.h. Define environment variable SCM_INIT_PATH to be the full - pathname of Init5e1.scm. | + pathname of Init5e2.scm. | WARNING: require.scm not found. Define environment variable SCHEME_LIBRARY_PATH to be the full pathname of the scheme library [SLIB]. Change library-vicinity in - Init5e1.scm to point to library or | + Init5e2.scm to point to library or | remove. Make sure the value of (library-vicinity) has a trailing @@ -1192,8 +1195,8 @@ WARNING: require.scm not found. Define environment variable  File: scm.info, Node: Testing, Next: Reporting Problems, Prev: Problems Running, Up: Installing SCM -2.11 Testing | -============ | +2.11 Testing +============ Loading `r4rstest.scm' in the distribution will run an [R4RS] conformance test on `scm'. @@ -1243,7 +1246,7 @@ Some symbol names print incorrectly. Change memory model option to C than HEAP_SEG_SIZE). ERROR: Rogue pointer in Heap. See above under machine crashes. Newlines don't appear correctly in Check file mode (define OPEN_... in -output files. `Init5e1.scm'). | +output files. `Init5e2.scm'). | Spaces or control characters appear Check character defines in in symbol names. `scmfig.h'. Negative numbers turn positive. Check SRS in `scmfig.h'. @@ -1258,14 +1261,14 @@ Sparc(SUN-4) heap is growing out of control This causes lots of stuff which should be collected to not be. This will be a problem with any _conservative_ GC until we find what instruction will clear the register windows. This problem is - exacerbated by using lots of call-with-current-continuations. A | - possible fix for dynthrow() is commented out in `continue.c'. | + exacerbated by using lots of call-with-current-continuations. A + possible fix for dynthrow() is commented out in `continue.c'.  File: scm.info, Node: Reporting Problems, Prev: Testing, Up: Installing SCM -2.12 Reporting Problems | -======================= | +2.12 Reporting Problems +======================= Reported problems and solutions are grouped under Compiling, Linking, Running, and Testing. If you don't find your problem listed there, you @@ -1290,8 +1293,8 @@ include:  File: scm.info, Node: Operational Features, Next: The Language, Prev: Installing SCM, Up: Top -3 Operational Features | -********************** | +3 Operational Features +********************** * Menu: @@ -1302,7 +1305,7 @@ File: scm.info, Node: Operational Features, Next: The Language, Prev: Install * SCM Session:: * Editing Scheme Code:: * Debugging Scheme Code:: -* Debugging Continuations:: | +* Debugging Continuations:: * Errors:: * Memoized Expressions:: * Internal State:: @@ -1311,8 +1314,8 @@ File: scm.info, Node: Operational Features, Next: The Language, Prev: Install  File: scm.info, Node: Invoking SCM, Next: SCM Options, Prev: Operational Features, Up: Operational Features -3.1 Invoking SCM | -================ | +3.1 Invoking SCM +================ scm [-a kbytes] [-muvbiq] [-version] [-help] [[-]-no-init-file] [-p int] [-r feature] [-h feature] @@ -1326,7 +1329,7 @@ variable SCM_INIT_PATH. If SCM_INIT_PATH is not defined or if the file it names is not present, `scm' tries to find the directory containing the executable file. If it is able to locate the executable, `scm' looks for the initialization -file (usually `Init5e1.scm') in platform-dependent directories relative | +file (usually `Init5e2.scm') in platform-dependent directories relative | to this directory. See *Note File-System Habitat:: for a blow-by-blow description. @@ -1335,12 +1338,12 @@ compile parameter IMPLINIT (defined in the makefile or `scmfig.h') is tried. Unless the option `-no-init-file' or `--no-init-file' occurs in the -command line, `Init5e1.scm' checks to see if there is file | +command line, `Init5e2.scm' checks to see if there is file | `ScmInit.scm' in the path specified by the environment variable HOME (or in the current directory if HOME is undefined). If it finds such a file it is loaded. -`Init5e1.scm' then looks for command input from one of three sources: | +`Init5e2.scm' then looks for command input from one of three sources: | From an option on the command line, from a file named on the command line, or from standard input. @@ -1352,55 +1355,55 @@ Lexical Conventions.  File: scm.info, Node: SCM Options, Next: Invocation Examples, Prev: Invoking SCM, Up: Operational Features -3.2 Options | -=========== | +3.2 Options +=========== The options are processed in the order specified on the command line. - -- Command Option: -a k | + -- Command Option: -a k specifies that `scm' should allocate an initial heapsize of K kilobytes. This option, if present, must be the first on the command line. If not specified, the default is `INIT_HEAP_SIZE' in source file `setjump.h' which the distribution sets at `25000*sizeof(cell)'. - -- Command Option: -no-init-file | - -- Command Option: --no-init-file | + -- Command Option: -no-init-file + -- Command Option: --no-init-file Inhibits the loading of `ScmInit.scm' as described above. - -- Command Option: --help | + -- Command Option: --help prints usage information and URI; then exit. - -- Command Option: --version | + -- Command Option: --version prints version information and exit. - -- Command Option: -r feature | + -- Command Option: -r feature requires FEATURE. This will load a file from [SLIB] if that - FEATURE is not already provided. If FEATURE is 2, 2rs, or r2rs; | - 3, 3rs, or r3rs; 4, 4rs, or r4rs; 5, 5rs, or r5rs; `scm' will | - require the features neccessary to support [R2RS]; [R3RS]; [R4RS]; | - or [R5RS], respectively. | + FEATURE is not already provided. If FEATURE is 2, 2rs, or r2rs; + 3, 3rs, or r3rs; 4, 4rs, or r4rs; 5, 5rs, or r5rs; `scm' will + require the features neccessary to support [R2RS]; [R3RS]; [R4RS]; + or [R5RS], respectively. - -- Command Option: -h feature | + -- Command Option: -h feature provides FEATURE. - -- Command Option: -l filename | - -- Command Option: -f filename | + -- Command Option: -l filename + -- Command Option: -f filename loads FILENAME. `Scm' will load the first (unoptioned) file named on the command line if no `-c', `-e', `-f', `-l', or `-s' option preceeds it. - -- Command Option: -d filename | + -- Command Option: -d filename Loads SLIB `databases' feature and opens FILENAME as a database. - -- Command Option: -e expression | - -- Command Option: -c expression | + -- Command Option: -e expression + -- Command Option: -c expression specifies that the scheme expression EXPRESSION is to be evaluated. These options are inspired by `perl' and `sh' respectively. On Amiga systems the entire option and argument need to be enclosed in quotes. For instance `"-e(newline)"'. - -- Command Option: -o dumpname | + -- Command Option: -o dumpname saves the current SCM session as the executable program `dumpname'. This option works only in SCM builds supporting `dump' (*note Dump::). @@ -1410,33 +1413,33 @@ The options are processed in the order specified on the command line. it is invoked. Otherwise the (new) command line is processed as usual when the saved image is invoked. - -- Command Option: -p level | + -- Command Option: -p level sets the prolixity (verboseness) to LEVEL. This is the same as the `scm' command (verobse LEVEL). - -- Command Option: -v | + -- Command Option: -v (verbose mode) specifies that `scm' will print prompts, evaluation times, notice of loading files, and garbage collection statistics. This is the same as `-p3'. - -- Command Option: -q | + -- Command Option: -q (quiet mode) specifies that `scm' will print no extra information. This is the same as `-p0'. - -- Command Option: -m | + -- Command Option: -m specifies that subsequent loads, evaluations, and user interactions will be with syntax-rules macro capability. To use a specific syntax-rules macro implementation from [SLIB] (instead of [SLIB]'s default) put `-r' MACROPACKAGE before `-m' on the command line. - -- Command Option: -u | + -- Command Option: -u specifies that subsequent loads, evaluations, and user interactions will be without syntax-rules macro capability. Syntax-rules macro capability can be restored by a subsequent `-m' on the command line or from Scheme code. - -- Command Option: -i | + -- Command Option: -i specifies that `scm' should run interactively. That means that `scm' will not terminate until the `(quit)' or `(exit)' command is given, even if there are errors. It also sets the prolixity level @@ -1446,26 +1449,26 @@ The options are processed in the order specified on the command line. will assume that it should be interactive unless given a subsequent `-b' option. - -- Command Option: -b | + -- Command Option: -b specifies that `scm' should run non-interactively. That means that `scm' will terminate after processing the command line or if there are errors. - -- Command Option: -s | + -- Command Option: -s specifies, by analogy with `sh', that `scm' should run interactively and that further options are to be treated as program aguments. - -- Command Option: - | - -- Command Option: -- | + -- Command Option: - + -- Command Option: -- specifies that further options are to be treated as program aguments.  File: scm.info, Node: Invocation Examples, Next: SCM Variables, Prev: SCM Options, Up: Operational Features -3.3 Invocation Examples | -======================= | +3.3 Invocation Examples +======================= `% scm foo.scm' Loads and executes the contents of `foo.scm' and then enters @@ -1496,39 +1499,39 @@ File: scm.info, Node: Invocation Examples, Next: SCM Variables, Prev: SCM Opt  File: scm.info, Node: SCM Variables, Next: SCM Session, Prev: Invocation Examples, Up: Operational Features -3.4 Environment Variables | -========================= | +3.4 Environment Variables +========================= - -- Environment Variable: SCM_INIT_PATH | + -- Environment Variable: SCM_INIT_PATH is the pathname where `scm' will look for its initialization code. - The default is the file `Init5e1.scm' in the source directory. | + The default is the file `Init5e2.scm' in the source directory. | - -- Environment Variable: SCHEME_LIBRARY_PATH | + -- Environment Variable: SCHEME_LIBRARY_PATH is the [SLIB] Scheme library directory. - -- Environment Variable: HOME | - is the directory where `Init5e1.scm' will look for the user | + -- Environment Variable: HOME + is the directory where `Init5e2.scm' will look for the user | initialization file `ScmInit.scm'. - -- Environment Variable: EDITOR | + -- Environment Variable: EDITOR is the name of the program which `ed' will call. If EDITOR is not defined, the default is `ed'. -3.5 Scheme Variables | -==================== | +3.5 Scheme Variables +==================== - -- Variable: *argv* | + -- Variable: *argv* contains the list of arguments to the program. `*argv*' can change during argument processing. This list is suitable for use as an argument to [SLIB] `getopt'. - -- Variable: *syntax-rules* | + -- Variable: *syntax-rules* controls whether loading and interaction support syntax-rules macros. Define this in `ScmInit.scm' or files specified on the command line. This can be overridden by subsequent `-m' and `-u' options. - -- Variable: *interactive* | + -- Variable: *interactive* controls interactivity as explained for the `-i' and `-b' options. Define this in `ScmInit.scm' or files specified on the command line. This can be overridden by subsequent `-i' and `-b' options. @@ -1536,8 +1539,8 @@ File: scm.info, Node: SCM Variables, Next: SCM Session, Prev: Invocation Exam  File: scm.info, Node: SCM Session, Next: Editing Scheme Code, Prev: SCM Variables, Up: Operational Features -3.6 SCM Session | -=============== | +3.6 SCM Session +=============== * Options, file loading and features can be specified from the command line. *Note System interface: (scm)System interface. @@ -1549,23 +1552,23 @@ File: scm.info, Node: SCM Session, Next: Editing Scheme Code, Prev: SCM Varia * Typing the interrupt character aborts evaluation of the current form and resumes the top level read-eval-print loop. - -- Function: quit | - -- Function: quit n | - -- Function: exit | - -- Function: exit n | + -- Function: quit + -- Function: quit n + -- Function: exit + -- Function: exit n Aliases for `exit' (*note exit: (slib)System.). On many systems, SCM can also tail-call another program. *Note execp: I/O-Extensions. - -- Callback procedure: boot-tail dumped? | + -- Callback procedure: boot-tail dumped? `boot-tail' is called by `scm_top_level' just before entering interactive top-level. If `boot-tail' calls `quit', then interactive top-level is not entered. - -- Function: program-arguments | + -- Function: program-arguments Returns a list of strings of the arguments scm was called with. - -- Function: getlogin | + -- Function: getlogin Returns the (login) name of the user logged in on the controlling terminal of the process, or #f if this information cannot be determined. @@ -1573,31 +1576,31 @@ File: scm.info, Node: SCM Session, Next: Editing Scheme Code, Prev: SCM Varia For documentation of the procedures `getenv' and `system' *Note System Interface: (slib)System Interface. - -- Function: vms-debug | + -- Function: vms-debug If SCM is compiled under VMS this `vms-debug' will invoke the VMS debugger.  File: scm.info, Node: Editing Scheme Code, Next: Debugging Scheme Code, Prev: SCM Session, Up: Operational Features -3.7 Editing Scheme Code | -======================= | +3.7 Editing Scheme Code +======================= - -- Function: ed arg1 ... | + -- Function: ed arg1 ... The value of the environment variable `EDITOR' (or just `ed' if it isn't defined) is invoked as a command with arguments ARG1 .... - -- Function: ed filename | + -- Function: ed filename If SCM is compiled under VMS `ed' will invoke the editor with a single the single argument FILENAME. Gnu Emacs: Editing of Scheme code is supported by emacs. Buffers holding - files ending in .scm are automatically put into scheme-mode. | + files ending in .scm are automatically put into scheme-mode. - If your Emacs can run a process in a buffer you can use the Emacs | - command `M-x run-scheme' with SCM. Otherwise, use the emacs | - command `M-x suspend-emacs'; or see "other systems" below. | + If your Emacs can run a process in a buffer you can use the Emacs + command `M-x run-scheme' with SCM. Otherwise, use the emacs + command `M-x suspend-emacs'; or see "other systems" below. Epsilon (MS-DOS): There is lisp (and scheme) mode available by use of the package @@ -1627,9 +1630,9 @@ other systems:  File: scm.info, Node: Debugging Scheme Code, Next: Debugging Continuations, Prev: Editing Scheme Code, Up: Operational Features - | -3.8 Debugging Scheme Code | -========================= | + +3.8 Debugging Scheme Code +========================= The `cautious' and `stack-limit' options of `build' (*note Build Options::) support debugging in Scheme. @@ -1665,53 +1668,53 @@ Options::) support debugging in Scheme. There are several SLIB macros which so useful that SCM automatically loads the appropriate module from SLIB if they are invoked. - -- Macro: trace proc1 ... | + -- Macro: trace proc1 ... Traces the top-level named procedures given as arguments. - -- Macro: trace | + -- Macro: trace With no arguments, makes sure that all the currently traced identifiers are traced (even if those identifiers have been redefined) and returns a list of the traced identifiers. - -- Macro: untrace proc1 ... | + -- Macro: untrace proc1 ... Turns tracing off for its arguments. - -- Macro: untrace | + -- Macro: untrace With no arguments, untraces all currently traced identifiers and returns a list of these formerly traced identifiers. The routines I use most frequently for debugging are: - -- Function: print arg1 ... | + -- Function: print arg1 ... `Print' writes all its arguments, separated by spaces. `Print' outputs a `newline' at the end and returns the value of the last argument. - One can just insert `(print '