summaryrefslogtreecommitdiff
path: root/help/comp.programming.literate_FAQ
blob: 9cf2fe52835045a28f37d6d62785303f76c88c42 (plain)
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
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
Path: senator-bedfellow.mit.edu!dreaderd!not-for-mail
Message-ID: <literate-programming-faq_1075625008@rtfm.mit.edu>
Supersedes: <literate-programming-faq_1074244461@rtfm.mit.edu>
Expires: 1 Mar 2004 08:43:28 GMT
X-Last-Updated: 2000/03/16
From: thompson@shelob.ce.ttu.edu
Organization: Texas Tech University, Lubbock, Texas, USA
Newsgroups: comp.programming.literate,comp.answers,news.answers
Subject: comp.programming.literate FAQ
Followup-To: comp.programming.literate
Reply-To: thompson@shelob.ce.ttu.edu
Approved: news-answers-request@MIT.Edu
Summary: Literate Programming FAQ
Distribution: world
Originator: faqserv@penguin-lust.MIT.EDU
Date: 01 Feb 2004 08:43:46 GMT
Lines: 2618
NNTP-Posting-Host: penguin-lust.mit.edu
X-Trace: 1075625026 senator-bedfellow.mit.edu 574 18.181.0.29
Xref: senator-bedfellow.mit.edu comp.programming.literate:5657 comp.answers:56121 news.answers:265541

Archive-name: literate-programming-faq
Last-modified: 2000/03/15
Version: 1.3.1

The Literate Programming FAQ
  David B. Thompson <thompson@shelob.ce.ttu.edu>
  Version: 1.3.1, Mar 15, 2000

  The purpose of this document is two-fold: First, there is a need to
  present a basic description of literate programming and how applica-
  tion of literate programming principles can improve the resulting
  code.  Second, there is a need to present a list of tools available 
to
  iterate programmers.  Hopefully, this document will meet both needs.
  ____________________________________________________________________
