[Contents] [Back] [Prev] [Up] [Next] [Forward]
More people than I can name have contributed to SLIB. Thanks to all of
you!
SLIB 3b1, released February 2008.
Aubrey Jaffer <agj @ alum.mit.edu>
Current information about SLIB can be found on SLIB's WWW home
page:
http://swiss.csail.mit.edu/~jaffer/SLIB
SLIB is part of the GNU project.
There are five parts to installation:
-
Unpack the SLIB distribution.
-
Install documentation and
slib script.
-
Configure the Scheme implementation(s) to locate the SLIB directory
and implementation directories.
-
Arrange for Scheme implementation to load its SLIB initialization file.
-
Build the SLIB catalog for the Scheme implementation.
If the SLIB distribution is a GNU/Linux RPM, it will create the SLIB
directory `/usr/share/slib'.
If the SLIB distribution is a ZIP file, unzip the distribution to create
the SLIB directory. Locate this `slib' directory either in your
home directory (if only you will use this SLIB installation); or put it
in a location where libraries reside on your system. On unix systems
this might be `/usr/share/slib', `/usr/local/lib/slib', or
`/usr/lib/slib'. If you know where SLIB should go on other
platforms, please inform agj @ alum.mit.edu.
make infoz
make install
If the Scheme implementation supports getenv, then the value of
the shell environment variable SCHEME_LIBRARY_PATH will be used
for (library-vicinity) if it is defined. Currently, Bigloo,
Chez, Elk, Gambit, Guile, Jscheme, Larceny, MITScheme, MzScheme,
RScheme, STk, VSCM, and SCM support getenv. Scheme48 supports
getenv but does not use it for determining
library-vicinity. (That is done from the Makefile.)
The (library-vicinity) can also be set from the SLIB
initialization file or by implementation-specific means.
Support for locating an implementation's auxiliary directory is uneven
among implementations. Also, the person installing SLIB may not have
write permission to some of these directories (necessary for writing
slibcat). Therefore, those implementations supporting getenv
(except SCM and Scheme48) provide a means for specifying the
implementation-vicinity through environment variables. Define
the indicated environment variable to the pathname (with trailing
slash or backslash) of the desired directory. Do not use `slib/'
as an implementation-vicinity!
| Bigloo | BIGLOO_IMPLEMENTATION_PATH |
| Chez | CHEZ_IMPLEMENTATION_PATH |
| ELK | ELK_IMPLEMENTATION_PATH |
| Gambit | GAMBIT_IMPLEMENTATION_PATH |
| Guile | GUILE_IMPLEMENTATION_PATH |
| Jscheme | JSCHEME_IMPLEMENTATION_PATH |
| MIT-Scheme | MITSCHEME_IMPLEMENTATION_PATH |
| MzScheme | MZSCHEME_IMPLEMENTATION_PATH |
| RScheme | RSCHEME_IMPLEMENTATION_PATH |
| STk | STK_IMPLEMENTATION_PATH |
| Vscm | VSCM_IMPLEMENTATION_PATH |
Check the manifest in `README' to find a configuration file for
your Scheme implementation. Initialization files for most IEEE P1178
compliant Scheme Implementations are included with this distribution.
You should check the definitions of software-type,
scheme-implementation-version,
implementation-vicinity,
and library-vicinity in the initialization file. There are
comments in the file for how to configure it.
Once this is done, modify the startup file for your Scheme
implementation to load this initialization file.
When SLIB is first used from an implementation, a file named
`slibcat' is written to the implementation-vicinity for that
implementation. Because users may lack permission to write in
implementation-vicinity, it is good practice to build the new
catalog when installing SLIB.
To build (or rebuild) the catalog, start the Scheme implementation (with
SLIB), then:
(require 'new-catalog)
The catalog also supports color-name dictionaries. With an
SLIB-installed scheme implementation, type:
(require 'color-names)
(make-slib-color-name-db)
(require 'new-catalog)
(slib:exit)
Multiple implementations of Scheme can all use the same SLIB directory.
Simply configure each implementation's initialization file as outlined
above.
- Implementation: SCM
-
The SCM implementation does not require any initialization file as SLIB
support is already built into SCM. See the documentation with SCM for
installation instructions.
- Implementation: Larceny
-
Starting with version 0.96, Larceny contains its own SLIB
initialization file, loaded by
(require 'srfi-96). If
SCHEME_LIBRARY_PATH is not set, then Larceny looks for an `slib'
subdirectory of a directory in the list returned by
(current-require-path)
larceny -- -e "(require 'srfi-96)"
- Implementation: ELK
-
elk -i -l ${SCHEME_LIBRARY_PATH}elk.init
- Implementation: PLT Scheme
-
- Implementation: DrScheme
-
- Implementation: MzScheme
-
The `init.ss' file in the _slibinit_ collection is an SLIB
initialization file. To run SLIB in MzScheme:
mzscheme -f ${SCHEME_LIBRARY_PATH}mzscheme.init
- Implementation: MIT Scheme
-
scheme -load ${SCHEME_LIBRARY_PATH}mitscheme.init
- Implementation: Gambit-C 3.0
-
gsi -:s ${SCHEME_LIBRARY_PATH}gambit.init -
- Implementation: SISC
-
sisc -e "(load \"${SCHEME_LIBRARY_PATH}sisc.init\")" --
- Implementation: Kawa
-
kawa -f ${SCHEME_LIBRARY_PATH}kawa.init --
- Implementation: Guile
-
Guile versions 1.6 and earlier link to an archaic SLIB version. In
RedHat or Fedora installations:
rm /usr/share/guile/slib
ln -s ${SCHEME_LIBRARY_PATH} /usr/share/guile/slib
In Debian installations:
rm /usr/share/guile/1.6/slib
ln -s ${SCHEME_LIBRARY_PATH} /usr/share/guile/1.6/slib
${SCHEME_LIBRARY_PATH} is where SLIB gets installed.
Guile with SLIB can then be started thus:
guile -l ${SCHEME_LIBRARY_PATH}guile.init
- Implementation: Scheme48
-
To make a Scheme48 image for an installation under
<prefix>,
-
cd to the SLIB directory
-
type
make prefix=<prefix> slib48.
-
To install the image, type
make prefix=<prefix> install48. This
will also create a shell script with the name slib48 which will
invoke the saved image.
- Implementation: VSCM
-
From: Matthias Blume <blume @ cs.Princeton.EDU>
Date: Tue, 1 Mar 1994 11:42:31 -0500
Disclaimer: The code below is only a quick hack. If I find some time
to spare I might get around to make some more things work.
You have to provide `vscm.init' as an explicit command line
argument. Since this is not very nice I would recommend the following
installation procedure:
-
run scheme
-
(load "vscm.init")
-
(slib:dump "dumpfile")
-
mv dumpfile place-where-vscm-standard-bootfile-resides. For example:
mv dumpfile /usr/local/vscm/lib/scheme-boot
In this case vscm should have been compiled with flag:
-DDEFAULT_BOOTFILE='"/usr/local/vscm/lib/scheme-boot"'
See Makefile (definition of DDP) for details.
SLIB comes with shell script for Unix platforms.
slib [ scheme | scm | gsi | mzscheme | guile
| scheme48 | scmlit | elk | sisc | kawa ]
Starts an interactive Scheme-with-SLIB session.
The optional argument to the slib script is the Scheme
implementation to run. Absent the argument, it searches for
implementations in the above order.
If there is no initialization file for your Scheme implementation, you
will have to create one. Your Scheme implementation must be largely
compliant with
IEEE Std 1178-1990,
Revised^4 Report on the Algorithmic Language Scheme, or
Revised^5 Report on the Algorithmic Language Scheme
in order to support SLIB. (8)
`Template.scm' is an example configuration file. The comments
inside will direct you on how to customize it to reflect your system.
Give your new initialization file the implementation's name with
`.init' appended. For instance, if you were porting
foo-scheme then the initialization file might be called
`foo.init'.
Your customized version should then be loaded as part of your scheme
implementation's initialization. It will load `require.scm' from
the library; this will allow the use of provide,
provided?, and require along with the vicinity
functions (these functions are documented in the sections
section Feature and section Require). The rest of the library will then
be accessible in a system independent fashion.
Please mail new working configuration files to agj @ alum.mit.edu
so that they can be included in the SLIB distribution.
All library packages are written in IEEE P1178 Scheme and assume that a
configuration file and `require.scm' package have already been
loaded. Other versions of Scheme can be supported in library packages
as well by using, for example, (provided? 'r3rs) or
(require 'r3rs) (see section Require).
If a procedure defined in a module is called by other procedures in
that module, then those procedures should instead call an alias
defined in that module:
(define module-name:foo foo)
The module name and `:' should prefix that symbol for the
internal name. Do not export internal aliases.
A procedure is exported from a module by putting Schmooz-style
comments (see section Schmooz) or `;@' at the beginning of the line
immediately preceding the definition (define,
define-syntax, or defmacro). Modules, exports and other
relevant issues are discussed in section Compiling Scheme.
Code submitted for inclusion in SLIB should not duplicate (more than
one) routines already in SLIB files. Use require to force
those library routines to be used by your package.
Documentation should be provided in Emacs Texinfo format if possible,
but documentation must be provided.
Your package will be released sooner with SLIB if you send me a file
which tests your code. Please run this test before you send me
the code!
Please document your changes. A line or two for `ChangeLog' is
sufficient for simple fixes or extensions. Look at the format of
`ChangeLog' to see what information is desired. Please send me
diff files from the latest SLIB distribution (remember to send
diffs of `slib.texi' and `ChangeLog'). This makes for
less email traffic and makes it easier for me to integrate when more
than one person is changing a file (this happens a lot with
`slib.texi' and `*.init' files).
If someone else wrote a package you want to significantly modify, please
try to contact the author, who may be working on a new version. This
will insure against wasting effort on obsolete versions.
Please do not reformat the source code with your favorite
beautifier, make 10 fixes, and send me the resulting source code. I do
not have the time to fish through 10000 diffs to find your 10 real fixes.
This section has instructions for SLIB authors regarding copyrights.
Each package in SLIB must either be in the public domain, or come with a
statement of terms permitting users to copy, redistribute and modify it.
The comments at the beginning of `require.scm' and
`macwork.scm' illustrate copyright and appropriate terms.
If your code or changes amount to less than about 10 lines, you do not
need to add your copyright or send a disclaimer.
In order to put code in the public domain you should sign a copyright
disclaimer and send it to the SLIB maintainer. Contact
agj @ alum.mit.edu for the address to mail the disclaimer to.
I, <my-name>, hereby affirm that I have placed the software
package <name> in the public domain.
I affirm that I am the sole author and sole copyright holder for the
software package, that I have the right to place this software package
in the public domain, and that I will do nothing to undermine this
status in the future.
signature and date
This wording assumes that you are the sole author. If you are not the
sole author, the wording needs to be different. If you don't want to
be bothered with sending a letter every time you release or modify a
module, make your letter say that it also applies to your future
revisions of that module.
Make sure no employer has any claim to the copyright on the work you
are submitting. If there is any doubt, create a copyright disclaimer
and have your employer sign it. Mail the signed disclaimer to the
SLIB maintainer. Contact agj @ alum.mit.edu for the address to mail
the disclaimer to. An example disclaimer follows.
If you submit more than about 10 lines of code which you are not
placing into the Public Domain (by sending me a disclaimer) you need
to:
-
Arrange that your name appears in a copyright line for the appropriate
year. Multiple copyright lines are acceptable.
-
With your copyright line, specify any terms you require to be
different from those already in the file.
-
Make sure no employer has any claim to the copyright on the work you
are submitting. If there is any doubt, create a copyright disclaimer
and have your employer sign it. Mail the signed disclaim to the SLIB
maintainer. Contact agj @ alum.mit.edu for the address to mail the
disclaimer to.
This disclaimer should be signed by a vice president or general
manager of the company. If you can't get at them, anyone else
authorized to license out software produced there will do. Here is a
sample wording:
<employer> Corporation hereby disclaims all copyright
interest in the program <program> written by <name>.
<employer> Corporation affirms that it has no other intellectual
property interest that would undermine this release, and will do
nothing to undermine it in the future.
<signature and date>,
<name>, <title>, <employer> Corporation
-
Entries that are labeled as Functions are called for their return
values. Entries that are labeled as Procedures are called primarily for
their side effects.
-
Examples in this text were produced using the
scm Scheme
implementation.
-
At the beginning of each section, there is a line that looks like:
(require 'feature)
Include this line in your code prior to using the package.
Version 1.2, November 2002
Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
-
PREAMBLE
The purpose of this License is to make a manual, textbook, or other
functional and useful document free in the sense of freedom: to
assure everyone the effective freedom to copy and redistribute it,
with or without modifying it, either commercially or noncommercially.
Secondarily, this License preserves for the author and publisher a way
to get credit for their work, while not being considered responsible
for modifications made by others.
This License is a kind of "copyleft", which means that derivative
works of the document must themselves be free in the same sense. It
complements the GNU General Public License, which is a copyleft
license designed for free software.
We have designed this License in order to use it for manuals for free
software, because free software needs free documentation: a free
program should come with manuals providing the same freedoms that the
software does. But this License is not limited to software manuals;
it can be used for any textual work, regardless of subject matter or
whether it is published as a printed book. We recommend this License
principally for works whose purpose is instruction or reference.
-
APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. Such a notice grants a
world-wide, royalty-free license, unlimited in duration, to use that
work under the conditions stated herein. The "Document", below,
refers to any such manual or work. Any member of the public is a
licensee, and is addressed as "you". You accept the license if you
copy, modify or distribute the work in a way requiring permission
under copyright law.
A "Modified Version" of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section
of the Document that deals exclusively with the relationship of the
publishers or authors of the Document to the Document's overall
subject (or to related matters) and contains nothing that could fall
directly within that overall subject. (Thus, if the Document is in
part a textbook of mathematics, a Secondary Section may not explain
any mathematics.) The relationship could be a matter of historical
connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding
them.
The "Invariant Sections" are certain Secondary Sections whose titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License. If a
section does not fit the above definition of Secondary then it is not
allowed to be designated as Invariant. The Document may contain zero
Invariant Sections. If the Document does not identify any Invariant
Sections then there are none.
The "Cover Texts" are certain short passages of text that are listed,
as Front-Cover Texts or Back-Cover Texts, in the notice that says that
the Document is released under this License. A Front-Cover Text may
be at most 5 words, and a Back-Cover Text may be at most 25 words.
A "Transparent" copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed of
pixels) generic paint programs or (for drawings) some widely available
drawing editor, and that is suitable for input to text formatters or
for automatic translation to a variety of formats suitable for input
to text formatters. A copy made in an otherwise Transparent file
format whose markup, or absence of markup, has been arranged to thwart
or discourage subsequent modification by readers is not Transparent.
An image format is not Transparent if used for any substantial amount
of text. A copy that is not "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input
format, @acronym{SGML} or @acronym{XML} using a publicly available
@acronym{DTD}, and standard-conforming simple @acronym{HTML},
PostScript or @acronym{PDF} designed for human modification. Examples
of transparent image formats include @acronym{PNG}, @acronym{XCF} and
@acronym{JPG}. Opaque formats include proprietary formats that can be
read and edited only by proprietary word processors, @acronym{SGML} or
@acronym{XML} for which the @acronym{DTD} and/or processing tools are
not generally available, and the machine-generated @acronym{HTML},
PostScript or @acronym{PDF} produced by some word processors for
output purposes only.
The "Title Page" means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the material
this License requires to appear in the title page. For works in
formats which do not have any title page as such, "Title Page" means
the text near the most prominent appearance of the work's title,
preceding the beginning of the body of the text.
A section "Entitled XYZ" means a named subunit of the Document whose
title either is precisely XYZ or contains XYZ in parentheses following
text that translates XYZ in another language. (Here XYZ stands for a
specific section name mentioned below, such as "Acknowledgements",
"Dedications", "Endorsements", or "History".) To "Preserve the Title"
of such a section when you modify the Document means that it remains a
section "Entitled XYZ" according to this definition.
The Document may include Warranty Disclaimers next to the notice which
states that this License applies to the Document. These Warranty
Disclaimers are considered to be included by reference in this
License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.
-
VERBATIM COPYING
You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License applies
to the Document are reproduced in all copies, and that you add no other
conditions whatsoever to those of this License. You may not use
technical measures to obstruct or control the reading or further
copying of the copies you make or distribute. However, you may accept
compensation in exchange for copies. If you distribute a large enough
number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
-
COPYING IN QUANTITY
If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
Document's license notice requires Cover Texts, you must enclose the
copies in covers that carry, clearly and legibly, all these Cover
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
the back cover. Both covers must also clearly and legibly identify
you as the publisher of these copies. The front cover must present
the full title with all words of the title equally prominent and
visible. You may add other material on the covers in addition.
Copying with changes limited to the covers, as long as they preserve
the title of the Document and satisfy these conditions, can be treated
as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto adjacent
pages.
If you publish or distribute Opaque copies of the Document numbering
more than 100, you must either include a machine-readable Transparent
copy along with each Opaque copy, or state in or with each Opaque copy
a computer-network location from which the general network-using
public has access to download using public-standard network protocols
a complete Transparent copy of the Document, free of added material.
If you use the latter option, you must take reasonably prudent steps,
when you begin distribution of Opaque copies in quantity, to ensure
that this Transparent copy will remain thus accessible at the stated
location until at least one year after the last time you distribute an
Opaque copy (directly or through your agents or retailers) of that
edition to the public.
It is requested, but not required, that you contact the authors of the
Document well before redistributing any large number of copies, to give
them a chance to provide you with an updated version of the Document.
-
MODIFICATIONS
You may copy and distribute a Modified Version of the Document under
the conditions of sections 2 and 3 above, provided that you release
the Modified Version under precisely this License, with the Modified
Version filling the role of the Document, thus licensing distribution
and modification of the Modified Version to whoever possesses a copy
of it. In addition, you must do these things in the Modified Version:
-
Use in the Title Page (and on the covers, if any) a title distinct
from that of the Document, and from those of previous versions
(which should, if there were any, be listed in the History section
of the Document). You may use the same title as a previous version
if the original publisher of that version gives permission.
-
List on the Title Page, as authors, one or more persons or entities
responsible for authorship of the modifications in the Modified
Version, together with at least five of the principal authors of the
Document (all of its principal authors, if it has fewer than five),
unless they release you from this requirement.
-
State on the Title page the name of the publisher of the
Modified Version, as the publisher.
-
Preserve all the copyright notices of the Document.
-
Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
-
Include, immediately after the copyright notices, a license notice
giving the public permission to use the Modified Version under the
terms of this License, in the form shown in the Addendum below.
-
Preserve in that license notice the full lists of Invariant Sections
and required Cover Texts given in the Document's license notice.
-
Include an unaltered copy of this License.
-
Preserve the section Entitled "History", Preserve its Title, and add
to it an item stating at least the title, year, new authors, and
publisher of the Modified Version as given on the Title Page. If
there is no section Entitled "History" in the Document, create one
stating the title, year, authors, and publisher of the Document as
given on its Title Page, then add an item describing the Modified
Version as stated in the previous sentence.
-
Preserve the network location, if any, given in the Document for
public access to a Transparent copy of the Document, and likewise
the network locations given in the Document for previous versions
it was based on. These may be placed in the "History" section.
You may omit a network location for a work that was published at
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.
-
For any section Entitled "Acknowledgements" or "Dedications", Preserve
the Title of the section, and preserve in the section all the
substance and tone of each of the contributor acknowledgements and/or
dedications given therein.
-
Preserve all the Invariant Sections of the Document,
unaltered in their text and in their titles. Section numbers
or the equivalent are not considered part of the section titles.
-
Delete any section Entitled "Endorsements". Such a section
may not be included in the Modified Version.
-
Do not retitle any existing section to be Entitled "Endorsements" or
to conflict in title with any Invariant Section.
-
Preserve any Warranty Disclaimers.
If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no material
copied from the Document, you may at your option designate some or all
of these sections as invariant. To do this, add their titles to the
list of Invariant Sections in the Modified Version's license notice.
These titles must be distinct from any other section titles.
You may add a section Entitled "Endorsements", provided it contains
nothing but endorsements of your Modified Version by various
parties--for example, statements of peer review or that the text has
been approved by an organization as the authoritative definition of a
standard.
You may add a passage of up to five words as a Front-Cover Text, and a
passage of up to 25 words as a Back-Cover Text, to the end of the list
of Cover Texts in the Modified Version. Only one passage of
Front-Cover Text and one of Back-Cover Text may be added by (or
through arrangements made by) any one entity. If the Document already
includes a cover text for the same cover, previously added by you or
by arrangement made by the same entity you are acting on behalf of,
you may not add another; but you may replace the old one, on explicit
permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.
-
COMBINING DOCUMENTS
You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
versions, provided that you include in the combination all of the
Invariant Sections of all of the original documents, unmodified, and
list them all as Invariant Sections of your combined work in its
license notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and
multiple identical Invariant Sections may be replaced with a single
copy. If there are multiple Invariant Sections with the same name but
different contents, make the title of each such section unique by
adding at the end of it, in parentheses, the name of the original
author or publisher of that section if known, or else a unique number.
Make the same adjustment to the section titles in the list of
Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled "History"
in the various original documents, forming one section Entitled
"History"; likewise combine any sections Entitled "Acknowledgements",
and any sections Entitled "Dedications". You must delete all
sections Entitled "Endorsements."
-
COLLECTIONS OF DOCUMENTS
You may make a collection consisting of the Document and other documents
released under this License, and replace the individual copies of this
License in the various documents with a single copy that is included in
the collection, provided that you follow the rules of this License for
verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute
it individually under this License, provided you insert a copy of this
License into the extracted document, and follow this License in all
other respects regarding verbatim copying of that document.
-
AGGREGATION WITH INDEPENDENT WORKS
A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
distribution medium, is called an "aggregate" if the copyright
resulting from the compilation is not used to limit the legal rights
of the compilation's users beyond what the individual works permit.
When the Document is included in an aggregate, this License does not
apply to the other works in the aggregate which are not themselves
derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half of
the entire aggregate, the Document's Cover Texts may be placed on
covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic form.
Otherwise they must appear on printed covers that bracket the whole
aggregate.
-
TRANSLATION
Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
Replacing Invariant Sections with translations requires special
permission from their copyright holders, but you may include
translations of some or all Invariant Sections in addition to the
original versions of these Invariant Sections. You may include a
translation of this License, and all the license notices in the
Document, and any Warranty Disclaimers, provided that you also include
the original English version of this License and the original versions
of those notices and disclaimers. In case of a disagreement between
the translation and the original version of this License or a notice
or disclaimer, the original version will prevail.
If a section in the Document is Entitled "Acknowledgements",
"Dedications", or "History", the requirement (section 4) to Preserve
its Title (section 1) will typically require changing the actual
title.
-
TERMINATION
You may not copy, modify, sublicense, or distribute the Document except
as expressly provided for under this License. Any other attempt to
copy, modify, sublicense or distribute the Document is void, and will
automatically terminate your rights under this License. However,
parties who have received copies, or rights, from you under this
License will not have their licenses terminated so long as such
parties remain in full compliance.
-
FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions
of the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
http://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
License "or any later version" applies to it, you have the option of
following the terms and conditions either of that specified version or
of any later version that has been published (not as a draft) by the
Free Software Foundation. If the Document does not specify a version
number of this License, you may choose any version ever published (not
as a draft) by the Free Software Foundation.
ADDENDUM: How to use this License for your documents
To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and
license notices just after the title page:
Copyright (C) year your name.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts. A copy of the license is included in the section entitled ``GNU
Free Documentation License''.
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
replace the "with...Texts." line with this:
with the Invariant Sections being list their titles, with
the Front-Cover Texts being list, and with the Back-Cover Texts
being list.
If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.
If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of
free software license, such as the GNU General Public License,
to permit their use in free software.
@node Index, Procedure and Macro Index, About SLIB, Top
@unnumbered Index
@ifnotinfo
@ifnotinfo
[Contents] [Back] [Prev] [Up] [Next] [Forward]
Words changed since last version are marked in red by
HITCH.