wegrzyn@cdx39.UUCP (Chuck Wegrzyn) (11/14/86)
Can anyone tell me how I would go about getting Kyoto Common Lisp? Any help would be greatly appreciated.
dls@tropix.UUCP (David L. Snyder ) (11/17/86)
In article <473@cdx39.UUCP> wegrzyn@cdx39.UUCP (Chuck Wegrzyn) writes: > > Can anyone tell me how I would go about getting Kyoto Common Lisp? >Any help would be greatly appreciated. For those who haven't found out already, KCL is available from: Ibuki 399 Main Street Los Altos, CA 94022 (415) 949-1126 Henson Graves is the person you want to speak with. The prices are $700 for objects and $700 for complete sources. Object code is available for Vaxen, Suns, Apollos, and a few others. KCL is used by enough folks that some public domain tools support it; specifically, Xerox's Portable CommonLoops will run under KCL. I don't have any first hand experience with KCL (yet). It was originally done at Kyoto University, by Taiichi Yuasa and Masami Hagiya in the Research Institute for Mathematical Sciences, and is supposedly quite clean and portable. It'd be great to hear from someone with real experience, especially concerning performance. David Snyder
felix@lifia.UUCP (Francois Felix INGRAND) (11/20/86)
In article <227@tropix.UUCP> dls@tropix.UUCP (David L. Snyder ) writes: >In article <473@cdx39.UUCP> wegrzyn@cdx39.UUCP (Chuck Wegrzyn) writes: >> >> Can anyone tell me how I would go about getting Kyoto Common Lisp? > > Ibuki > 399 Main Street > Los Altos, CA 94022 > (415) 949-1126 >is supposedly quite clean and portable. > >It'd be great to hear from someone with real experience, especially >concerning performance. > >David Snyder Here, at lifia, we use KCL since more than one year. Now our release must be out of date, but the features of this CL are: - It is quite clean, but we have found small bugs here and there (not really important, indeed for the soft I write). - It seems to be portable, My soft must run on KCL, VAXLISP (DEC) and I never had any problems to port from one to the over (no experience with other CL). - The compilation are VERY SLOW. Perhaps it is because the lisp is transformed in C then in code, but I think that this the major problem of this CL. - The execution is not very fast to, but with the test I have made, It seems to be the same speed than VAXLISP (but many people said me that VAXLISP was not considered as a fast CL). - The garbage collecting seems to be "better" than those of VAXLISP (VAXLISP GC stop for a very long time), in KCL, it is not more discret... - It was not expensive, and it was one of the first CL on Unix (VAX). Just one point. When we bought it, I asked it directly to Hagiya and Yuasa at the Research Institute for Mathematical Sciences of Kyoto, and I remember that it was not so expensive, but perhaps it is because we are Academic group. -- Felix -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Francois Felix INGRAND (-: Pourquoi tant de haine... :-( \ | / UUCP: ...{mcvax,inria}!lifia!felix EDIKA \|/ > ...{mcvax,inria}!imag!felix ( O: ) /|\ > Disclaimer: The views and opinions expressed here are mine... / | \ Please don't tell my employer...
AI.BOYER@MCC.COM (Bob Boyer) (06/23/87)
Kyoto Common Lisp (KCL) is a complete implementation of Common Lisp written by T. Yuasa and M. Hagiya working under Professor R. Nakajima at the Research Institute for Mathematical Sciences, Kyoto University. It runs on many different machines and is highly portable. It executes very efficiently and it is superbly documented. KCL is being made available at no fee through the implementors' generosity. The complete sources are included. One channel of distribution is via ftp on the Arpanet/Internet. LICENSE REQUIRED! IMPORTANT: Although there is no fee, KCL is not in the public domain. You are authorized to obtain it only after signing and mailing in a license agreement. Before you ftp KCL files you MUST fill out and send in the license agreement included in this message. Otherwise, you are not permitted to make copies of KCL. COPYING KCL VIA INTERNET KCL may be obtained from Internet source rascal.ics.utexas.edu [128.83.144.1], a Sun-3 at the University of Texas at Austin. To obtain KCL, login as "ftp" with password "guest". There are three tar files: /pub/kcl.tar, 4.0 megabytes /pub/kcl.tar.C, produced by compact from kcl.tar, 2.8 megabytes /pub/kcl.tar.Z, produced by compress from kcl.tar, 1.2 megabytes Any of the three files is sufficient to generate KCL. Please ftp the compressed file if possible. Please use ftp at an odd hour if possible to reduce traffic on a sometimes heavily loaded network. Be sure to use binary mode with ftp. A current version of this message may be found as the file /pub/kcl.broadcast. MACHINES ON WHICH KCL RUNS KCL runs on many machines. With the sources provided in the ftp file, KCL may be executed on the following machines (and operating systems). VAX/UNIX (4.2BSD) SUN2 (OS2, 3) SUN3 (OS3) SONY'S NEWS (4.2BSD) ATT3B2 (System V) Fujitu S3000 (System V) Sumitomo's E15 (Uniplus System V) Data General MV (DGUX) Instructions for making the system are in the file doc/porting in the ftp tar file. KCL LICENSE FORM To obtain the right to copy KCL, sign this license form and send it and a copy to the Kyoto address at the end of the form. ONCE YOU HAVE MAILED THE SIGNED LICENSE FORM, YOU MAY COPY KCL. YOU DO NOT HAVE TO WAIT FOR RECEIPT OF THE SIGNED FORM. --------------------------- cut here ---------------------------- LICENSE AGREEMENT FOR KYOTO COMMON LISP The Special Interest Group in LISP (Taiichi Yuasa and Masami Hagiya) at the Research Institute for Mathematical Sciences, Kyoto University (hereinafter referred to as SIGLISP) grants to USER NAME: _________________________________________ USER ADDRESS: ______________________________________ ______________________________________ (hereinafter referred to as USER), a non-transferable and non-exclusive license to copy and use Kyoto Common LISP (hereinafter referred to as KCL) under the following terms and conditions and for the period of time identified in Paragraph 6. 1. This license agreement grants to the USER the right to use KCL within their own home or organization. The USER may make copies of KCL for use within their own home or organization, but may not further distribute KCL except as provided in paragraph 2. 2. SIGLISP intends that KCL be widely distributed and used, but in a manner which preserves the quality and integrity of KCL. The USER may send a copy of KCL to another home or organization only after either receiving permission from SIGLISP or after seeing written evidence that the other home or organization has signed this agreement and sent a hard copy of it to SIGLISP. If the USER has made modifications to KCL and wants to distribute that modified copy, the USER will first obtain permission from SIGLISP by written or electronic communication. Any USER which has received such a modified copy can pass it on as received, but must receive further permission for further modifications. All modifications to copies of KCL passed on to other homes or organizations shall be clearly and conspicuously indicated in all such copies. Under no other circumstances than provided in this paragraph shall a modified copy of KCL be represented as KCL. 3. The USER will ensure that all their copies of KCL, whether modified or not, carry as the first information item the following copyright notice: (c) Copyright Taiichi Yuasa and Masami Hagiya, 1984. All rights reserved. Copying of this file is authorized to users who have executed the true and proper "License Agreement for Kyoto Common LISP" with SIGLISP. 4. Title to and ownership of KCL and its copies shall at all times remain with SIGLISP and those admitted by SIGLISP as contributors to the development of KCL. The USER will return to SIGLISP for further distribution modifications to KCL, modifications being understood to mean changes which increase the speed, reliability and existing functionality of the software delivered to the USER. The USER may make for their own ownership and use enhancements to KCL which add new functionality and applications which employ KCL. Such modules may be returned to SIGLISP at the option of the USER. 5. KCL IS LICENSED WITH NO WARRANTY OF ANY KIND. SIGLISP WILL NOT BE RESPONSIBLE FOR THE CORRECTION OF ANY BUGS OR OTHER DEFICIENCIES. IN NO EVENT SHALL SIGLISP BE LIABLE FOR ANY DAMAGES OF ANY KIND, INCLUDING SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF KCL. 6. This license for KCL shall be effective from the date hereof and shall remain in force until the USER discontinues use of KCL. In the event the USER neglects or fails to perform or observe any obligations under this Agreement, this Agreement and the License granted hereunder shall be immediately terminated and the USER shall certify to SIGLISP in writing that all copies of KCL in whatever form in its possession or under its control have been destroyed. 7. Requests. KCL is provided by SIGLISP in a spirit of friendship and cooperation. SIGLISP asks that people enjoying the use of KCL cooperate in return to help further develop and distribute KCL. Specifically, SIGLISP would like to know which machines KCL gets used on. A brief notice form is appended to this agreement which the user is requested to send by email or otherwise. Please send in further notifications at reasonable intervals if you increase the number and type of machines on which KCL is loaded. You may send these notices to another USER which is cooperating with SIGLISP for this purpose. USER DATE: _________________________________________ BY: ___________________________________________ TITLE: ________________________________________ ADDRESS: ______________________________________ ______________________________________ SIGLISP DATE: _________________________________________ BY: ___________________________________________ Taiichi Yuasa Masami Hagiya Special Interest Group in LISP Research Institute for Mathematical Sciences Kyoto University Kyoto, 606, JAPAN Telex: 05422020 RIMS J JUNET: siglisp@kurims.kurims.kyoto-u.junet CSNET: siglisp%kurims.kurims.kyoto-u.junet@utokyo-relay.csnet USER has loaded KCL on the following machines since (date): Model Number Production Name Number of Machines END OF LICENSE FORM --------------------------- cut here ------------------------ DOCUMENTATION The principal documentation for KCL is, of course, the book "Common Lisp The Language" by Guy L. Steele, Jr. with contributions by Scott E. Fahlman, Richard P. Gabriel, David A. Moon, and Daniel L. Weinreb, Digital Press, 1984. Implementation-specific details of KCL (debugging, garbage collection, data structure format, declarations, operating system interface, installation) may be found in the 131 page "Kyoto Common Lisp Report" by Taiichi Yuasa and Masami Hagiya, the authors of KCL. This report is available from: Teikoku Insatsu Inc. Shochiku-cho, Ryogae-cho-dori Takeya-machi Sagaru, Naka-gyo-ku, Kyoto, 604, Japan tel: 075-231-4757 for 5,000 yen plus postage. The KCL Report is produced by the text-formatter KROFF (Kyoto ROFF), which is used locally within Kyoto University. Currently KROFF works only on printers available in Japan. It is possible that an American distributorship of this report will be arranged. The source of the report, with KROFF commands, is found in the file doc/report on the ftp tar file. It is possible to read this source, though it is as hard on the eyes as TeX or Scribe source. A translation of this source into TeX is underway and will be available as part of the distribution tape. Future information about the availability of the KCL Report will be available in updated versions of this message, in the file /pub/kcl.broadcast. A document describing how to port KCL to other systems is available at no charge from the authors of KCL. Each of the KCL primitives is thoroughly described by the "describe" function, which is based on 340K bytes of documentation. SUPPORT KCL is one of the most bug-free large software systems that we have ever used. However, when bugs are found, they may be reported to the implementors: hagiya%kurims.kurims.kyoto-u.junet%utokyo-relay.csnet@RELAY.CS.NET yuasa%kurims.kurims.kyoto-u.junet%utokyo-relay.csnet@RELAY.CS.NET We have found them extremely responsive to bug reports and suggestions. SAMPLE TRANSCRIPT Below is a complete transcript for obtaining and installing KCL on a Sun-3. Make a directory for locating KCL tutorial% mkdir /usr/joe/kcl Get the compressed tar file tutorial% cd /usr/joe/kcl tutorial% ftp 128.83.144.1 220 rascal FTP server (Version 4.7 Sun Sep 14 12:44:57 PDT 1986) ready. Name: ftp Password: guest ftp>binary ftp>get /pub/kcl.tar.Z kcl.tar.Z ftp>quit Build the KCL directory structure tutorial% uncompress kcl.tar.Z tutorial% tar -xvf kcl.tar . tutorial% rm kcl.tar Make KCL tutorial% cd /usr/joe/kcl/ tutorial% su password: super-user-password tutorial# cp h/cmpinclude.h /usr/include tutorial# exit tutorial% make Edit and Install Two Files We wish to replace "~" by "/usr/joe" in lc and kcl, and put them in a directory on the search path e.g. "/usr/joe/bin" tutorial% cd /usr/joe/kcl/unixport tutorial% mkdir /usr/joe/bin tutorial% sed -e "s.~./usr/joe/kcl.g" lc > /usr/joe/bin/lc tutorial% sed -e "s.~./usr/joe/kcl.g" kcl > /usr/joe/bin/kcl tutorial% chmod a+x /usr/joe/bin/lc /usr/joe/bin/kcl It is now possible to run kcl: tutorial% /usr/joe/bin/kcl KCL (Kyoto Common Lisp) >(+ 2 3) 5 >(bye) It is best to become super user and execute the following commands, so that all users may execute kcl. tutorial% su Password: superuser-password tutorial# cp /usr/joe/bin/kcl /usr/local/bin tutorial# cp /usr/joe/bin/lc /usr/local/bin tutorial# exit This transcript puts the entire kcl system, including sources and documentation, in the directory /usr/joe/kcl. Any other directory name would do as well, e.g., /usr/local instead of /usr/joe. Although this transcript has worked perfectly for us on a Sun-3, it might not work for you if you are running under NFS but not logged into the right machine: you may need to login as root on the system where /usr/include and /usr/local/bin are really located to do the super-user things. Immediately after the make is finished about 8.4 megatyes of disk space are in use. SINCERELY YOURS Robert S. Boyer William F. Schelter cl.boyer@r20.utexas.edu atp.schelter@r20.utexas.edu This message was written by Robert S. Boyer and William F. Schelter. The opinions expressed are theirs and are not necessarily those of the authors of KCL, the University of Texas, or MCC. The authors of KCL have, however, indicated that they have no objection to our distributing this message. P.S. Thanks to Dave Capshaw, George Fann, Warren Hunt, Ken Rimey, and Carl Quillen for helping debug this message. Ken Rimey, rimey@ernie.Berkeley.EDU, makes the following remarks about bringing up this release of KCL under BSD 4.3 on a Vax. 1. Bringing up KCL under BSD4.3. The machine on which I installed kcl was a Vax 88xx running Ultrix V2.0. Kcl crashed when executing the final save-system command in init_kcl.lsp. It also did so on a Vax running BSD4.3. (I don't know of any Vaxen still running 4.2.) The problem is caused by some highly non-portable code introduced into Lsave() in c/unixsave.c since the version of March 28, 1986. I deleted the new code and reintroduced the old which had been commented out. Here is the resulting working Lsave(): Lsave() { char filename[256]; check_arg(1); check_type_or_pathname_string_symbol_stream(&vs_base[0]); coerce_to_filename(vs_base[0], filename); _cleanup(); memory_save(kcl_self, filename); exit(0); /* no return */ } KCL ran successfully after only fixing the Lsave problem. 2. The files o/makefile and unixport/makefile define variables that need to be changed when compiling for any machine other than a Sun-3. These definitions are found at the heads of these files. Here is the head of my copy of o/makefile: MACHINE = VAX # Select 'VAX', 'SUN', 'SUN2R3', 'SUN3', 'ISI', 'SEQ', 'IBMRT', # or 'NEWS'. CHTAB = char_table.s # Select 'char_table.s' or 'sun_chtab.s'. # 1) char_table.s : for VAX, SEQ and NEWS # 2) sun_chtab.s : for SUN, SUN2R3 and SUN3 # 3) isi_chtab.s : for ISI # 4) ibmrt_chtab.s: for IBMRT For machines other than Sun-3, one might change the MAKE KCL section of this message to: tutorial% cd /usr/joe/kcl/ tutorial% vi o/makefile (If not Sun-3, change definitions MACHINE and CHTAB.) tutorial% vi o/unixport (If not Sun-3, change definition of MACHINE.) tutorial% su password: super-user-password tutorial# cp h/cmpinclude.h /usr/include tutorial# exit tutorial% make -------
murphy@astroatc.UUCP (Kathy Murphy) (08/03/87)
We are in the process of selecting a Lisp package to port to a new computer system (target market is NOT the AI community but we would like to have a Lisp compiler and interpreter available on the system). At the moment our choice is limited to either Kyoto Common Lisp or the pd version of FRANZ LISP. KCL appears to be much simpler to port and maintain but we have no idea how potential users view KCL vs pd FRANZ. I would appreciate comments on the following: General experience with KCL. KCL vs pd FRANZ LISP. The importance of Lisp compiler speed - KCL's compiler is very slow. Please mail replies directly to me. If there is enough interest I can summarize results. Thank you. -- Kathleen Murphy ...!uwvax!astroatc!murphy Astronautics Technology Center 5800 Cottage Grove Rd. (608) 221-9001, x137 Madison, WI 53716
kempf@hplabsz.HPL.HP.COM (Jim Kempf) (08/04/87)
Related question: Has anyone ported Kyoto to the AT? Jim Kempf kempf@hplabs.hp.com
hcn1@sphinx.uchicago.edu (howard charles nusbaum) (09/14/87)
We have just set up a MicroVax II with 9 meg of RAM and 150 meg of disk running VMS. First question: Will this configuration run Kyoto Common Lisp? Second question: What do I need to do to get a copy of Kyoto Common Lisp? (Whom do I contact, what amount do I pay, etc etc). Thanks very much for your assistance. Howard C. Nusbaum Department of Behavioral Sciences' The University of Chicago 5848 S. University Ave. Chicago, IL 60637 (312) 702-6468
neves@ai.WISC.EDU (David M. Neves) (09/15/87)
If anyone has successfully put Kyoto Common Lisp on a 4.3 Vax Unix system please tell me how you did it. When I try to MAKE the source I get a memory error as it is loading in the compiler. My makefile constants might be wrong. -Thanks, David David Neves, Computer Sciences Department, University of Wisconsin-Madison Usenet: {allegra,heurikon,ihnp4,seismo}!uwvax!neves Arpanet: neves@cs.wisc.edu
maner@bgsuvax.UUCP (09/17/87)
> > We have just set up a MicroVax II with 9 meg of RAM and 150 > meg of disk running VMS. First question: Will this configuration > run Kyoto Common Lisp? Second question: What do I need to do > to get a copy of Kyoto Common Lisp? (Whom do I contact, what > amount do I pay, etc etc). > Hope this helps: From: CL.BOYER@R20.UTEXAS.EDU Kyoto Common Lisp (KCL) is a complete implementation of Common Lisp written by T. Yuasa and M. Hagiya working under Professor R. Nakajima at the Research Institute for Mathematical Sciences, Kyoto University. It runs on many different machines and is highly portable. It executes very efficiently and it is superbly documented. KCL is being made available at no fee through the implementors' generosity. The complete sources are included. One channel of distribution is via ftp on the Arpanet/Internet. LICENSE REQUIRED! IMPORTANT: Although there is no fee, KCL is not in the public domain. You are authorized to obtain it only after signing and mailing in a license agreement. Before you ftp KCL files you MUST fill out and send in the license agreement included in this message. Otherwise, you are not permitted to make copies of KCL. COPYING KCL VIA INTERNET KCL may be obtained from Internet source rascal.ics.utexas.edu [128.83.144.1], a Sun-3 at the University of Texas at Austin. To obtain KCL, login as "ftp" with password "guest". There are three tar files: /pub/kcl.tar, 4.0 megabytes /pub/kcl.tar.C, produced by compact from kcl.tar, 2.8 megabytes /pub/kcl.tar.Z, produced by compress from kcl.tar, 1.2 megabytes Any of the three files is sufficient to generate KCL. Please ftp the compressed file if possible. Please use ftp at an odd hour if possible to reduce traffic on a sometimes heavily loaded network. Be sure to use binary mode with ftp. A current version of this message may be found as the file /pub/kcl.broadcast. MACHINES ON WHICH KCL RUNS KCL runs on many machines. With the sources provided in the ftp file, KCL may be executed on the following machines (and operating systems). VAX/UNIX (4.2BSD) SUN2 (OS2, 3) SUN3 (OS3) SONY'S NEWS (4.2BSD) ATT3B2 (System V) Fujitu S3000 (System V) Sumitomo's E15 (Uniplus System V) Data General MV (DGUX) Instructions for making the system are in the file doc/porting in the ftp tar file. KCL LICENSE FORM To obtain the right to copy KCL, sign this license form and send it and a copy to the Kyoto address at the end of the form. ONCE YOU HAVE MAILED THE SIGNED LICENSE FORM, YOU MAY COPY KCL. YOU DO NOT HAVE TO WAIT FOR RECEIPT OF THE SIGNED FORM. --------------------------- cut here ---------------------------- LICENSE AGREEMENT FOR KYOTO COMMON LISP The Special Interest Group in LISP (Taiichi Yuasa and Masami Hagiya) at the Research Institute for Mathematical Sciences, Kyoto University (hereinafter referred to as SIGLISP) grants to USER NAME: _________________________________________ USER ADDRESS: ______________________________________ ______________________________________ (hereinafter referred to as USER), a non-transferable and non-exclusive license to copy and use Kyoto Common LISP (hereinafter referred to as KCL) under the following terms and conditions and for the period of time identified in Paragraph 6. 1. This license agreement grants to the USER the right to use KCL within their own home or organization. The USER may make copies of KCL for use within their own home or organization, but may not further distribute KCL except as provided in paragraph 2. 2. SIGLISP intends that KCL be widely distributed and used, but in a manner which preserves the quality and integrity of KCL. The USER may send a copy of KCL to another home or organization only after either receiving permission from SIGLISP or after seeing written evidence that the other home or organization has signed this agreement and sent a hard copy of it to SIGLISP. If the USER has made modifications to KCL and wants to distribute that modified copy, the USER will first obtain permission from SIGLISP by written or electronic communication. Any USER which has received such a modified copy can pass it on as received, but must receive further permission for further modifications. All modifications to copies of KCL passed on to other homes or organizations shall be clearly and conspicuously indicated in all such copies. Under no other circumstances than provided in this paragraph shall a modified copy of KCL be represented as KCL. 3. The USER will ensure that all their copies of KCL, whether modified or not, carry as the first information item the following copyright notice: (c) Copyright Taiichi Yuasa and Masami Hagiya, 1984. All rights reserved. Copying of this file is authorized to users who have executed the true and proper "License Agreement for Kyoto Common LISP" with SIGLISP. 4. Title to and ownership of KCL and its copies shall at all times remain with SIGLISP and those admitted by SIGLISP as contributors to the development of KCL. The USER will return to SIGLISP for further distribution modifications to KCL, modifications being understood to mean changes which increase the speed, reliability and existing functionality of the software delivered to the USER. The USER may make for their own ownership and use enhancements to KCL which add new functionality and applications which employ KCL. Such modules may be returned to SIGLISP at the option of the USER. 5. KCL IS LICENSED WITH NO WARRANTY OF ANY KIND. SIGLISP WILL NOT BE RESPONSIBLE FOR THE CORRECTION OF ANY BUGS OR OTHER DEFICIENCIES. IN NO EVENT SHALL SIGLISP BE LIABLE FOR ANY DAMAGES OF ANY KIND, INCLUDING SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF KCL. 6. This license for KCL shall be effective from the date hereof and shall remain in force until the USER discontinues use of KCL. In the event the USER neglects or fails to perform or observe any obligations under this Agreement, this Agreement and the License granted hereunder shall be immediately terminated and the USER shall certify to SIGLISP in writing that all copies of KCL in whatever form in its possession or under its control have been destroyed. 7. Requests. KCL is provided by SIGLISP in a spirit of friendship and cooperation. SIGLISP asks that people enjoying the use of KCL cooperate in return to help further develop and distribute KCL. Specifically, SIGLISP would like to know which machines KCL gets used on. A brief notice form is appended to this agreement which the user is requested to send by email or otherwise. Please send in further notifications at reasonable intervals if you increase the number and type of machines on which KCL is loaded. You may send these notices to another USER which is cooperating with SIGLISP for this purpose. USER DATE: _________________________________________ BY: ___________________________________________ TITLE: ________________________________________ ADDRESS: ______________________________________ ______________________________________ SIGLISP DATE: _________________________________________ BY: ___________________________________________ Taiichi Yuasa Masami Hagiya Special Interest Group in LISP Research Institute for Mathematical Sciences Kyoto University Kyoto, 606, JAPAN Telex: 05422020 RIMS J JUNET: siglisp@kurims.kurims.kyoto-u.junet CSNET: siglisp%kurims.kurims.kyoto-u.junet@utokyo-relay.csnet USER has loaded KCL on the following machines since (date): Model Number Production Name Number of Machines END OF LICENSE FORM --------------------------- cut here ------------------------ DOCUMENTATION The principal documentation for KCL is, of course, the book "Common Lisp The Language" by Guy L. Steele, Jr. with contributions by Scott E. Fahlman, Richard P. Gabriel, David A. Moon, and Daniel L. Weinreb, Digital Press, 1984. Implementation-specific details of KCL (debugging, garbage collection, data structure format, declarations, operating system interface, installation) may be found in the 131 page "Kyoto Common Lisp Report" by Taiichi Yuasa and Masami Hagiya, the authors of KCL. This report is available from: Teikoku Insatsu Inc. Shochiku-cho, Ryogae-cho-dori Takeya-machi Sagaru, Naka-gyo-ku, Kyoto, 604, Japan tel: 075-231-4757 for 5,000 yen plus postage. The KCL Report is produced by the text-formatter KROFF (Kyoto ROFF), which is used locally within Kyoto University. Currently KROFF works only on printers available in Japan. It is possible that an American distributorship of this report will be arranged. The source of the report, with KROFF commands, is found in the file doc/report on the ftp tar file. It is possible to read this source, though it is as hard on the eyes as TeX or Scribe source. A translation of this source into TeX is underway and will be available as part of the distribution tape. Future information about the availability of the KCL Report will be available in updated versions of this message, in the file /pub/kcl.broadcast. A document describing how to port KCL to other systems is available at no charge from the authors of KCL. Each of the KCL primitives is thoroughly described by the "describe" function, which is based on 340K bytes of documentation. SUPPORT KCL is one of the most bug-free large software systems that we have ever used. However, when bugs are found, they may be reported to the implementors: hagiya%kurims.kurims.kyoto-u.junet%utokyo-relay.csnet@RELAY.CS.NET yuasa%kurims.kurims.kyoto-u.junet%utokyo-relay.csnet@RELAY.CS.NET We have found them extremely responsive to bug reports and suggestions. SAMPLE TRANSCRIPT Below is a complete transcript for obtaining and installing KCL on a Sun-3. Make a directory for locating KCL tutorial% mkdir /usr/joe/kcl Get the compressed tar file tutorial% cd /usr/joe/kcl tutorial% ftp 128.83.144.1 220 rascal FTP server (Version 4.7 Sun Sep 14 12:44:57 PDT 1986) ready. Name: ftp Password: guest ftp>binary ftp>get /pub/kcl.tar.Z kcl.tar.Z ftp>quit Build the KCL directory structure tutorial% uncompress kcl.tar.Z tutorial% tar -xvf kcl.tar . tutorial% rm kcl.tar Make KCL tutorial% cd /usr/joe/kcl/ tutorial% su password: super-user-password tutorial# cp h/cmpinclude.h /usr/include tutorial# exit tutorial% make Edit and Install Two Files We wish to replace "~" by "/usr/joe" in lc and kcl, and put them in a directory on the search path e.g. "/usr/joe/bin" tutorial% cd /usr/joe/kcl/unixport tutorial% mkdir /usr/joe/bin tutorial% sed -e "s.~./usr/joe/kcl.g" lc > /usr/joe/bin/lc tutorial% sed -e "s.~./usr/joe/kcl.g" kcl > /usr/joe/bin/kcl tutorial% chmod a+x /usr/joe/bin/lc /usr/joe/bin/kcl It is now possible to run kcl: tutorial% /usr/joe/bin/kcl KCL (Kyoto Common Lisp) >(+ 2 3) 5 >(bye) It is best to become super user and execute the following commands, so that all users may execute kcl. tutorial% su Password: superuser-password tutorial# cp /usr/joe/bin/kcl /usr/local/bin tutorial# cp /usr/joe/bin/lc /usr/local/bin tutorial# exit This transcript puts the entire kcl system, including sources and documentation, in the directory /usr/joe/kcl. Any other directory name would do as well, e.g., /usr/local instead of /usr/joe. Although this transcript has worked perfectly for us on a Sun-3, it might not work for you if you are running under NFS but not logged into the right machine: you may need to login as root on the system where /usr/include and /usr/local/bin are really located to do the super-user things. Immediately after the make is finished about 8.4 megatyes of disk space are in use. SINCERELY YOURS Robert S. Boyer William F. Schelter cl.boyer@r20.utexas.edu atp.schelter@r20.utexas.edu This message was written by Robert S. Boyer and William F. Schelter. The opinions expressed are theirs and are not necessarily those of the authors of KCL, the University of Texas, or MCC. The authors of KCL have, however, indicated that they have no objection to our distributing this message. P.S. Thanks to Dave Capshaw, George Fann, Warren Hunt, Ken Rimey, and Carl Quillen for helping debug this message. Ken Rimey, rimey@ernie.Berkeley.EDU, makes the following remarks about bringing up this release of KCL under BSD 4.3 on a Vax. 1. Bringing up KCL under BSD4.3. The machine on which I installed kcl was a Vax 88xx running Ultrix V2.0. Kcl crashed when executing the final save-system command in init_kcl.lsp. It also did so on a Vax running BSD4.3. (I don't know of any Vaxen still running 4.2.) The problem is caused by some highly non-portable code introduced into Lsave() in c/unixsave.c since the version of March 28, 1986. I deleted the new code and reintroduced the old which had been commented out. Here is the resulting working Lsave(): Lsave() { char filename[256]; check_arg(1); check_type_or_pathname_string_symbol_stream(&vs_base[0]); coerce_to_filename(vs_base[0], filename); _cleanup(); memory_save(kcl_self, filename); exit(0); /* no return */ } KCL ran successfully after only fixing the Lsave problem. 2. The files o/makefile and unixport/makefile define variables that need to be changed when compiling for any machine other than a Sun-3. These definitions are found at the heads of these files. Here is the head of my copy of o/makefile: MACHINE = VAX # Select 'VAX', 'SUN', 'SUN2R3', 'SUN3', 'ISI', 'SEQ', 'IBMRT', # or 'NEWS'. CHTAB = char_table.s # Select 'char_table.s' or 'sun_chtab.s'. # 1) char_table.s : for VAX, SEQ and NEWS # 2) sun_chtab.s : for SUN, SUN2R3 and SUN3 # 3) isi_chtab.s : for ISI # 4) ibmrt_chtab.s: for IBMRT For machines other than Sun-3, one might change the MAKE KCL section of this message to: tutorial% cd /usr/joe/kcl/ tutorial% vi o/makefile (If not Sun-3, change definitions MACHINE and CHTAB.) tutorial% vi o/unixport (If not Sun-3, change definition of MACHINE.) tutorial% su password: super-user-password tutorial# cp h/cmpinclude.h /usr/include tutorial# exit tutorial% make ------- -- CSNet : maner@research1.bgsu.edu | CS Dept 419/372-2337 UUCP : {cbatt,cbosgd}!osu-cis!bgsuvax!maner | BGSU Generic : maner%research1.bgsu.edu@relay.cs.net | Bowling Green, OH 43403 Opinion : If you are married, you deserve a MARRIAGE ENCOUNTER weekend!
thomas@gmdzi.UUCP (Thomas Gordon) (02/24/88)
I am sure this has been asked before, but I wasn't interested at the time I first saw the information: Could someone please mail me information about Kyoto Common Lisp. In particular, where can we order a copy. Thank you, Tom Gordon thomas@gmdxps
atoenne@laura.UUCP (Andreas Toenne) (04/07/88)
Someone posted an article about Kyoto Common Lisp about a year ago. How much does it cost (I think there was a handling charge only) ? Where can I get a tape/streamer copy ? Are there other *cheap* full Common Lisp implementations ? Thanks in advance, Andreas Toenne atoenne@unido.uucp
pmy@vivaldi.acc.virginia.edu (Pete Yadlowsky) (02/24/89)
We've been struggling off and on for some time trying to get KCL to run on AT&T equipment, specifically, 3B2s and '15s. The kernel has always compiled and executed without problems. But, anything produced with (save) invariably crashed, with a core dump and 'illegal instruction' message. So, I decided to take a peek at the 'save'd image, to see what its sections looked like, particularly the .text section. It didn't look like the kernel's .text section at all. In fact, it looked more like data than code. Then I noticed something peculiar about an #ifdef block in source file unixsave.c. There's an #ifdef ATT3B1 block nested within an #ifdef ATT block. Within that ATT3B1 block, there's a call to 'filecpy', which is supposed to copy the kernel's .text section to the newly-generated image. The implication here is that any AT&T image *not* targeted for a 3B1 would not get a copy of the .text section. Bingo. When I moved the call to 'filecpy' outside the #ifdef ATT3B1 block (still keeping it within the ATT block), everything was fine. We're now running KCL on our 3B2s and '15s (SysV ver 3.0 for the most part). Following is a diff-generated ed script for patching the KCL source file, unixsave.c -------------------------------- cut --------------------------------- 271a filecpy(save, original, header.a_text); . 270d ---------------------------------------------------------------------- Please, please somebody tell me I'm not the last person in the known universe to figure this one out. :-) Geez, what a forehead-slapper. Peter M. Yadlowsky Academic Computing Center University of Virginia pmy@Virginia.EDU
cees@fwi.uva.nl (Cees Bol) (01/24/90)
Hello there, I have a question. I have the sources of Kyoto Common Lisp. There are many machines (Vax, Suns, etc..) on which this Lisp version runs. Only not on my machine... I want to run it on a PowerNode9000 (UTX2.1Bu01) of Encore (Gould). Before I start hacking myself I want to ask if someone else has done it before. Yes? Would you please send me the files or the diffs. Thank very much. Cees Bol. email: cees@fwi.uva.nl University of Amsterdam Faculty of Mathematics and Computer sciences Plantage Muidergracht 24 1018 TV Amsterdam Holland.
molloyt@ul.ie (08/10/90)
Does anyone know where I can get my hand on Kyoto Common Lisp (KCL). I need a licience agreement for KCL in order to purchase the sources for OBJ3, a ADT specification language. Thanks in advance, Tony Molloy. e-mail molloyt@ul.ie University of Limerick, Ireland
sboswell@sdcc13.ucsd.edu (....What Is?....) (06/24/91)
I just tried to compile my AVL tree class under Kyoto Common Lisp and run it, and it says "DEFCLASS not defined." Does Kyoto support CLOS at all? Is there an extension I didn't install? If not, can someone recommend a version of Common Lisp that compiles to fast, efficient code that'll run under an average Unix system (I'm running it on an HP 300) that supports CLOS? -- Steve Boswell | This opinion is distributed in the hopes that it whatis@ucsd.edu | will be useful, but WITHOUT ANY WARRANTY... whatis@gnu.ai.mit.edu |