__

  Table of Contents






















































  1. Welcome

     1.1 Disclaimer
     1.2 Copyright
     1.3 What's New?
     1.4 What's Needed?

  2. Introduction

  3. How do I get the FAQ?

     3.1 Literate Programming FAQ

  4. Is there a newsgroup?

  5. What internet nodes are of interest to literate programmers?

     5.1 Web Ring
     5.2 The Literate Programming Archive (LPA)
     5.3 Comprehensive TeX Archive Network (CTAN)

  6. What is Literate Programming?

  7. How do I begin literate programming?

  8. Important and Actively-Supported Tools

     8.1 CWEB
     8.2 CWEBx3.0
     8.3 FWEB
     8.4 noweb
     8.5 nuweb
     8.6 ProTeX

  9. Unsupported Tools

     9.1 AFTWEB (Almost Free Text WEB)
     9.2 APLWEB
     9.3 CLiP
     9.4 mCWEB
     9.5 FunnelWeb
     9.6 FunnelWeb 3.0AC
     9.7 LEO
     9.8 Literate Programmer's Workshop (LPW)
     9.9 MapleWEB
     9.10 Matlabweb
     9.11 RWEB
     9.12 SchemeWEB
     9.13 SpideryWEB
     9.14 WEB
     9.15 WinWordWEB

  10. Are there other tools I should know about?

     10.1 C2LaTeX
     10.2 c2cweb
     10.3 c2man
     10.4 cnoweb
     10.5 dpp
     10.6 Fold2Web
     10.7 Funnelweb Mode
     10.8 noweb.el
     10.9 noweb-outline.el
     10.10 nuweb.el
     10.11 Web mode

  11. What other resources are available?

     11.1 TeX Resources

  12. Are there any code examples?

  13. Bibliographies

  14. Other Opinions about Literate Programming

     14.1 van Ammers
     14.2 Ramsey
     14.3 My (Dave Thompson's) Experience
     14.4 Others

  15. How to anonymously ftp

  16. Acknowledgements

  17. End notes



  ____________________________________________________________________
__

  1.  Welcome

  Information contained in this document is the best available at
  preparation.  The original file was dated October 15, 1993 (just for
  historical purposes).


  1.1.  Disclaimer

  This FAQ is presented with no warranties or guarantees of ANY KIND
  including correctness or fitness for any particular purpose.  The
  author of this document has attempted to verify correctness of the
  data contained herein; however, slip-ups can and do happen.  If you
  use this data, you do so at your own risk.


  1.2.  Copyright

  Copyright 1993-2000 by David B. Thompson.  All rights reserved
  worldwide. Permission is granted to copy this document for free
  distribution so long as it remains intact and unmodified.  For other
  arrangements, contact the author/maintainer via email:
  <thompson@shelob.ce.ttu.edu>



  1.3.  What's New?


  o  Updated dpp entry.  See Section ``dpp''

  o  Added noweb-outline.el entry.  See section ``noweb-outline.el''


  1.4.  What's Needed?


  o  I've checked some of the links to software.  If anyone finds the
     FAQ useful, please let me know if the links are active or dead 
when
     you're surfing.

  o  Some authors have disappeared.  If you know one of them, or are 
an
     author (and wish to remain in contact ;), then please provide
     current contact information.

  o  I could use some feedback on the state of the FAQ.  It's about as
     complete as I know how to make it.



  2.  Introduction

  Literate programming is a phrase coined by Donald Knuth to describe
  the approach of developing computer programs from the perspective 
of a
  report or prose.  The focus, then, is on description (and
  documentation) of the approach in human-readable form. This is in
  contrast to the normal approach of focusing on the code.

  This document is for new and experienced users of literate 
programming
  tools.  The purpose is to explain the concept of literate 
programming
  and to provide a resource for locating resources of interest to
  literate programmers and those interested in literate programming.

  The Literate Programming (LitProg) Frequently Asked Questions (FAQ)
  list is maintained by Dave Thompson <thompson@shelob.ce.ttu.edu>.

  Comments and constructive criticisms are welcome.  Direct flames to
  /dev/null (or nul if you're a msdos user! ;-) If you find an error,
  please report it.  I'm particularly interested in establishing the
  locations of generally available literate programming tools.  If you
  are the author of such a tool and wish to have it included in this
  list, please send email.

  Please note this is a work-in-progress.  It is not complete, and
  probably will never be complete.  Nevertheless, the information
  contained herein may be useful to some.  Use it as it is intended.



  3.  How do I get the FAQ?

  3.1.  Literate Programming FAQ

  You have many ways to get a current copy of this FAQ.  One is to use
  anonymous ftp (if you don't know how, see a later section in this 
FAQ)
  to connect to one of the ``Comprehensive TeX Arvchive Network'' 
sites
  or the Literate Programming Archive and retrieve a copy of the file.
  Open an ftp connection to one of the CTAN sites and retrieve the 
file
  help/comp.programming.literate_FAQ.

  Cesar Bellardini cballard@santafe.com.ar prepared a translation of 
the
  FAQ into Spanish.  It's available at

  (For more information on CTAN and the literate programming archive,
  see the section below entitled ``Internet Nodes of Interest to
  Literate Programmers''.)



  4.  Is there a newsgroup?

  One of the most important resources is the literate programming
  newsgroup, comp.programming.literate.  Because of the amount of
  spamming and unrelated posts, the newsgroup is now moderated.  You 
can
  read this newsgroup using your standard reader.


  5.  What internet nodes are of interest to literate programmers?

  The principal nodes of interest to literate programmers are the
  Literate Programming Archive (LPA hereafter) and the CTAN
  (Comprehensive TeX Archive Network).



  5.1.  Web Ring


  There is a web ring for literate programming.  It is at the URL
  www.webring.org/cgi-bin/webring?ring=litprog;list



  5.2.  The Literate Programming Archive (LPA)

  The Literate Programming Archive (LPA) is:

  o  Node: ftp.th-darmstadt.de [130.83.55.75]

  o  Directory: /pub/programming/literate-programming

  o  Notes: Fastest response during off-U.S.  [yep] business hours.

  However, the LPA seems to be defunct in that no files are available 
in
  the /pub directory.  If anyone knows anything about the status of 
the
  LPA, please send email.



  5.3.  Comprehensive TeX Archive Network (CTAN)

  Participating hosts in the Comprehensive TeX Archive Network are 
(from
  the file CTAN.sites):

  o  ftp.dante.de (Mainz, Germany)

  o  anonymous ftp /tex-archive (/pub/tex /pub/archive)

  o  Gopher: gopher.dante.de

  o  e-mail ftpmail@dante.de

  o  WWW www.tex.ac.uk

  o  Administrator: <ftpmaint@dante.de>

  o  ftp.tex.ac.uk (Cambridge, UK)

  o  anonymous ftp /tex-archive (/pub/tex /pub/archive)

  o  Gopher: gopher.tex.ac.uk

  o  NFS mountable from nfs.tex.ac.uk:/public/ctan/tex-archive

  o  WWW www.tex.ac.uk

  o  Administrator: <ctan-uk@tex.ac.uk>

  o  ctan.tug.org (Boston, Massachusetts, USA)

  o  anonymous ftp /tex-archive (/pub/archive)


  o  WWW ctan.tug.org

  o  Administrator: <ctan@tug.org>

  The pointer, ftp://ftp.cdrom.com/pub/tex/ctan/CTAN.sites, is 
directed
  to the official list of CTAN archive sites and their mirrors.



  6.  What is Literate Programming?

  Literate programming is the combination of documentation and source
  together in a fashion suited for reading by human beings.  In fact,
  literate programs should be enjoyable reading, even inviting!  
(Sorry
  Bob, I couldn't resist!)  In general, literate programs combine 
source
  and documentation in a single file.  Literate programming tools then
  parse the file to produce either readable documentation or 
compilable
  source.  The WEB style of literate programming was created by D.E.
  Knuth during the development of his TeX typsetting software.

  All the original work revolves around a particular literate
  programming tool called WEB.  Knuth says:

       The philosophy behind WEB is that an experienced system pro-
       grammer, who wants to provide the best possible documenta-
       tion of his or her software products, needs two things
       simultaneously: a language like TeX for formatting, and a
       language like C for programming.  Neither type of language
       can provide the best documentation by itself; but when both
       are appropriately combined, we obtain a system that is much
       more useful than either language separately.



       The structure of a software program may be thought of as a
       web that is made up of many interconnected pieces.  To docu-
       ment such a program we want to explain each individual part
       of the web and how it relates to its neighbours. The typo-
       graphic tools provided by TeX give us an opportunity to
       explain the local structure of each part by making that
       structure visible, and the programming tools provided by
       languages such as C or Fortran make it possible for us to
       specify the algorithms formally and unambigously. By combin-
       ing the two, we can develop a style of programming that max-
       imizes our ability to perceive the structure of a complex
       piece of software, and at the same time the documented pro-
       grams can be mechanically translated into a working software
       system that matches the documentation.


  See Section ``Other Opinions'' for some additional thoughts on
  literate programming.



  7.  How do I begin literate programming?

  I've given considerable thought as to what should be in this section
  of the FAQ.  This is probably the most important section of this
  document.  My suggestion is that you review Section ``Supported
  Tools'' and Section ``Unsupported Tools'' to choose a system
  appropriate for the kind of development you do.  Then, use the 
manual
  that accompanies the system to determine how it complements your
  development style.


  Both Eric van Ammers, Section ``van Ammers'', and Norman Ramsey,
  Section ``Ramsey'', wrote some thoughts on literate programming.  
I've
  included these thoughts in Section ``Other Opinions'' below.

  I started with a pretty-printing tool, Section ``cnoweb'', as a test
  of the utility of interweaving significant documentation with code.
  My experience is detailed in Section ``Thompson''.

  Wayne Sewell's (1989) Weaving a Program: Literate Programming in 
WEB.
  Van Nostrand Reinhold, ISBN 0-442-31946-0 (pbk).   This book focuses
  on using Knuth's web system.

  I've read D. E. Knuth's collection of articles (1992) entitled
  Literate Programming. Center for the Study of Language and
  Information, Stanford University, ISBN 0-937073-80-6 (pbk).  This 
book
  gives insight into Knuth's thoughts as he developed the web system 
of
  literate programming (and TeX for typesetting).  However, it does 
not
  document methods for literate programming.

  Some talk exists in the newsgroup/mailing list for a Usenet 
University
  course in literate programming.  I'm sure discussion of this topic
  will be welcomed.  (1Feb2000: Note this thread has been dead for a
  long, long time.  I wish someone would pick it up.)



  8.  Important and Actively-Supported Tools

  I have selected a few of the tools from my list that appear to be 
most
  actively supported.  Inclusion here does not imply endorsement;
  exclusion does not imply lack of quality.


  8.1.  CWEB


     Developer:
        Silvio Levy and D.E. Knuth

     Version:
        3.5

     Hardware:
        Unix systems (dos and amiga ports available)

     Languages:
        C and C++

     Formatter:
        Plain TeX and LaTeX.

     Availability:
        Anonymous ftp from:

     o  ftp://labrea.stanford.edu:/pub/cweb

     o  LPA:/c.c++

     o  CTAN:/web/c_cpp/cweb

     o  DOS version is no longer available.

     o  Win32 version www.literateprogramming.com

     o  Amiga version from Aminet:dev/c.

     o  Mac port of CTANGLE in LPA:/machines/mac

     o  LaTeX support in LPA:/c.c++

     Readme:
        Bundled with above

     Description:
        No description provided.

     Support:
        Bugs to <levy@math.berkeley.edu>


  8.2.  CWEBx3.0


     Developer:
        Marc van Leeuwen

     Version:
        3.04

     Hardware:
        Any system using ASCII code

     Languages:
        ANSI C

     Formatter:
        Plain TeX

     Availability:
        Anonymous ftp from:

     o  wwwmathlabo.univ-poitiers.fr/~maavl/CWEBx/

     Readme:
        Bundled with above

     Brief description:
        A modified implementation of CWEB, with some extensions.
        Provides a mode for full compatibility with Levy/Knuth CWEB. 
The
        most significant extras are:

     o  Typedef declarations affect formatting througout source file

     o  Include files are scanned for typedef definitions

     o  Flexible selection of layout style

     o  Possibility to refer to sections using symbolic labels

     o  CTANGLE detects unbalanced braces and parentheses

     o  CWEAVE can be made to report syntax errors more easily

     o  Some additional mechanisms to avoid formatting problems

     o  New and modular set of grammar rules, based on ANSI C syntax

     o  Possibility to suppress #line directives

     o  A new manual


     Support:
        bugs and remarks to maavl@mathlabo.univ-poitiers.fr


  8.3.  FWEB


     Developer:
        John A. Krommes

     Version:
        1.62

     Hardware:
        Unix, VMS, and DOS platforms (anything with ANSI C)

     Languages:
        C, C++, Fortran-77, Fortran-90, Ratfor, TeX; also, a anguage-
        independent mode.

     Formatter:
        LaTeX.  Plain TeX may work, but is no longer supported.

     Availability:
        Anonymous ftp from:

     o  ftp.pppl.gov/pub/fweb

     o  CTAN:/web/fweb

     o  msdos version on ftp.ppl.gov site

     Readme:
        In bundle with above.

     Description:
        It also has a well-developed user's manual and its own FAQ 
(see
        above).  Beginning with 1.40, documentation is maintained in 
gnu
        texinfo format.  It runs on most platforms: VMS, PC, UNIX, and
        pretty much anything that the GNU C compiler (GCC) is 
supported
        for.

     Features:

     o  Processes multiple languages during a single run (so one can 
mix
        C and Fortran, for example).

     o  Language-independent mode (v1.40).

     o  Ability to turn off pretty-printing (v1.40).

     o  Built-in Ratfor translator.

     o  Built-in macro preprocessor (closely follows ANSI C, with
        extensions).

     o  A style file that allows the user to adjust many parameters 
and
        behavior patterns of FWEB.

     o  Various operator-overloading features that provide additional
        pretty-printing capabilities to languages such as C++ and
        Fortran-90.

     o  Numerous miscellaneous features and command-line options.


     Support:
        Bug reports and suggestions to krommes@princeton.edu Online
        documentation is available at
        w3.pppl.gov/%7ekrommes/fweb_toc.html


  8.4.  noweb


     Developer:
        Norman Ramsey <nr@eecs.harvard.edu>

     Version:
        2.9a

     Hardware:
        Unix and DOS platforms (DOS binaries available for v2.7).

     Languages:
        All programming languages, singly or in combination.  
Automatic
        indexing for C, Icon, Pascal, Standard ML, TeX, Yacc

     Formatter:
        Plain TeX, LaTeX, and HTML formatters.  Will convert LaTeX to
        HTML automatically.

     Availability:
        Anonymous ftp from:

     o  CTAN:/web/noweb

     o  LPA:/independent

     o  Last recourse, use ftp.cs.virginia.edu:pub/nr

     Readme:
        With bundle above, or see the noweb home page:
        www.eecs.harvard.edu/~nr/noweb Those without http access can
        consult ``Literate Programming Simplified,'' IEEE Software,
        September 1994, pp97-105, or ``Literate Programming Using
        Noweb,'' Linux Journal, October 1997, pp64-69.


     Description:
        Noweb is designed to meet the needs of literate programmers
        while retaining the simplest possible input format.  Its 
primary
        advantages are simplicity, extensibility, and language-
        independence.  Noweb uses 5 control sequences to WEB's 27.  
The
        noweb manual is only 3 pages; an additional page explains how 
to
        customize its LaTeX output.  Noweb works ``out of the box'' 
with
        any programming language, and supports TeX, latex, and HTML 
back
        ends.  A back end to support full hypertext or indexing takes
        about 250 lines; a simpler one can be written in 40 lines of
        awk. Unlike WEB, Noweb does not have prettyprinting built in,
        but there are several third-party extensions that provide
        prettyprinting, includeing dpp, pretzel, and nwpp.


        Noweb supports indexing and identifier cross-reference,
        including hypertext ``hot links.'' noweb includes a simple,
        efficient LaTeX-to-HTML converter, so you can use hypertext
        browsers on your legacy documents.  Noweb can also process 
nuweb
        programs, so you can use noweb to convert a standard nuweb
        program to HTML with one command.


     Support:
        email to the author


  8.5.  nuweb


     Developer:
        Preston Briggs: <preston@cs.rice.edu>

     Version:
        0.87

     Hardware:
        Unix systems: Sparcs, RS/6000s, HPs; (!) MSDOS and Amiga.

     Languages:
        Any programming language or combination of programming
        languages.

     Formatter:
        Latex

     Availability:
        Anonymous ftp from:

     o  Unix: CTAN:/web/nuweb

     o  DOS:  CTAN:/web/nuweb-pc

     o  LPA:/independent

     o  Amiga: CTAN:/web/nuweb/nuweb_ami

     o  Amiga: wuarchive.wustl.edu/pub/aminet

     Readme:
        Send mail to <preston@cs.rice.edu>


     Description:
        A single program that takes a web file written in a 
combination
        of latex and any programming language(s) and produces a latex
        file that can be pretty printed and a set of files containing
        code for compilation/interpretation by the appropriate 
language
        processors.


        Strengths include speed, simplicity, multiple languages, nice
        indices and cross-references, latex.  Doesn't require any
        special macros or macro files.


        Drawbacks: latex-dependent, no code pretty printing, harder to
        make indices than cweb.


        More good stuff: nice support for make, doesn't reformat 
source
        files, so they're easy to debug.  Lots of control without too
        much effort.  That is, it doesn't do too much!


        Future directions... Very little change planned, except 
perhaps
        refinements in the indexing software.


     Support:
        Hack it yourself or send e-mail to <preston@cs.rice.edu>


  8.6.  ProTeX


     Developer:
        Eitan Gurari <gurari@cis.ohio-state.edu>

     Version:
        ProTeX 1.5,  AlProTeX 2.3

     Hardware:
        Any platform with (La)TeX

     Languages:
        Any language

     Formatter:
        TeX or LaTeX

     Availability:
        Anonymous ftp from:

     o  www.cis.ohio-state.edu/~gurari/systems.html

     o  LPA:/independent

     Readme:
        With bundle above

     Description:

     o  Easy to use

     o  Extensible

     o  Language independent

     o  Multiple output files

     o  Fast (single compilation provides output and dvi files)

     o  Option for XHTML and pdf files

     o  No installation is needed besides copying the files (written 
in
        TeX) Introduction of main features and examples on web site
        above.  Complete manual in Eitan M. Gurari, "TeX and LaTeX:
        Drawing and Literate Programming", McGraw-Hill, 1994

     Support:
        <gurari@cis.ohio-state.edu>



  9.  Unsupported Tools



  9.1.  AFTWEB (Almost Free Text WEB)


     Developer:
        Todd A. Coram

     Version:
        4.6

     Hardware:
        Linux, Unix, MSDOS Any system with Perl, and a C++ compiler 
with
        STL (such as gcc 2.7.2).

     Languages:
        Any (C/C++ support supplied)

     Formatter:
        LaTeX or HTML by way of AFT.

     Availability:
        www.mindspring.com/~coram/aft.html

     Readme:
        Bundled with above.


     Brief description:
        AFTWEB uses a CWEB-like syntax. It uses AFT for documentation
        markup (AFT is a minimalistic, yet powerful, markup language
        with very few commands).  AFTWEB was written in AFTWEB (using
        C++) and the weaved document is available online (as HTML) at
        the URL listed above.


        Support for C and C++ is supplied. You can easily support 
other
        languages (such as Java and Perl) by writing a new language
        description file.


        The markup language AFT is very easy to learn and is available
        at the same URL as AFTWEB.


     Support:
        Bugs to tcoram@pobox.com


  9.2.  APLWEB


     Developer:
        Christoph von Basum

     Version:
        Unknown

     Hardware:
        MSDOS

     Languages:
        IBM APL2 and STSC APL

     Formatter:
        Plain TeX

     Availability:
        Anonymous ftp from: watserv1.uwaterloo.ca:/languages/apl/aplwe
b

     Readme:
        At above ftp location.


     Description:
        None available.

     Support:
        Unknown

     Note:
        The status of this particular package is unknown.  It's at the
        ftp site, but other than that I can't say.  Last known email
        address of developer is CvB@erasmus.hrz.uni-bielefeld.de.


  9.3.  CLiP


     Developer:
        E.W. van Ammers and M.R. Kramer

     Versions:
        2.0 and 2.4b (DOS only)

     Platform:
        Vax/VMS, Unix, DOS

     Languages:
        Any programming language

     Formatter:
        Any formatter (TeX, LaTeX, Troff, Runoff, HTML, etc) or any
        wordprocessor including WYSIWYG systems (Word Perfect, 
WinWord,
        Ami Pro, Word Pro, etc.)

     Availability:
        Anonymous ftp from:

     o  ftp://sun01.info.wau.nl:/CLIP/ms_dos

     o  ftp://sun01.info.wau.nl:/CLIP/ms_dos_24b

     o  ftp://sun01.info.wau.nl:/CLIP/vax_vms

     o  ftp://sun01.info.wau.nl:/CLIP/unix

     o  CTAN:/web/clip

     o  LPA:/machines/ms-dos

     o  LPA:/machines/vax

     Readme:
        With bundle above

     Description:
        CLiP does not use explicit commands to perform the extraction
        process. Rather it recognizes pseudostatements written as
        comments in the programming language in question. CLiP
        distinguishes pseudostatements from ordinary comments because
        the former comply with a particular style. This style can be
        adjusted to suit virtually any programming language. The CLiP
        approach to LP makes the system extremely versatile. It is
        independent of programming language and text processing
        environment. We designed CLiP to be compatible with hypertext
        systems as well. Some hypertext examples are at:

     o  ftp://sun01.info.wau.nl/clip/html/queens.htm

     o  ftp://sun01.info.wau.nl/clip/html/pal1.htm

     Features:

     o  CLiP imposes virtually no limitations on the text-processing
        system used to produce the documentation. If the 
text-processor
        supports these items you can

     o  structure the documentation according to your own taste.

     o  include drawings, pictures, tables etc.

     o  disclose your documentation my means of X-ref tables, Indexes,
        Table of contents, Table of tables, Table of figures, etc.

     o  typeset the documented code.

     o  Extracts any number of modules from a maximum of 64 source
        files.

     o  No pretty-printing. Code from the source files is copied "as 
is"
        to the module.

     o  Appearance of code segments in the documentation matches those
        of the modules to ease the identification of code segments.

     o  Supports partially specified data types.

     o  Comprehensive user manual (preliminary version) and technical
        description.

     o  No automatic generation of a X-ref table for program
        identifiers.

     Support:
        Bugs, problems and assistance by e-mail to
        <Eric.vanAmmers@user.info.wau.nl>


  9.4.  mCWEB


     Developer:
        Markus Oellinger

     Version:
        1.0

     Hardware:
        Unix

     Languages:
        C/C++

     Formatter:
        plain TeX

     Availability:
        anonymous ftp from ist.tu-
        graz.ac.at:/pub/utils/litprog/mcweb/mcweb.tgz

     Readme:
        at same location

     Description:
        This is mCWEB 1.0, a descendant of the CWEB system of 
structured
        documentation by Donald E. Knuth and Silvio Levy.  It adds 
some
        features that are indispensable when working in a team. mCWEB
        regards a project of a book consisting of several chapter 
files.
        By means of import and export commands, it automatically 
manages
        all relationships between the chapters of a book and to other
        books.


        Interface documentation is now also part of mCWEB. It is
        extracted into a second TeX file. This makes it possible to
        define well known interfaces between the individual parts of a
        project that will be implemented by different persons.


        In addition, mCWEB parses C header files to find out about all
        the datatypes defined there.


        mCWEB comes with a full completely rewritten user manual and 
is
        compatible with CWEB.


     Support:
        Institute of Software Technology, moell@ist.tu-graz.ac.at


  9.5.  FunnelWeb


     Developer:
        Ross N. Williams ross@ross.net

     Version:
        V3.2  (May 1999).

     Hardware:
        MS-DOS, MacOS, Win32, OpenVMS, Solaris, Red Hat Linux, BSD/OS,
        FreeBSD, Digital Unix, IRIX.

     Status:
        Open Source GNU.

     Languages:
        No restrictions.

     Formatter:
        Generates TeX and/or HTML

     Web:
        www.ross.net/funnelweb/

     Availability:
        ftp.ross.net/clients/ross/funnelweb/

     Readme:
        With bundle above.


     Description:
        FunnelWeb is a production-quality literate-programming tool 
that
        emphasises simplicity and reliability. Everything about
        FunnelWeb, from the simplicity of its language to the
        comprehensive tutorial in the user's manual, has been designed
        to make this as simple, as practical, and as usable a tool as
        possible.

     Features:

     o  Provides a simple macro preprocessor facility.

     o  Generates typeset documentation in TeX and/or HTML formats.

     o  Runs on a wide range of platforms.

     o  Portable C source code distributed under GNU licence.

     o  Comprehensively documented online:

     o  www.ross.net/funnelweb/tutorial/

     o  www.ross.net/funnelweb/reference/

     o  www.ross.net/funnelweb/developer/

     o  Programming-language independent.

     o  Mature and essentially bug-free (released 1992).

     o  Can generate multiple output files.

     o  Allows complete control over the output text.

     o  Also useful for generating web sites!


     Support:
        No formal support available.  Mailing list maintained with 
about
        50 subscribers.  Informal assistance available from mailing
        list.


  9.6.  FunnelWeb 3.0AC


     Developer:
        Enhanced by A.B.Coates coates@physics.uq.edu.au from FunnelWeb
        v3.0 by Ross N. Williams ross@guest.adelaide.edu.au

     Version:
        3.0AC

     Hardware:
        MSDOS, Mac, VMS, Sun, OSF/1, Linux, Sys.V, OS/2.

     Languages:
        No restrictions.

     Formatter:
        Tex, LaTeX, or HTML.

     Availability:
        Anonymous ftp from
        ftp.physics.uq.oz.au:/pub/funnelwebAC30.tar.gz

     Readme:
        With bundle above; for FunnelWeb manual see WWW page
        www.physics.uq.oz.au:8001/people/coates/funnelweb.html


     Description:
        FunnelWeb 3.0AC is an enhanced version of FunnelWeb (see the
        entry for FunnelWeb).  FunnelWeb is designed to be typesetter
        independent, though FunnelWeb v3.0 only supports (La)TeX as 
the
        typesetter.  FunnelWeb 3.0AC also supports HTML, and creates
        appropriate hypertext links within the document among the code
        sections.  FunnelWeb 3.0AC also supports automatic and manual
        insertion of line directives, so that compiler errors can be
        flagged back to the original FunnelWeb source file.  FunnelWeb
        3.0AC is completely compatible with FunnelWeb v3.0 sources 
(with
        one minor exception; see the file README.ABC which comes with
        the FunnelWeb 3.0AC distribution).


     Support:
        Supported by A.B.Coates coates@physics.uq.edu.au, subject to 
the
        time constraints imposed by his thesis.


  9.7.  LEO


     Developer:
        Edward K. Ream edream@mailbag.com

     Version:
        1.0

     Hardware:
        Windows

     Languages:
        Unknown

     Formatter:
        Unknown

     Availability:
        Contact the author or see
        www.mailbag.com/users/edream/front.html

     Readme:
        Unknown

     Description:
        See web site.

     Support:
        Unknown.


  9.8.  Literate Programmer's Workshop (LPW)


     Developer:
        Norbert Lindenberg

     Version:
        1.1

     Hardware:
        Apple Macintosh

     Languages:
        C++, Object Pascal & others

     Formatter:
        self-contained WYSIWYG system

     Availability:
        Anonymous ftp from:

     o  CTAN:/web/lpw

     o  ftp.apple.com:/pub/literate.prog

     Readme:
        With bundle above.  Also comes with 38-page manual.


     Description:
        The Literate Programming Workshop is an environment for the
        integrated development of program source text and 
documentation
        in combined documents. It consists of a WYSIWYG word processor
        based on a style sheet approach, a mechanism to extract parts 
of
        the text in a document, and a project management system that
        handles multi-document projects. The system is designed to be
        used in conjunction with the Macintosh Programmer's Workshop: 
it
        prepares raw source text for the MPW compilers, accepts MPW
        error messages, and shows them in the context of the original
        documents. Automatic indexing and hypertext features allow for
        easy access to both source text and documentation.


        LPW is shareware.


     Support:
        Bugs, problems, and questions to lpw@aol.com


  9.9.  MapleWEB


     Developer:
        Unknown

     Version:
        Unknown

     Hardware:
        Unknown

     Languages:
        Maple

     Formatter:
        Unknown

     Availability:
        Anonymous ftp from CTAN/maple/mapleweb

     Readme:
        Unknown

     Description:
        None

     Support:
        Unknown





  9.10.  Matlabweb


     Developer:
        Mark Potse

     Version:
        2.09

     Hardware:
        any, but only Unix tested & supported

     Languages:
        Matlab

     Formatter:
        Plain TeX and LaTeX.

     Availability:
        Anonymous ftp from the CTAN archives,

     Readme:
        Bundled with above


     Description:
        CWEB-like literate programming system for the Matlab language.
        Created with a modified version of the Spider system. Several
        more or less language-specific features:

     o  macros with multiple arguments

     o  comments and verbatim comments

     o  strings can be formatted as code, with help for nested 
strings,
        e.g. for callbacks in user interface programming.

     o  string arguments for macros, that get inserted in strings in 
the
        replacement text

     o  "@f foo TeX"  works as in recent versions of CWEB

     Support:
        not guaranteed. Try M.Potse@amc.uva.nl, comments are welcome.


  9.11.  RWEB


     Developer:
        Unknown

     Version:
        Unknown

     Hardware:
        Unknown

     Languages:
        Unknown

     Formatter:
        Unknown

     Availability:
        Anonymous ftp from CTAN
     Readme:
        Unknown

     Description:
        Web generator in AWK.

     Support:
        Unknown


  9.12.  SchemeWEB


     Developer:
        John D. Ramsdell

     Version:
        2.1

     Hardware:
        Unix and DOS platforms

     Languages:
        Any dialect of Lisp.

     Formatter:
        LaTeX.

     Availability:
        The Unix version is in the Scheme Repository and it is 
available
        via anonymous ftp from:

     o  cs.indiana.edu:/pub/scheme-repository/utl/schemeweb.sh

     o  CTAN:/tex-archive/web/schemeweb

     o  The DOS version is part of the PCS/Geneva Scheme system which 
is
        available via anonymous ftp from: cui.unige.ch:/pub/pcs

     Readme:
        In bundle with above.

     Description:
        SchemeWEB is a Unix filter that allows you to generate both 
Lisp
        and LaTeX code from one source file.  The generated LaTeX code
        formats Lisp programs in typewriter font obeying the spacing 
in
        the source file. Comments can include arbitrary LaTeX 
commands.
        SchemeWEB was originally developed for the Scheme dialect of
        Lisp, but it can easily be used with most other dialects.

     Support:
        Bug reports to ramsdell@mitre.org.


  9.13.  SpideryWEB


     Developer:
        Norman Ramsey <nr@eecs.harvard.edu>

     Version:
        Unknown

     Hardware:
        Unix and DOS platforms

     Languages:
        Most Algol-like languages, including C, Ada, Pascal, Awk, and
        many others.

     Formatter:
        Plain TeX and latex for text formatters.

     Availability:
        Anonymous ftp from CTAN.

     Readme:
        In distribution.


     Description:
        A system for building language-dependent WEBs. Spider is 
frozen;
        no further development is planned.


     Support:
        Bug reports to spider-bugs@oracorp.com.


  9.14.  WEB


     Developer:
        Donald Knuth

     Version:
        4.4 (apparently)

     Hardware:
        Any TeX system should have it.

     Languages:
        Pascal

     Formatter:
        TeX (of course! ;-)

     Availability:
        Distributed with TeX systems.  Also avaliable in source form
        from labrea.stanford.edu/tex/web.

     Readme:
        Unknown

     Documentation:
        Available from labrea.stanford.edu/tex/web/webman.tex

     Description:
        This is the original software that started it all.  The 
original
        TeX processor was written in WEB.

     Support:
        None known.


  9.15.  WinWordWEB


     Developer:
        Lee Wittenberg leew@pilot.njin.net


     Version:
        Unknown

     Hardware:
        Needs Microsoft Word for Windows, v.2.x, and, of course, MS-
        Windows 3.x.

     Languages:
        Any programming language.

     Formatter:
        Word for Windows 2.x for text formatting and file maintenance.

     Availability:
        samson.kean.edu:pub/leew

     Readme:
        WORDWEB.DOC in the downloadable package describes the system.

     Description:
        WinWordWEB is a set of a Word for Windows macros (plus a
        paragraph style) that provide a crude literate programming
        environment.  The ``look and feel'' of the system is based on
        Norman Ramsey's noweb, but can easily be modified to suit
        individual tastes.

     Support:
        None.  WinWordWEB was written as a prototype to see if a 
WYSIWYG
        literate programming system was possible.  It is intended as a
        jumping off point for future work by others. However, the 
system
        is surprisingly usable as it stands, and the author is
        interested in hearing from users (satisfied and dissatisfied).


        Anyone interested in actively supporting (and improving) the
        product should contact the author via email.



  10.  Are there other tools I should know about?

  Follows is a list of some not-quite-literate-programming tools.  
Some
  term these pretty-printers.  Others may call them literate 
programming
  tools.  In any event, they don't seem to be quite in the same 
category
  as the tools listed above, so I'll include them here.


  10.1.  C2LaTeX


     Developer:
        John D. Ramsdell

     Version:
        Unknown

     Hardware:
        Unix

     Languages:
        C

     Formatter:
        LaTeX but it's easy to change the formatter.


     Availability:
        Anonymous ftp from omnigate.clarkson.edu:/pub/tex/tex-
        programs/c2latex.

     Readme:
        Absent.  Documentation is in the C source for c2latex.

     Description:
        C2latex provides simple support for literate programming in C.
        Given a C source file in which the comments have been written 
in
        LaTeX, c2latex converts the C source file into a LaTeX source
        file.  It can be used to produce typeset listings of C 
programs
        and/or documentation associated with the program.

        C2latex produces LaTeX source by implementing a small number 
of
        rules.  A C comment that starts at the beginning of a line is
        copied unmodified into the LaTeX source file.  Otherwise, non-
        blank lines are surrounded by a pair of formatting commands
        (\begin{flushleft} and \end{flushleft}), and the lines are
        separated by \\*. Each non-blank line is formatted using 
LaTeX's
        \verb command, except comments within the line are formatted 
in
        an \mbox.

     Support:
        Send bug reports to ramsdell@mitre.org.


  10.2.  c2cweb


     Developer:
        Werner Lemberg

     Version:
        1.5

     Hardware:
        DOS, OS/2, Unix (gcc) - CWEB source included

     Languages:
        C, C++

     Formatter:
        TeX

     Availability:
        Anonymous ftp from CTAN:/web/c_cpp/c2cweb

     Readme:
        In distribution.

     Description:
        c2cweb will transform plain C or C++ code into a CWEB file to
        get a pretty formatted output. A modified CWEAVE (which
        transforms the CWEB file into a TeX file, see below) is 
included
        also.

     Support:
        Werner Lemberg <a7971428@unet.univie.ac.at>


  10.3.  c2man


     author:
        Graham Stoney <greyham@research.canon.oz.au>
     language:
        C, nroff, texinfo, latex, html

     version:
        2.0 patchlevel 33

     parts:
        documentation generator (C -> nroff -man, -> texinfo, ->latex,
        -> html)

     location:
        ftp from

     o  any comp.sources.misc archive, in volume42 (the version in the
        comp.sources.reviewed archive is obsolete)

     o  dnpap.et.tudelft.nl/pub/Unix/Util/ c2man-2.0.*.tar.gz

     o  Australia archie.au/usenet/comp.sources.misc/volume42
        c2man-2.0/*

     o  N.America ftp://ftp.wustl.edu/usenet/comp.sources.misc/volume4
2/
        c2man-2.0/*

     o  Europe: ftp://ftp.irisa.fr/News/comp.sources.misc/volume42/
        c2man-2.0/*

     o  Japan:
        ftp://ftp.iij.ad.jp/pub/NetNews/comp.sources.misc/volume42/
        c2man-2.0/*

     Patches:
        lth.se/pub/netnews/sources.bugs/volume93/sep/c2man*

     description:
        c2man is an automatic documentation tool that extracts 
comments
        from C source code to generate functional interface
        documentation in the same format as sections 2 & 3 of the Unix
        Programmer's Manual. It requires minimal effort from the
        programmer by looking for comments in the usual places near 
the
        objects they document, rather than imposing a rigid function-
        comment syntax or requiring that the programmer learn and use 
a
        typesetting language. Acceptable documentation can often be
        generated from existing code with no modifications.

     conformance:
        supports both K&R and ISO/ANSI C coding styles

     features:

     o  generates output in nroff -man, TeXinfo, LaTeX or HTML format

     o  handles comments as part of the language grammar

     o  automagically documents enum parameter & return values

     o  handles C (/* */) and C++ (//) style comments

     o  doesn't handle C++ grammar (yet)

     requires:
        yacc/byacc/bison, lex/flex, and nroff/groff/texinfo/LaTeX.

     ports:
        Unix, OS/2, MSDOS, VMS.

     portability:
        very high for unix, via Configure

     status:
        actively developed; contributions by users are encouraged.

     discussion:
        via a mailing list: send "subscribe c2man <Your Name>" (in the
        message body) to listserv@research.canon.oz.au

     help:
        from the author and other users on the mailing list:
        c2man@research.canon.oz.au

     announcements:
        patches appear first in comp.sources.bugs, and then in
        comp.sources.misc.

     updated:
        1994/10/07


  10.4.  cnoweb


     Developer:
        Jim Fox

     Version:
        1.4 (January 4, 1991)

     Hardware:
        Anything with C and TeX.

     Languages:
        C

     Formatter:
        Plain TeX.

     Availability:
        Anonymous ftp from:

     o  CTAN

     o  LPA:/c.c++

     Readme:
        Unknown, cnoweb.tex contains documentation.

     Description:
        cnoweb is as it's name describes: write C, not web.  No 
tangling
        or weaving is implemented.  Documentation (between standard /*
        */ delimiteres) is written in TeX.  cnoweb provides 
typesetting
        of documentation, an table of contents of routines, and 
pretty-
        printing of C source.

     Support:
        None known.


  10.5.  dpp


     Developer:
        Dan Schmidt <dfan@alum.mit.edu>
     Version:
        0.2.1

     Hardware:
        Any platform with Perl 5

     Languages:
        C/C++ (Java soon), under noweb

     Formatter:
        LaTeX

     Availability:
        www.dfan.org/real/dpp.nw

     Readme:
        www.dfan.org/real/dpp.html

     Support:
        email to the author <dfan@alum.mit.edu>

     Description:
        dpp is a C/C++ prettyprinter for noweb.  Its output is 
extremely
        similar to that of CWEB, but it respects the indentation and
        line breaks of the source file.

        Features include:

     o  user-defined keywords

     o  the ability to turn prettyprinting off for specified output
        files (e.g., makefiles)

     o  the option to typeset comments in TeX, or not

     o  prettyprinting of quoted code, in documentation or chunk names

     o  the ability to undo whitespace hand-formatting that looks good
        monospaced but awful in a proportional font



  10.6.  Fold2Web


     Developer:
        Bernhard Lang lang@tu-harburg.d400.de

     Version:
        V0.8

     Hardware:
        MSDOS

     Languages:
        All (must allow comment lines)

     Formatter:
        LaTeX

     Availability:
        Anonymous ftp from: kirk.ti1.tu-harburg.de (134.28.41.50)
        /pub/fold2web/readme /pub/fold2web/fold2web.zip

     Readme:
        In distribution
     Description:
        The idea behind the Fold2Web tool is the following: A 
programmer
        can write his program source with a folding editor and later 
map
        the folded source files automatically to WEB-files. The
        generated WEB-files can then be modified by inserting required
        documentations.


        The advantage by starting program developement with original
        sources is to get short design cycles during the compile/debug
        steps. By using a folding editor the global structuring
        information can be already captured in folds during this
        developement phase. Fold information is typically stored in
        comment lines and thus will not affect the efficiency of the
        compile/debug design cycle.


        Some folding editors and a folding mode for the emacs are
        available (e.g. see our FUE folding editor for MSDOS machines
        which is a modified micro emacs. Pick it at kirk in directory
        /pub/fold2web).


        After reaching a stable version of a program source its time 
to
        convert the source file to a WEB-file and do the program
        documentation.  Fold2Web is written to convert folded source
        text of any programming language to nuweb files. The folded
        structure is kept by mapping folds to scraps. Fold markers 
which
        differ between languages due to different ways of specifying
        comments can be configured for each language.


        Good results can also achived when given but poor documented
        program sources have to be modified. Such sources can be 
folded
        using a folding editor to extract the global structures. This
        offers a global view to the program structures and help to
        understand its functionality.  Furthermore the program code is
        not affected, only comment lines are inserted. Once folded the
        program source can be automatically translated to a WEB 
document
        using the above tool.


     Support:
        email to lang@tu-harburg.d400.de


  10.7.  Funnelweb Mode


     Developer:
        Daniel Simmons simmdan@kenya.isu.edu

     Version:
        Unknown

     Availability:
        www.miscrit.be/~ddw


     Description:
        The other day I did a quick hack to nuweb.el as included with
        the nuweb distribution so as to make a funnelweb-mode.el.  
I've
        only used it briefly, and I'm sure that it can be improved 
quite
        a bit.  I've been thinking about adding support for folding on
        sections, a pull-down menu to select macro definitions (like 
the
        recent functions posted to gnu.emacs.sources for a C function
        definition pull-down menu) and some kind of tags support for
        funnelweb.


     Support:
        Unknown


  10.8.  noweb.el


     Developer:
        Bruce Stephens (no email contact)

     Version:
        Unknown.

     Availability:
        Lost

     Description:
        This is a very simple mode I just hacked up.  There's a lot
        wrong with it, but I thought others may be interested, even as
        it stands.  It *requires* text properties, and assumes those
        used in GNU Emacs 19.22; it'll quite likely work with Lucid
        Emacs, but I haven't tried it.


        I use it with auctex8.1 and cc-mode 3.229, both of which are
        loaded separately (I think my emacs is dumped with them, in
        fact).


        The idea is to have one mode (which calls itself c-mode, but
        actually has LaTeX-mode keybindings) generally (this means 
that
        the code is hilighted nicely), and have the code chunks use a
        different keymap.

     Support:
        Unknown


  10.9.  noweb-outline.el


     Developer:
        Dan Schmidt dfan@alum.mit.edu

     Version:
        0.0.3

     Hardware:
        Any platform with Emacs

     Languages:
        noweb

     Availability:
        www.dfan.org/real/noweb-outline.el

     Readme:
        www.dfan.org/real/noweb-outline.html

     Support:
        email to the author, dfan@alum.mit.edu

     Description:
        noweb-outline.el is a mode for Emacs that allows you to easily
        navigate the chunk tree of a noweb program.


        One of the problems with literate programming is that it's 
easy
        to lose track of how your tangled source file (the one that 
the
        compiler actually sees) is structured. In noweb-outline-mode,
        you can interactively explore the tree of chunks you are
        creating, giving you the big picture as well as the small.
        Enough description; it would take more time for me to explain 
it
        than for you to just go ahead and try it out.


        noweb-outline.el is currently in an alpha state (I've worked 
on
        it for only a couple of days), but it is already very useful. 
A
        nice file to use to try it out is example/wc.nw in the noweb
        distribution.


  10.10.  nuweb.el


     Developer:
        Dominique de Waleffe ddw@acm.org

     Version:
        1.99

     Availability:
        Anonymous ftp from CTAN


     Description:
        Provides a major mode extending Auctex for editing nuweb 
files.
        Main features (in 2.0):

     o  Edit scrap bodies in a separate buffer in a different mode
        (selected using emacs defaults for files, specific indication
        -*-mode-*-, or a buffer-local variable)

     o  Extends Auctex commands so that nuweb is called before LaTeX,

     o  Easy navigation on scrap definition and use points.

     o  Now creates an imenu (C-M-mouse1) with user index entries, 
macro
        definition positions and file definition positions.


     Support:
        Email to ddw@acm.org


  10.11.  Web mode


     Developer:
        Bart Childs bart@cs.tamu.edu

     Version:
        Unknown

     Tools supported:
        web, fweb, cweb, funnelweb


     Availability:
        Anonymous ftp ftp.cs.tamu.edu:pub/tex-web/web/EMACS.web-mode
        thrain.anu.edu.au:pub/web/EMACS.web-mode

     Description:
        This version works with versions 18 and 19 of Emacs to be best
        of my knowledge.  I have cleaned up a number of documentation
        items ...  In the same directory is wm_refcard.tex which is an
        edited version of the famous one to include some web-mode
        commands.


        The files limbo* are related to its use and notice that half
        them have an uppercase L in them for LaTeX.  The setup is 
based
        upon the fact that we (I am not alone here) primarily use FWEB
        for C and Fortran programming.


        We are using version 1.40 of FWEB although John Krommes warns
        that it is not mature and the manual is not yet updated.  The
        info files are!  We are using LaTeX almost exclusively.  That
        will likely change and we will revert to version 1.30 if the
        final form of 1.40 cannot return to the simple section numbers
        and avoid the HORRIBLE LATEX 0.1.7.2.4.6 type section numbers.

     Support:
        Unknown


  11.  What other resources are available?

  11.1.  TeX Resources

  Another resource of interest to literate programmers is the
  comp.text.tex newsgroup.   If you're using (La)TeX as your 
typsetting
  system and have access to internet, then you should investigate this
  resource.

  Another reason the TeX resources should be important is that so many
  of the literate programming tools rely on either plain TeX or LaTeX 
as
  their text formatter.  (La)TeX software systems exist for most
  computing platforms.  These systems can be found on CTAN and other
  major archive sites.  Use archie to find them or simply ftp to one 
of
  the CTAN sites and browse.



  12.  Are there any code examples?

  Examples of web programs are included with the FWEB, CWEB, and noweb
  distributions.  nuweb is written in itself.

  Cameron Smith converted the K&R calculator program into a literate
  program.   It can be retrieved by anonymous ftp from:

    niord.shsu.edu [192.92.115.8] directory kr-cweb-sample as
      krcwsamp.zip
    or from
      LPA/Documentation


  Ross Williams has released a funnelweb example.  You can retrieve 
this
  file from node ftp.adelaide.edu.au [129.127.40.3] as

    /pub/funnelweb/examples/except.*

  This file should be on CTAN as well.

  Lee Wittenberg has posted a few litprog examples.  They are 
available
  via anonymous ftp from:

          ftp://samson.kean.edu/pub/leew/samples.LP


  The Stanford GraphBase is a large collection of programs by Don 
Knuth
  for doing all kinds of computations and games with graphs; it is 
writ-
  ten in (Levy/Knuth) CWEB. More details in the distribution.  It is
  available via anonymous ftp from:

    labrea.stanford.edu:/pub/sgb





  13.  Bibliographies

  Nelson Beebe has collected an extensive bibliography treating 
literate
  programming.  His work is available for anonymous ftp from
  ftp://ftp.math.utah.edu/pub/tex/bib/index.html#litprog.  Be sure to
  look around this site; there are many things of interest to user of
  TeX resources as well as literate programmers.

  Although I have not verified this, LPA is an alternate source for
  these files.  Note that they are updated frequently (Nelson says
  several times each week), so be sure to get a fresh copy before
  extensive use.  Joachim Schrod indicates that these files may be
  updated daily and can be retrieved via anonymous ftp at
  LPA/documentation.



  14.  Other Opinions about Literate Programming



  14.1.  van Ammers

  An author (Eric W. van Ammers) wrote me a short article treating his
  opinions on literate programming.

  First observation on LP

  About 90% of the disussion on this list is about problems with
  applying some WEB-family member to a particular programming language
  or a special documentation situation.  This is ridiculous, I think.
  Let me explain shortly why.

  Lemma 1:

  I have proposed for many years that programming has nothing to do 
with
  programming langauges, i.e. a good programmer makes good programs in
  any language (given some time to learn the syntax) and a bad
  programmer will never make a good program, no matter the language he
  uses (today many people share this view, fortunately).

  Lemma 2:

  Literate Programming has (in a certain way not yet completely
  understood) to do with essential aspects of programming.


  Conclusion 1:

  A LP-tool should be independent of programming language.

  Lemma 3:

  It seems likely that the so called BOOK FORMAT PARADIGM [ref. 1] 
plays
  an important role in making literate programs work.

  Lemma 4:

  There are very many documentation systems currently being used to
  produce documents in the BOOK FORMAT.

  Conclusion 2:

  A LP-tool should be independent of the documentation system that the
  program author whishes to use.

  My remark some time ago that we should discuss the generic 
properties
  of an LP-tool was based on the above observation.

  References:

  [1] Paul W. Oman and Curtus Cook. ``Typographical style is more than
  cosmetic.''  CACM 33, 5, 506-520 (May 1990)

  Second observation on LP

  The idea of a literate program as a text book should be extendend 
even
  further. I would like to see a literate program as an (in)formal
  argument of the correctness of the program.

  Thus a literate program should be like a textbook on mathematicics. 
 A
  mathematical textbook explains a theory in terms of lemma and
  theorems. But the proofs are never formal in the sense that they are
  obtaind by symbol manipulation of a proof checker. Rather the proofs
  are by so called ``informal rigour'', i.e. by very precise and
  unambiguous sentences in a natural language.

  Eric W. van Ammers <ammers@rcl.wau.nl>



  14.2.  Ramsey

  Another author (Norman Ramsey) wrote me and asked that his opinions 
be
  included in the FAQ.  What follows are Norman's comments verbatim.

  I see it's time for the ``how is literate programming different from
  verbose commenting'' question.  Perhaps David Thompson will get this
  into the FAQ.  Alert! What follows are my opinions.  In no way do I
  claim to speak for the (fractious) literate-programming community.

  How is literate programming different from verbose commenting?

  There are three distinguishing characteristics.  In order of
  importance, they are:

  1. flexible order of elaboration

  2. automatic support for browsing

  3. typeset documentation, especially diagrams and mathematics


  Flexible order of elaboration means being able to divide your source
  program into chunks and write the chunks in any order, independent 
of
  the order required by the compiler.  In principle, you can choose 
the
  order best suited to explaining what you are doing.  More subtly, 
this
  discipline encourages the author of a literate program to take the
  time to consider each fragment of the program in its proper sphere,
  e.g., not to rush past the error checking to get to the ``good
  parts.'' In its time and season, each part of the program is a good
  part. (This is the party line; your mileage may vary.)

  I find the reordering most useful for encapsulating tasks like input
  validation, error checking, and printing output fit for humans --- 
all
  tasks that tend to obscure ``real work'' when left inline.  
Reordering
  is less important when using languages like Modula-3, which has
  exceptions and permits declarations in any order, than when using
  languages like C, which has no exceptions and requires declaration
  before use.

  Automatic support for browsing means getting a table of contents,
  index, and cross-reference of your program.  Cross-reference might 
be
  printed, so that you could consult an index to look up the 
definition
  of an identifier `foo'.  With good tools, you might get a printed
  mini-index on every page if you wanted.  Or if you can use a 
hypertext
  technology, cross-reference might be as simple as clicking on an
  identifier to reach its definition.

  Indexing is typically done automatically or `semi-automatically', 
the
  latter meaning that identifier definitions are marked by hand.
  Diligently done semi-automatic indexes seem to be best, because the
  author can mark only the identifiers he or she considers important,
  but automatic indexing can be almost as good and requires no work.
  Some tools allow a mix of the two strategies.

  Some people have applied literate-programming tools to large batches
  of legacy code just to get the table of contents, index, and cross-
  reference.

  I don't use diagrams and mathematics very often, but I wouldn't want
  to have to live without them.  I have worked on one or two projects
  where the ability to use mathematical formulae to document the 
program
  was indispensible.  I also wouldn't like to explain some of my
  concurrent programs without diagrams.  Actually I write almost all 
of
  my literate programs using only sections headers, lists, and the
  occasional table.


      >Wouldn't it be easier to do one's literate programming using
      >a wysiwyg word processor (e.g. Word for Windows) and
      >indicate what is source code by putting it in a different
      >font?



  The data formats used in wysiwyg products are proprietary, and they
  tend to be documented badly if at all.  They are subject to change 
at
  the whim of the manufacturer. (I'll go out on a limb and say there 
are
  no significant wysiwyg tools in the public domain.  I hope the 
Andrew
  people will forgive me.) These conditions make it nearly impossible 
to
  write tools, especially tools that provide automatic indexing and
  cross-reference support.  The CLiP people have a partial solution 
that
  works for tools that can export text --- they plant tags and
  delimiters throughout the document that enable the reordering
  transformation (``tangling'').

  People use TeX, roff, and HTML because free implementations of these
  tools are widely available on a variety of platforms.  TeX and HTML
  are well documented, and TeX and roff are stable.  TeX is the most
  portable.  I think I have just answered the FAQ ``how come all these
  tools use TeX, anyway?'' :-)

  Norman Ramsey



  14.3.  My (Dave Thompson's) Experience

  In contrast to Eric's and Norman's comments, I'd like to interject
  from an anecdotal perspective.

  I first ran across the idea of literate programming in 1992 while
  poking around George Greenwade's TeX archive (at niord.shsu.edu) and
  stumbling on some of the tools.  My first experience was tinkering
  with cnoweb, see Section ``cnoweb''.  I used cnoweb to document a
  simple Bernoulli equation toy I built (in C) while working on a one-
  dimensional hydrodynamic model (in Fortran).  I was convinced that
  literate programming had promise (although cnoweb really qualifies 
as
  a pretty-printing tool).

  After reading Sewell's book, I kept hunting through the tools
  available until I found things that worked for me.  (More here as I
  have time to develop the story.)



  14.4.  Others

  I recently received email from Dave Johnson <scope@faroc.com.au> 
about
  his work developing language independent techniques.  The web site 
is
  www.dscope.com.au.



  15.  How to anonymously ftp

  Pretty much everything mentioned here is available by anonymous FTP.
  FAQ lists cross-posted to news.answers and rec.answers can be gotten
  from rtfm.mit.edu [18.181.0.24], under /pub/usenet/news.answers or
  under /pub/usenet/more.specific.group.name

  "anonymous FTP" is just a way for files to be stored where anyone 
can
  retrieve them over the Net.    For example, to retrieve the latest
  version of the literate programming FAQ, do the following:

  > ftp rtfm.mit.edu              /* connect to the site; message 
follows */
  > anonymous                     /* type this when it asks for your 
name */
  > <your email address>          /* type your address as the 
password    */
  > cd /pub/usenet                /* go to the directory you want to 
be   */
  > cd comp.programming.literate  /* one level down (no slash).       
    */
  > dir                           /* look at what's there             
    */
  > get literate-progamming-faq   /* get the file; case-sensitive     
    */
  > quit                          /* stop this mysterious thing       
    */


  If your FTP program complains that it doesn't know where the site 
you
  want to use is, type the numerical address instead of the sitename:

  > ftp 18.181.0.24               /* connect with numerical address */


  If you don't have ftp access, send e-mail to mail-server@rtfm.mit.ed
u
  with the single word "help" in the body of the message.

  Getting binary files (executables, or any compressed files) is only
  slightly more difficult.   You need to set binary mode inside FTP
  before you transfer the file.

  > binary            /* set binary transfer mode  */
  > ascii             /* set back to text transfer mode */


  FAQs and spoiler lists are generally ascii files; everything else is
  generally binary files.

  Some common extensions on binary files in archive sites are:

    .Z           Compressed; extract with uncompress
    .tar.Z       Compressed 'tape archive'; uncompress then untar or 
tar -xvf
    .gz or .z    Gnu gzip; use gunzip (available from 
prep.gnu.ai.mit.edu)
    .sit         (Mac) StufIt archive
    .zip         Extract with Zip or Unzip
    .zoo         Yet another archive/compress program
    .lhe         (Amiga) ?
    .lzh         Lha archive program.
    .arj         (PC) Arj archive program.
    .exe         (PC) Sometimes self-extracting archives-just execute 
them.
    .uue or .UUE Transfer as text file; use uudecode to convert to 
binary
    .hqx         (Mac) BinHex format; transfer in text mode


  Generic help can be found in the FAQs of comp.binaries.  <your_sys-
  tem_type> for how to transfer, extract, and virus-check binary 
files.
  (At rtfm.mit.edu)

  If you can't FTP from your site, use one of the following 
ftp-by-mail
  servers:

    ftpmail@decwrl.dec.com
    ftpmail@src.doc.ic.ac.uk
    ftpmail@cs.uow.edu.au
    ftpmail@grasp.insa-lyon.fr


  For complete instructions, send a message reading "help" to the
  server.

  If you don't know exactly what you're looking for, or exactly where 
it
  is, there are programs and servers that can help you.  For more 
info,
  send e-mail to mail-server@rtfm.mit.with with the body of the 
message
  reading send usenet/news.answers/finding-sources


  Thanks to Aliza R. Panitz (the "buglady") for this text.  I copied 
it
  verbatim from her post on faq-maintainers with only minor
  modifications.



  16.  Acknowledgements

  This document would not have happened without the help of many 
people.
  George Greenwade was instrumental in establishing the original 
mailing
  list way back in the early '90's (when I first became involved).
  Marcus Speh started one of the early ftp sites and was an active
  participant.  Among them are, Rob Beezer, Joachim Schrod, Piet van
  Oostrum, Ross N. Williams, Nelson H. F. Beebe, and Andrew Johnson.  
We
  wouldn't have literate programming if it wasn't for Donald Knuth and
  TeX.  Certainly, we wouldn't be where we are without the tool
  developers (all credited in their entries above).
  Cesar Bellardini cballard@santafe.com.ar deserves thanks for
  translating the FAQ into Spanish.

  A special thanks to Aliza R. Panitz for the text describing how to
  execute an anonymous ftp for files of interest.

  Any omissions from these acknowledgements should be considered an
  accident on my part.  Furthermore, participants in the
  comp.programming.literate newsgroup all contributed in various
  fashions.  Thank all of you.



  17.  End notes

  This document remains in a state of evolution (although I'm a strict
  creationist! <grin>).  I'm working on the SGML version to improve
  formatting of the resulting documents.  I'm also reorganizing the 
FAQ
  to improve its usability.  Comments are solicited for such
  improvements.  Omission of a particular tool should not be 
considered
  a snub in any sense--simply an error or oversight on my part.