|
|
1.1 root 1: Standard ML of New Jersey
2: Version 0.44, 4 December 1989
3:
4: by Andrew Appel and David MacQueen
5:
6: with contributions from
7:
8: Bruce Duba Trevor Jim James O'Toole
9: Norman Ramsey John Reppy Nick Rothwell
10: James Mattson Kevin Mitchell David Tarditi
11: Mads Tofte Peter Weinberger
12:
13: ------------------------------------------------
14:
15: STANDARD ML OF NEW JERSEY COPYRIGHT NOTICE, LICENSE AND DISCLAIMER.
16:
17: Copyright 1989 by AT&T Bell Laboratories
18:
19: Permission to use, copy, modify, and distribute this software and its
20: documentation for any purpose and without fee is hereby granted,
21: provided that the above copyright notice appear in all copies and that
22: both the copyright notice and this permission notice and warranty
23: disclaimer appear in supporting documentation, and that the name of
24: AT&T Bell Laboratories or any AT&T entity not be used in advertising
25: or publicity pertaining to distribution of the software without
26: specific, written prior permission.
27:
28: AT&T disclaims all warranties with regard to this software, including
29: all implied warranties of merchantability and fitness. In no event
30: shall AT&T be liable for any special, indirect or consequential
31: damages or any damages whatsoever resulting from loss of use, data or
32: profits, whether in an action of contract, negligence or other
33: tortious action, arising out of or in connection with the use or
34: performance of this software.
35:
36: ------------------------------------------------
37:
38: This file describes the latest release of the Standard ML of New
39: Jersey compiler. The main changes relative to previous versions are
40: described in the file doc/NEWS. This is a preliminary version that
41: supports almost the entire Standard ML language with few bugs. We
42: hope to release Version 1 of the compiler at the end of 1989.
43:
44: We are eager to receive your bug reports, comments, and constructive
45: criticism. The documentation is still in a primitive state, but your
46: comments on the installation instructions and manual would be
47: appreciated. Any error message beginning with "Compiler bug"
48: definitely indicates a bug in the compiler and should be reported.
49: Please use an appropriate variation on the bug reporting form in the
50: file doc/bug.form and send comments and bug reports to:
51:
52: David MacQueen
53: Room 2C-322
54: AT&T Bell Laboratories
55: Murray Hill, NJ 07974
56: USA
57: phone: 201-582-7691
58: email: [email protected]
59:
60: Instructions for installing the compiler are in the file doc/INSTALL.
61:
62: Format of the Distribution
63:
64: The compiler is being distributed in two forms: (1) as a tar file on
65: tape, and (2) as a set of compressed tar files accessible by anonymous ftp
66: from the host princeton.edu, directory /usr/ftp/pub/ml.
67:
68: 1. Tape distribution
69:
70: Extracting the contents of the tape using tar -x yields a single directory
71: named mldist. The contents of mldist are as follows (as printed by ls -F):
72:
73: README lib/ mo.ns32/ mo.vax/
74: doc/ mo.m68/ mo.sparc/ src/
75:
76: README (this file) contains some general information on the current release.
77:
78: The mo.vax, mo.m68, mo.ns32, and mo.sparc directories contain the Vax, Motorola
79: MC68020, National Semiconductor 32000, and SPARC object files for the compiler.
80:
81: The src directory contains the source code of the compiler.
82:
83: lib contains contributed software. At the moment, this consists of
84: a lexical analizer generator (lib/lexgen), a parser generator
85: (lib/mlyacc), a code generator generator (lib/mltwig), and a gnu emacs
86: major editing mode (lib/emacs).
87:
88: The doc directory contains a number of documentation files for installing and
89: using the compiler:
90:
91: INSTALL directions for installing the interactive Standard ML system.
92:
93: BATCHINSTALL directions for using the interim batch system and bootstrapping
94: the compiler.
95:
96: NEWS general information on changes and new features. A number of
97: important features of the compiler are documented only in this
98: file, alas.
99:
100: users a mailing list of current site contacts. Please inform us of
101: any updates or corrections.
102:
103: help hints for beginners on using the system.
104:
105: differences a (partial, out of date) list of differences between Standard
106: ML of New Jersey and the Edinburgh compiler.
107:
108: weak-types a very brief explanation of weak type variables.
109:
110: callcc an explanation of the new callcc primitives.
111:
112: profiling an explanation of how to use the profiling facilities.
113:
114: optimize hints on making your programs run faster
115:
116: localspec comments on "local" specifications in signatures
117:
118: bugs current list of known bugs (please check this before submitting
119: bug reports).
120:
121: bug.form suggested format for bug reports.
122:
123: refman/ LaTeX sources for an incomplete, provisional reference manual.
124:
125: examples/ A collection of example programs. We would like to collect
126: additional examples contributed by users. Please mail your
127: example programs to [email protected].
128:
129: papers/ source files (troff -ms or TeX) for papers describing the compiler.
130:
131:
132: 2. Ftp distribution
133:
134: To obtain the compiler by internet ftp, connect to host princeton.edu
135: use login id "anonymous" with your name as password, and go to directory
136: pub/ml ("cd pub/ml"). Then put ftp in binary mode ("binary") and "get"
137: the relevant files in that directory. An alternate site is research.att.com,
138: directory "dist/ml".
139:
140: Host: Net Address: Login: Passwd: Directory:
141: princeton.edu 128.112.128.1 anonymous Your name pub/ml
142: research.att.com 192.20.225.2 anonymous Your name dist/ml
143:
144: The directory pub/ml (dist/ml on research.att.com) contains a
145: zero-length file named VERSION-0.44 indentifying the version, an ascii
146: file named README that describes the current release and the following
147: compressed tar files:
148:
149: doc.tar.Z : the doc directory containing documentation
150: src.tar.Z : the src directory containing source code
151: lib.tar.Z : the lib directory containing contributed software
152: mo.m68.tar.Z : the mo.m68 directory of m68 object files
153: mo.vax.tar.Z : the mo.vax directory of vax object files
154: mo.sparc.tar.Z : the mo.sparc directory of sparc object files
155: mo.ns32.tar.Z : the mo.ns32 directory of NS32k object files
156:
157: You need only transfer the mo.*.tar.Z files that you need for your
158: machines (e.g. mo.m68.tar.Z for Sun 3, NeXT, etc., mo.vax.tar.Z for
159: Vax). The pub/ml (dist/ml) directory may also contain directories
160: with development versions of the compiler that contain a version
161: number followed by the letter "d". These files are made available for
162: development work and are liable to be even more flakey than the normal
163: beta releases.
164:
165: ***************************************************************************
166: NOTE: Ftp should be put into binary mode before transferring the compressed
167: tar files.
168: ***************************************************************************
169:
170: Here is a sample dialog:
171:
172: ftp
173: ftp> open princeton.edu [research.att.com]
174: Name: anonymous
175: Password: <your name>
176: ftp> binary
177: ftp> cd pub/ml [dist/ml]
178: ftp> get README
179: ftp> get src.tar.Z
180: ftp> get lib.tar.Z
181: ftp> get doc.tar.Z
182: ftp> get mo.m68.tar.Z
183: ftp> get mo.vax.tar.Z
184: ftp> close
185: ftp> quit
186:
187: After the files are transferred they should be uncompressed using the
188: uncompress command and then extracted using tar into a directory
189: called mldist. It may not be necessary to transfer all the files; if
190: you do not intend to run the compiler on a Vax, for instance, there is
191: no need to get the mo.vax.tar.Z file.
192:
193: For example:
194:
195: mkdir mldist
196: mv src.tar.Z mldist
197: cd mldist
198: uncompress -c src.tar.Z | tar xf -
199:
200: will unpack the src directory.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.