[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
new version of PCL
- To: CommonLoops.pa@Xerox.COM
- Subject: new version of PCL
- From: Gregor.pa@Xerox.COM
- Date: Fri, 16 Feb 90 16:06 PST
- Fcc: BD:>Gregor>mail>outgoing-mail-8.text.newest
- Line-fold: no
There is a new version of PCL on arisia.xerox.com.
(for PARC users it is in ~gregor/pcl)
The *pcl-system-date* for this version is "2/16/90 Rainy Day PCL (beta 3)".
This version fixes all the bugs reported in the past week including:
It does not fix a bug where a generic function with a large number of
EQL methods can create functions which exceed lambda-paramters-limit.
With this version, we begin a new mode of distributing PCL.
Specifically, the /pcl directory now contains a single tarfile which
contains all of the sources for this release. To get this version of
PCL, you should copy this single file (it is called tarfile). Once you
have copied the file, you can use the Unix `tar' progam to extract each
of the individual source files. Do this by saying:
tar -xf tarfile *
where `tarfile' is the name you have given the tarfile in your
One advantage of this is that people who do not have FTP access to
arisia can now use the BITFTP server at Princeton to get access to the
PCL sources. Following are the directions from get-pcl.text. Please
let me know if there are problems with these directions.
*** Using the BITFTP server at Princeton ***
For people who can't FTP from Internet (Arpanet) hosts, but who have
mail access to the BITNET, there exists a way to get the PCL files using
the BITFTP service provided by Princeton Univerity. If you know exactly
where to find the files that interest you, this is quite easy. In
particular, you have to know:
* the Internet host name of the host that maintains the files (such
* the directory where to find the files, relative to the root of the
FTP tree (i.E. `pub')
* whether the files are binary or ASCII text.
* the names of the files (say `pcl90.tar.Z' and `pcl90.README')
To do this, send a message to BITFTP@PUCC (or BITFTP@PUCC.BITNET if you
aren't on BITNET itself). The subject line of the message will be
ignored. The text (body) of the message should be:
FTP arisia.xerox.com UUENCODE
Then you wait (probably for about a day when you are in Europe) and
eventually you will receive E-Mail messages from BITFTP@PUCC (or
BITFTP2%PUCC...) with subject lines like `uudecoded file tarfile part
13'. Then you have to carefully concatenate the contents of ALL of
these files in the correct order.
Note: The following works on our Suns and should work on any
Berkeley UNIX machine. If you don't have the `compress' or `zcat'
program, you can get a free version (with MIT's X Window System
distribution, for example).
The resulting file can be `uudecode'd like this:
dagobert% uudecode name-of-the-assembled-file
This will give you a file tarfile.Z (it may actually have a different
name; then you may want to rename it in the first place). The `.Z' at
the end means that the file you now have is compressed. You can
uncompress it with `uncompress tarfile. You can untar the uncompressed
file with `tar xvf tarfile.
This will write all files in the tarfile to the current directory.
If you want to know more about the BITFTP service, send a letter to
`BITFTP@PUCC' that contains the single line `HELP'.