oz@yetti.UUCP (Ozan Yigit) (12/17/86)
A chess program from UCLA (Stuart CraigCraft), now a part of Free Software Foundation distribution, is available under yetti!/usr/spool/uucppublic. The program comes with special front-ends for X-windows and SunTools, some other experimental stuff, an opening book, and miscellaneous other facilities. Those sites with no links to yetti: please contact me (yetti!oz) for a guest uucp account. -rw-r--r-- 1 oz 614774 Dec 17 11:31 ~uucp/gnuchess.tar.Z The tar file is compressed using 12 bits. Note: The program carries Free Software Foundation public-distribution copyright. enjoy.. oz -- The best way to have a Usenet: [decvax|ihnp4]!utzoo!yetti!oz good idea is to have a Bitnet: oz@[yusol|yuyetti].BITNET lot of ideas. Phonet: [416] 736-5053 x 3976
oz@yetti.UUCP (Ozan Yigit) (12/19/86)
A Scheme interpreter from MIT, written in C, is available
under yetti!/usr/spool/uucppublic. This interpreter is the
one distributed in FSF tape, Copyright MIT.
CScheme (as it is called) is meant to run under UNIX or VMS.
It comes with a revised Scheme report, several development
environments, the contents of A&S&S's book (Structure and
Interpretation of Computer Programs), and other goodies.
[The report may or may not be printable. MIT use their OWN
tex macros, and I cannot locate these macros in *any* tex
distribution I have looked at.. sigh !! But at least, they
included a dvi file.]
******
Before you decide to pick this thing up, make sure to read
the installation document included with this posting.
******
PLEASE: pick this thing up only after-hours, or during the
weekend.
Those sites with no links to yetti: please contact me
(yetti!oz) for a guest uucp account. [Provided that you
know of no neighboring site that has already picked it up]
-rw-r--r-- 1 root 1575545 Dec 18 12:16 ~uucp/scheme.tar.Z
The tar file is compressed using 12 bits.
Performance of the interpreter: ????. We do not yet have
comperative benchmarks.
Acknowledgements: UofT folks were kind enough to pass me
a copy.
enjoy. oz
----- INSTALLATION DOCUMENT for CScheme -----------------
READ THIS FILE FIRST, then
o Read Install.unx for more information on how to install CScheme
under Unix.
o Read Install.vms for more information on how to install CScheme
under VMS.
Known problems:
- Do not try to bring up CScheme on machines on which C longs
are less than 32 bits unless you are willing to put weeks of work into
it. We're not even sure it is feasible without major redesign.
- If your machine does not use the ASCII character encoding,
you may be in for serious trouble. The code in a few places does
explicit ASCII case conversions, and although we plan to remove all
such dependencies, we have not yet done it. In particular, the file
string.c is known to have this problem.
- The bignum (infinite(?) precision integers) code may have problems
due to unsigned declarations being dropped by compilers (in addition
to any coding and algorithmic bugs, which bignum code is notorious
for). If you have problems with unsignedness/overflow, you may want
to try forcing it to use characters as digits rather than shorts.
Look at bignum.h.
If your machine is not one of the supported ones, you manage to get
CScheme up on it, and would like to have an easier time with the next
release, please let us know, and send us the modified files so that we
can incorporate your changes into the released sources.
IF YOU ARE RUNNING NEITHER UNIX NOR VMS ...
... you will have to do some extra work. The files Install.unx and
Install.vms may be of some help, but you'll have to filter out the
information which you can use.
Look for the file config.dst. (If the scheme directory has
subdirectories corresponding to the unix hierarchy, it should be in
the microcode subdirectory). Edit it as appropriate for your machine
and save it as config.h (the file Install.unx gives an overview, and
config.dst contains a detailed explanation of each definition).
Follow the installation procedure explained in Install.vms, after
modifying all the ".com" files to fit your command interpreter and
system. "@ing" a file on VMS means to give it as input to the
command interpreter ("SOURCEing" a file on the Unix C-shell, or
"TAKEing" a file on TOPS-20).
Note that scheme will use the unknown.c operating system file. Among
other things, this means that there will be no interrupt characters,
no immediate IO, and a fair amount of operating system dependent
procedures (time, date, file manipulation, etc.) will be missing.
If they can be implemented on your system and you feel up to the task,
you can use unix.c and vms.c for guidance.
If you run into problems not described above, get in touch with us
(see README) and we may be able to help. Good luck!
--
The best way to have a Usenet: [decvax|ihnp4]!utzoo!yetti!oz
good idea is to have a Bitnet: oz@[yusol|yuyetti].BITNET
lot of ideas. Phonet: [416] 736-5053 x 3976