/usr/share/doc/slib/slib_8.html is in slib 3b1-3.1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html401/loose.dtd">
<html>
<!-- This manual is for SLIB (version 3b1, June 2010),
the portable Scheme library.
Copyright C 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001,
2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
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."
-->
<!-- Created on June 9, 2010 by texi2html 1.82
texi2html was written by:
Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
Olaf Bachmann <obachman@mathematik.uni-kl.de>
and many others.
Maintained by: Many creative people.
Send bugs and suggestions to <texi2html-bug@nongnu.org>
-->
<head>
<title>slib: 8. About SLIB</title>
<meta name="description" content="slib: 8. About SLIB">
<meta name="keywords" content="slib: 8. About SLIB">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="texi2html 1.82">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.smallquotation {font-size: smaller}
pre.display {font-family: serif}
pre.format {font-family: serif}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: serif; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: serif; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.roman {font-family:serif; font-weight:normal;}
span.sansserif {font-family:sans-serif; font-weight:normal;}
ul.toc {list-style: none}
-->
</style>
</head>
<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
<a name="About-SLIB"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="slib_7.html#Extra_002dSLIB-Packages" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Installation" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib_7.html#Other-Packages" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="About-SLIB-1"></a>
<h1 class="chapter">8. About SLIB</h1>
<p>More people than I can name have contributed to SLIB. Thanks to all of
you!
</p>
<blockquote><p>SLIB 3b1, released June 2010.<br>
Aubrey Jaffer <agj @ alum.mit.edu><br>
</p></blockquote>
<p>Current information about SLIB can be found on SLIB’s <em>WWW</em> home
page:
</p>
<p align="center"> <a href="http://swiss.csail.mit.edu/~jaffer/SLIB">http://swiss.csail.mit.edu/~jaffer/SLIB</a>
</p>
<p>SLIB is part of the GNU project.
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top"><a href="#Installation">8.1 Installation</a></td><td> </td><td align="left" valign="top"> How to install SLIB on your system.
</td></tr>
<tr><td align="left" valign="top"><a href="#The-SLIB-script">8.2 The SLIB script</a></td><td> </td><td align="left" valign="top"> Run interactive SLIB sessions.
</td></tr>
<tr><td align="left" valign="top"><a href="#Porting">8.3 Porting</a></td><td> </td><td align="left" valign="top"> SLIB to new platforms.
</td></tr>
<tr><td align="left" valign="top"><a href="#Coding-Guidelines">8.4 Coding Guidelines</a></td><td> </td><td align="left" valign="top"> How to write modules for SLIB.
</td></tr>
<tr><td align="left" valign="top"><a href="#Copyrights">8.5 Copyrights</a></td><td> </td><td align="left" valign="top"> Intellectual propery issues.
</td></tr>
<tr><td align="left" valign="top"><a href="#About-this-manual">8.6 About this manual</a></td><td> </td><td align="left" valign="top">
</td></tr>
</table>
<hr size="6">
<a name="Installation"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#About-SLIB" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Unpacking-the-SLIB-Distribution" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="Installation-1"></a>
<h2 class="section">8.1 Installation</h2>
<p><A NAME="Installation"></A>
</p>
<a name="index-install"></a>
<a name="index-installation"></a>
<p>There are five parts to installation:
</p>
<ul>
<li>
Unpack the SLIB distribution.
</li><li>
Install documentation and <code>slib</code> script.
</li><li>
Configure the Scheme implementation(s) to locate the SLIB directory
and implementation directories.
</li><li>
Arrange for Scheme implementation to load its SLIB initialization file.
</li><li>
Build the SLIB catalog for the Scheme implementation.
</li></ul>
<hr size="6">
<a name="Unpacking-the-SLIB-Distribution"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#Installation" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Install-documentation-and-slib-script" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Installation" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">8.1.1 Unpacking the SLIB Distribution</h3>
<p>If the SLIB distribution is a GNU/Linux RPM, it will create the SLIB
directory ‘<tt>/usr/share/slib</tt>’.
</p>
<p>If the SLIB distribution is a ZIP file, unzip the distribution to create
the SLIB directory. Locate this ‘<tt>slib</tt>’ 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 ‘<tt>/usr/share/slib</tt>’, ‘<tt>/usr/local/lib/slib</tt>’, or
‘<tt>/usr/lib/slib</tt>’. If you know where SLIB should go on other
platforms, please inform agj @ alum.mit.edu.
</p>
<hr size="6">
<a name="Install-documentation-and-slib-script"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#Unpacking-the-SLIB-Distribution" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Configure-Scheme-Implementation-to-Locate-SLIB" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Installation" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">8.1.2 Install documentation and slib script</h3>
<a name="index-slib"></a>
<a name="index-script"></a>
<table><tr><td> </td><td><pre class="example">make infoz
make install
</pre></td></tr></table>
<hr size="6">
<a name="Configure-Scheme-Implementation-to-Locate-SLIB"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#Install-documentation-and-slib-script" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Loading-SLIB-Initialization-File" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Installation" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">8.1.3 Configure Scheme Implementation to Locate SLIB</h3>
<p>If the Scheme implementation supports <code>getenv</code>, then the value of
the shell environment variable <var>SCHEME_LIBRARY_PATH</var> will be used
for <code>(library-vicinity)</code> if it is defined. Currently, Bigloo,
Chez, Elk, Gambit, Guile, Jscheme, Larceny, MITScheme, MzScheme,
RScheme, STk, VSCM, and SCM support <code>getenv</code>. Scheme48 supports
<code>getenv</code> but does not use it for determining
<code>library-vicinity</code>. (That is done from the Makefile.)
</p>
<p>The <code>(library-vicinity)</code> can also be set from the SLIB
initialization file or by implementation-specific means.
</p>
<p>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 <code>getenv</code>
(except SCM and Scheme48) provide a means for specifying the
<code>implementation-vicinity</code> through environment variables. Define
the indicated environment variable to the pathname (with trailing
slash or backslash) of the desired directory. Do not use ‘<tt>slib/</tt>’
as an implementation-vicinity!
</p>
<table>
<tr><td width="30%">Bigloo</td><td width="70%">BIGLOO_IMPLEMENTATION_PATH</td></tr>
<tr><td width="30%">Chez</td><td width="70%">CHEZ_IMPLEMENTATION_PATH</td></tr>
<tr><td width="30%">ELK</td><td width="70%">ELK_IMPLEMENTATION_PATH</td></tr>
<tr><td width="30%">Gambit</td><td width="70%">GAMBIT_IMPLEMENTATION_PATH</td></tr>
<tr><td width="30%">Guile</td><td width="70%">GUILE_IMPLEMENTATION_PATH</td></tr>
<tr><td width="30%">Jscheme</td><td width="70%">JSCHEME_IMPLEMENTATION_PATH</td></tr>
<tr><td width="30%">MIT-Scheme</td><td width="70%">MITSCHEME_IMPLEMENTATION_PATH</td></tr>
<tr><td width="30%">MzScheme</td><td width="70%">MZSCHEME_IMPLEMENTATION_PATH</td></tr>
<tr><td width="30%">RScheme</td><td width="70%">RSCHEME_IMPLEMENTATION_PATH</td></tr>
<tr><td width="30%">STk</td><td width="70%">STK_IMPLEMENTATION_PATH</td></tr>
<tr><td width="30%">Vscm</td><td width="70%">VSCM_IMPLEMENTATION_PATH</td></tr>
</table>
<hr size="6">
<a name="Loading-SLIB-Initialization-File"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#Configure-Scheme-Implementation-to-Locate-SLIB" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Build-New-SLIB-Catalog-for-Implementation" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Installation" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">8.1.4 Loading SLIB Initialization File</h3>
<p>Check the manifest in ‘<tt>README</tt>’ to find a configuration file for
your Scheme implementation. Initialization files for most IEEE P1178
compliant Scheme Implementations are included with this distribution.
</p>
<p>You should check the definitions of <code>software-type</code>,
<code>scheme-implementation-version</code>,
<code>implementation-vicinity</code>,
and <code>library-vicinity</code> in the initialization file. There are
comments in the file for how to configure it.
</p>
<p>Once this is done, modify the startup file for your Scheme
implementation to <code>load</code> this initialization file.
</p>
<hr size="6">
<a name="Build-New-SLIB-Catalog-for-Implementation"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#Loading-SLIB-Initialization-File" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Implementation_002dspecific-Instructions" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Installation" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">8.1.5 Build New SLIB Catalog for Implementation</h3>
<p>When SLIB is first used from an implementation, a file named
‘<tt>slibcat</tt>’ is written to the <code>implementation-vicinity</code> for that
implementation. Because users may lack permission to write in
<code>implementation-vicinity</code>, it is good practice to build the new
catalog when installing SLIB.
</p>
<p>To build (or rebuild) the catalog, start the Scheme implementation (with
SLIB), then:
</p>
<table><tr><td> </td><td><pre class="example">(require 'new-catalog)
</pre></td></tr></table>
<p>The catalog also supports color-name dictionaries. With an
SLIB-installed scheme implementation, type:
</p><table><tr><td> </td><td><pre class="example">(require 'color-names)
(make-slib-color-name-db)
(require 'new-catalog)
(slib:exit)
</pre></td></tr></table>
<hr size="6">
<a name="Implementation_002dspecific-Instructions"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#Build-New-SLIB-Catalog-for-Implementation" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#The-SLIB-script" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Installation" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">8.1.6 Implementation-specific Instructions</h3>
<p>Multiple implementations of Scheme can all use the same SLIB directory.
Simply configure each implementation’s initialization file as outlined
above.
</p>
<dl>
<dt><a name="index-SCM"></a><u>Implementation:</u> <b>SCM</b></dt>
<dd><p>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.
</p></dd></dl>
<dl>
<dt><a name="index-Larceny"></a><u>Implementation:</u> <b>Larceny</b></dt>
<dd><p>Starting with version 0.96, Larceny contains its own SLIB
initialization file, loaded by <code>(require 'srfi-96)</code>. If
SCHEME_LIBRARY_PATH is not set, then Larceny looks for an ‘<tt>slib</tt>’
subdirectory of a directory in the list returned by
<code>(current-require-path)</code>
</p>
<table><tr><td> </td><td><pre class="example">larceny -- -e "(require 'srfi-96)"
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-ELK"></a><u>Implementation:</u> <b>ELK</b></dt>
<dd><table><tr><td> </td><td><pre class="example">elk -i -l ${SCHEME_LIBRARY_PATH}elk.init
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-PLT-Scheme"></a><u>Implementation:</u> <b>PLT Scheme</b></dt>
<dt><a name="index-DrScheme"></a><u>Implementation:</u> <b>DrScheme</b></dt>
<dt><a name="index-MzScheme"></a><u>Implementation:</u> <b>MzScheme</b></dt>
<dd>
<p>The ‘<tt>init.ss</tt>’ file in the _slibinit_ collection is an SLIB
initialization file. To run SLIB in MzScheme:
</p>
<table><tr><td> </td><td><pre class="example">mzscheme -f ${SCHEME_LIBRARY_PATH}mzscheme.init
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-MIT-Scheme"></a><u>Implementation:</u> <b>MIT Scheme</b></dt>
<dd><table><tr><td> </td><td><pre class="example">scheme -load ${SCHEME_LIBRARY_PATH}mitscheme.init
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-Gambit_002dC-3_002e0"></a><u>Implementation:</u> <b>Gambit-C 3.0</b></dt>
<dd><table><tr><td> </td><td><pre class="example">gsi -:s ${SCHEME_LIBRARY_PATH}gambit.init -
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-SISC"></a><u>Implementation:</u> <b>SISC</b></dt>
<dd><table><tr><td> </td><td><pre class="example">sisc -e "(load \"${SCHEME_LIBRARY_PATH}sisc.init\")" --
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-Kawa"></a><u>Implementation:</u> <b>Kawa</b></dt>
<dd><table><tr><td> </td><td><pre class="example">kawa -f ${SCHEME_LIBRARY_PATH}kawa.init --
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-Guile"></a><u>Implementation:</u> <b>Guile</b></dt>
<dd><p>Guile versions 1.6 and earlier link to an archaic SLIB version. In
RedHat or Fedora installations:
</p>
<table><tr><td> </td><td><pre class="example">rm /usr/share/guile/slib
ln -s ${SCHEME_LIBRARY_PATH} /usr/share/guile/slib
</pre></td></tr></table>
<p>In Debian installations:
</p>
<table><tr><td> </td><td><pre class="example">rm /usr/share/guile/1.6/slib
ln -s ${SCHEME_LIBRARY_PATH} /usr/share/guile/1.6/slib
</pre></td></tr></table>
<p><code>${SCHEME_LIBRARY_PATH}</code> is where SLIB gets installed.
</p>
<p>Guile with SLIB can then be started thus:
</p>
<table><tr><td> </td><td><pre class="example">guile -l ${SCHEME_LIBRARY_PATH}guile.init
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-Scheme48"></a><u>Implementation:</u> <b>Scheme48</b></dt>
<dd><p>To make a Scheme48 image for an installation under <code><prefix></code>,
</p>
<ol>
<li>
<code>cd</code> to the SLIB directory
</li><li>
type <code>make prefix=<prefix> slib48</code>.
</li><li>
To install the image, type <code>make prefix=<prefix> install48</code>. This
will also create a shell script with the name <code>slib48</code> which will
invoke the saved image.
</li></ol>
</dd></dl>
<dl>
<dt><a name="index-VSCM"></a><u>Implementation:</u> <b>VSCM</b></dt>
<dd><table><tr><td> </td><td><pre class="format">From: Matthias Blume <blume @ cs.Princeton.EDU>
Date: Tue, 1 Mar 1994 11:42:31 -0500
</pre></td></tr></table>
<p>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.
</p>
<p>You have to provide ‘<tt>vscm.init</tt>’ as an explicit command line
argument. Since this is not very nice I would recommend the following
installation procedure:
</p>
<ol>
<li>
run scheme
</li><li>
<code>(load "vscm.init")</code>
</li><li>
<code>(slib:dump "dumpfile")</code>
</li><li>
mv dumpfile place-where-vscm-standard-bootfile-resides. For example:
<p><code>mv dumpfile /usr/local/vscm/lib/scheme-boot</code>
</p>
<p>In this case vscm should have been compiled with flag:
</p>
<p>-DDEFAULT_BOOTFILE=’"/usr/local/vscm/lib/scheme-boot"’
</p>
<p>See Makefile (definition of DDP) for details.
</p></li></ol>
</dd></dl>
<hr size="6">
<a name="The-SLIB-script"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#Implementation_002dspecific-Instructions" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Porting" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="The-SLIB-script-1"></a>
<h2 class="section">8.2 The SLIB script</h2>
<p>SLIB comes with shell script for Unix platforms.
</p>
<table><tr><td> </td><td><pre class="example"><b> slib </b> [ scheme | scm | gsi | mzscheme | guile
| scheme48 | scmlit | elk | sisc | kawa ]
</pre></td></tr></table>
<p>Starts an interactive Scheme-with-SLIB session.
</p>
<p>The optional argument to the <code>slib</code> script is the Scheme
implementation to run. Absent the argument, it searches for
implementations in the above order.
</p>
<hr size="6">
<a name="Porting"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#The-SLIB-script" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Coding-Guidelines" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="Porting-1"></a>
<h2 class="section">8.3 Porting</h2>
<p>If there is no initialization file for your Scheme implementation, you
will have to create one. Your Scheme implementation must be largely
compliant with
</p><table><tr><td> </td><td><pre class="lisp"><cite>IEEE Std 1178-1990</cite>,
<cite>Revised^4 Report on the Algorithmic Language Scheme</cite>, or
<cite>Revised^5 Report on the Algorithmic Language Scheme</cite>
</pre></td></tr></table>
<p>in order to support SLIB. <a name="DOCF8" href="slib_fot.html#FOOT8">(8)</a>
</p>
<p>‘<tt>Template.scm</tt>’ 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
‘<tt>.init</tt>’ appended. For instance, if you were porting
<code>foo-scheme</code> then the initialization file might be called
‘<tt>foo.init</tt>’.
</p>
<p>Your customized version should then be loaded as part of your scheme
implementation’s initialization. It will load ‘<tt>require.scm</tt>’ from
the library; this will allow the use of <code>provide</code>,
<code>provided?</code>, and <code>require</code> along with the <em>vicinity</em>
functions (these functions are documented in the sections
<a href="slib_1.html#Feature">Feature</a> and <a href="slib_1.html#Require">Require</a>). The rest of the library will then
be accessible in a system independent fashion.
</p>
<p>Please mail new working configuration files to <code>agj @ alum.mit.edu</code>
so that they can be included in the SLIB distribution.
</p>
<hr size="6">
<a name="Coding-Guidelines"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#Porting" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Modifications" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="Coding-Guidelines-1"></a>
<h2 class="section">8.4 Coding Guidelines</h2>
<p>All library packages are written in IEEE P1178 Scheme and assume that a
configuration file and ‘<tt>require.scm</tt>’ package have already been
loaded. Other versions of Scheme can be supported in library packages
as well by using, for example, <code>(provided? 'r3rs)</code> or
<code>(require 'r3rs)</code> (see section <a href="slib_1.html#Require">Require</a>).
<a name="index-r3rs-2"></a>
</p>
<p>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:
</p>
<table><tr><td> </td><td><pre class="lisp">(define module-name:foo foo)
</pre></td></tr></table>
<p>The module name and ‘<samp>:</samp>’ should prefix that symbol for the
internal name. Do not export internal aliases.
</p>
<p>A procedure is exported from a module by putting Schmooz-style
comments (see section <a href="slib_4.html#Schmooz">Schmooz</a>) or ‘<samp>;@</samp>’ at the beginning of the line
immediately preceding the definition (<code>define</code>,
<code>define-syntax</code>, or <code>defmacro</code>). Modules, exports and other
relevant issues are discussed in <a href="slib_1.html#Compiling-Scheme">Compiling Scheme</a>.
</p>
<p>Code submitted for inclusion in SLIB should not duplicate (more than
one) routines already in SLIB files. Use <code>require</code> to force
those library routines to be used by your package.
</p>
<p>Documentation should be provided in Emacs Texinfo format if possible,
but documentation must be provided.
</p>
<p>Your package will be released sooner with SLIB if you send me a file
which tests your code. Please run this test <em>before</em> you send me
the code!
</p>
<hr size="6">
<a name="Modifications"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#Coding-Guidelines" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Copyrights" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Coding-Guidelines" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">8.4.1 Modifications</h3>
<p>Please document your changes. A line or two for ‘<tt>ChangeLog</tt>’ is
sufficient for simple fixes or extensions. Look at the format of
‘<tt>ChangeLog</tt>’ to see what information is desired. Please send me
<code>diff</code> files from the latest SLIB distribution (remember to send
<code>diff</code>s of ‘<tt>slib.texi</tt>’ and ‘<tt>ChangeLog</tt>’). 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
‘<tt>slib.texi</tt>’ and ‘<samp>*.init</samp>’ files).
</p>
<p>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.
</p>
<p>Please <em>do not</em> 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.
</p>
<hr size="6">
<a name="Copyrights"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#Modifications" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Putting-code-into-the-Public-Domain" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="Copyrights-1"></a>
<h2 class="section">8.5 Copyrights</h2>
<p><A NAME="Copyrights"></A>
</p>
<p>This section has instructions for SLIB authors regarding copyrights.
<a name="index-copyright"></a>
</p>
<p>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 ‘<tt>require.scm</tt>’ and
‘<tt>macwork.scm</tt>’ illustrate copyright and appropriate terms.
</p>
<p>If your code or changes amount to less than about 10 lines, you do not
need to add your copyright or send a disclaimer.
</p>
<hr size="6">
<a name="Putting-code-into-the-Public-Domain"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#Copyrights" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Explicit-copying-terms" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Copyrights" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">8.5.1 Putting code into the Public Domain</h3>
<p>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.
</p>
<blockquote><p>I, <var><my-name></var>, hereby affirm that I have placed the software
package <var><name></var> in the public domain.
</p>
<p>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.
</p><p align="right"> <var>signature and date</var>
</p></blockquote>
<p>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.
</p>
<p>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.
</p>
<hr size="6">
<a name="Explicit-copying-terms"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#Putting-code-into-the-Public-Domain" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#Example_003a-Company-Copyright-Disclaimer" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Copyrights" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">8.5.2 Explicit copying terms</h3>
<p>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:
</p>
<ul>
<li>
Arrange that your name appears in a copyright line for the appropriate
year. Multiple copyright lines are acceptable.
</li><li>
With your copyright line, specify any terms you require to be
different from those already in the file.
</li><li>
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.
</li></ul>
<hr size="6">
<a name="Example_003a-Company-Copyright-Disclaimer"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#Explicit-copying-terms" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#About-this-manual" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#Copyrights" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<h3 class="subsection">8.5.3 Example: Company Copyright Disclaimer</h3>
<p>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:
</p>
<blockquote><p><var><employer></var> Corporation hereby disclaims all copyright
interest in the program <var><program></var> written by <var><name></var>.
</p>
<p><var><employer></var> 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.
</p>
<p align="left"><var><signature and date></var>,
<var><name></var>, <var><title></var>, <var><employer></var> Corporation
</p></blockquote>
<hr size="6">
<a name="About-this-manual"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#Example_003a-Company-Copyright-Disclaimer" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#GNU-Free-Documentation-License" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="About-this-manual-1"></a>
<h2 class="section">8.6 About this manual</h2>
<ul>
<li>
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.
</li><li>
Examples in this text were produced using the <code>scm</code> Scheme
implementation.
</li><li>
At the beginning of each section, there is a line that looks like:
<a name="index-feature-2"></a>
<table><tr><td> </td><td><pre class="example">(require 'feature)
</pre></td></tr></table>
<p>Include this line in your code prior to using the package.
</p></li></ul>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top"><a href="#GNU-Free-Documentation-License">8.6.1 GNU Free Documentation License</a></td><td> </td><td align="left" valign="top">
</td></tr>
</table>
<hr size="6">
<a name="GNU-Free-Documentation-License"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#About-this-manual" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="#About-SLIB" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#About-this-manual" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="GNU-Free-Documentation-License-1"></a>
<h3 class="subsection">8.6.1 GNU Free Documentation License</h3>
<p align="center"> Version 1.2, November 2002
</p>
<table><tr><td> </td><td><pre class="display">Copyright © 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.
</pre></td></tr></table>
<ol>
<li>
PREAMBLE
<p>The purpose of this License is to make a manual, textbook, or other
functional and useful document <em>free</em> 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.
</p>
<p>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.
</p>
<p>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.
</p>
</li><li>
APPLICABILITY AND DEFINITIONS
<p>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.
</p>
<p>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.
</p>
<p>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.
</p>
<p>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.
</p>
<p>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.
</p>
<p>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”.
</p>
<p>Examples of suitable formats for Transparent copies include plain
<small>ASCII</small> without markup, Texinfo input format, LaTeX input
format, <acronym>SGML</acronym> or <acronym>XML</acronym> using a publicly available
<acronym>DTD</acronym>, and standard-conforming simple <acronym>HTML</acronym>,
PostScript or <acronym>PDF</acronym> designed for human modification. Examples
of transparent image formats include <acronym>PNG</acronym>, <acronym>XCF</acronym> and
<acronym>JPG</acronym>. Opaque formats include proprietary formats that can be
read and edited only by proprietary word processors, <acronym>SGML</acronym> or
<acronym>XML</acronym> for which the <acronym>DTD</acronym> and/or processing tools are
not generally available, and the machine-generated <acronym>HTML</acronym>,
PostScript or <acronym>PDF</acronym> produced by some word processors for
output purposes only.
</p>
<p>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.
</p>
<p>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.
</p>
<p>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.
</p>
</li><li>
VERBATIM COPYING
<p>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.
</p>
<p>You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
</p>
</li><li>
COPYING IN QUANTITY
<p>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.
</p>
<p>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.
</p>
<p>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.
</p>
<p>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.
</p>
</li><li>
MODIFICATIONS
<p>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:
</p>
<ol>
<li>
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.
</li><li>
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.
</li><li>
State on the Title page the name of the publisher of the
Modified Version, as the publisher.
</li><li>
Preserve all the copyright notices of the Document.
</li><li>
Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
</li><li>
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.
</li><li>
Preserve in that license notice the full lists of Invariant Sections
and required Cover Texts given in the Document’s license notice.
</li><li>
Include an unaltered copy of this License.
</li><li>
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.
</li><li>
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.
</li><li>
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.
</li><li>
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.
</li><li>
Delete any section Entitled “Endorsements”. Such a section
may not be included in the Modified Version.
</li><li>
Do not retitle any existing section to be Entitled “Endorsements” or
to conflict in title with any Invariant Section.
</li><li>
Preserve any Warranty Disclaimers.
</li></ol>
<p>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.
</p>
<p>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.
</p>
<p>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.
</p>
<p>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.
</p>
</li><li>
COMBINING DOCUMENTS
<p>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.
</p>
<p>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.
</p>
<p>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.”
</p>
</li><li>
COLLECTIONS OF DOCUMENTS
<p>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.
</p>
<p>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.
</p>
</li><li>
AGGREGATION WITH INDEPENDENT WORKS
<p>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.
</p>
<p>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.
</p>
</li><li>
TRANSLATION
<p>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.
</p>
<p>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.
</p>
</li><li>
TERMINATION
<p>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.
</p>
</li><li>
FUTURE REVISIONS OF THIS LICENSE
<p>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
<a href="http://www.gnu.org/copyleft/">http://www.gnu.org/copyleft/</a>.
</p>
<p>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.
</p></li></ol>
<a name="ADDENDUM_003a-How-to-use-this-License-for-your-documents"></a>
<h2 class="heading">ADDENDUM: How to use this License for your documents</h2>
<p>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:
</p>
<table><tr><td> </td><td><pre class="smallexample"> Copyright (C) <var>year</var> <var>your name</var>.
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''.
</pre></td></tr></table>
<p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
replace the “with…Texts.” line with this:
</p>
<table><tr><td> </td><td><pre class="smallexample"> with the Invariant Sections being <var>list their titles</var>, with
the Front-Cover Texts being <var>list</var>, and with the Back-Cover Texts
being <var>list</var>.
</pre></td></tr></table>
<p>If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.
</p>
<p>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.
</p>
<hr size="6">
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#About-SLIB" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="slib_9.html#Index" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="slib.html#Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="slib_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="slib_10.html#Procedure-and-Macro-Index" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="slib_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<p>
<font size="-1">
This document was generated by <em>root</em> on <em>June 9, 2010</em> using <a href="http://www.nongnu.org/texi2html/"><em>texi2html 1.82</em></a>.
</font>
<br>
</p>
</body>
</html>
|