From owner-freebsd-hackers Sat Apr 1 19:13:19 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA20635 for hackers-outgoing; Sat, 1 Apr 1995 19:13:19 -0800 Received: from saul2.u.washington.edu (saul2.u.washington.edu [140.142.56.21]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id TAA20628 for ; Sat, 1 Apr 1995 19:13:16 -0800 Received: by saul2.u.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA19051; Sat, 1 Apr 95 19:11:49 -0800 X-Sender: spaz@saul2.u.washington.edu Date: Sat, 1 Apr 1995 19:11:49 -0800 (PST) From: John Utz To: Brian Tao Cc: "Paul F. Werkowski" , FreeBSD-hackers@freefall.cdrom.com Subject: CLISP clarification, Was: New Snapshot...Good and Bad.... In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk Hokay; Allow me to clear up all of this confusion that i started... On Sat, 1 Apr 1995, Brian Tao wrote: > On Fri, 31 Mar 1995, Paul F. Werkowski wrote: > > > > John> the other problem, which i imagine is a snapshot kind > > John> of thing ,is that CLISP falls over dead while it is trying > > > > You are running CMU Lisp on FreeBSD? How did you do this? No, it is not the official full on CMU LISP > > Isn't CLISP == Common LISP? Or is that the same as CMU LISP? Ahh, it is kind of a funny deal, i think that a lot of folks try and model there implemetations after the CMU Lisp, for reasons that are probably really apparent to Lisp folks. I know absolutely nothing about lisp. The implemetation i am trying to bootstrap is from Germany: @ncftp>more ANNOUNCE @This is CLISP, a Common Lisp implementation. @ CLISP is mostly CLtL1 compliant, with some CLtL2 additions, including a @ CLOS subset. Many features of CLtL2 or dpANS CL are currently not @ supported. @ The newest versions will always be available via anonymous ftp from @ ma2s2.mathematik.uni-karlsruhe.de [129.13.115.2], directory @ /pub/lisp/clisp/. @ Another ftp site carrying CLISP is @ ftp.cs.cmu.edu [128.2.206.173], directory user/ai/lang/lisp/impl/clisp/. ^^^^^^^^^^^^ Given the thread of this conversation I think this mirror is kind of significant. It would seem to me that if cmu wants to mirror this particular implementation that would indicate that they felt that it was a reasonable job that implements some significant feature not found in there original. I would be willing to bet that significant feature is SIZE!!! @ Our Common Lisp CLISP @ * needs only 1.5 MB of memory ^^^^^^^^^^^^^^^^ Did i read in someone else's posting that CMU CLISP wants 16M?!!! @ * implements 99% of the CLtL1 standard, as well as some extensions @ * can call your preferred editor @ * is freely distributable @ Get it via anonymous ftp from ma2s2.mathematik.uni-karlsruhe.de @ [129.13.115.2], @ directory /pub/lisp/clisp/, or contact @ Bruno Haible . If you are not hot and sweaty about getting the exact particular package then i would seriously look at this. It made right the heck up on 2.0R ( excepting __const char *__const sys_errlist, of course ). It might be an improvment to *have* this as opposed to *wondering* about the portability of the full on CMU version. As i said originally, it flops on the current snap. It compiles fine but seems to run out of room on my 8 meg 386 during the bytecompile stage ( this is a total wag , i infer this because the lisp environment gets created from the c code, executes, goes to work on a mess of *.lsp and dies in one called clos.lsp, but what i don't know about lisp defies all comprehension in terms of total, blind, ignorance. ). One of our vm gurus, i think it was DG but it might have been Bruce, mentioned something about needing snapshots to test out the current state of the vm code..so i would think that this might be an elliptic reference to the grief i was having. in case you are wondering why i am torturing myself with a language i can't comprehend,,, lisp is the lang of choice for symbolic computation and the guy that wrote this clisp has also done a gorgeous port of some classic symbolic computation code. Given the fact that i dont even know what the equivalent of printf is in lisp, it seemed logical to get his *environment* if i wanted to use his *port* with any chance of having a successfull compilation. Which, btw, turned out to be the case on 2.0R. obviously, i eagerly await the next snap, but i think i am stuck now until 2.1 because i dont see where i will have time to do this again until the quarter is over...it tooks three days of near continuous effort ( thank heaven my wife was out of town... :-) ) > -- > Brian ("Though this be madness, yet there is method in't") Tao > taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org > > ******************************************************************************* John Utz spaz@stein.u.washington.edu idiocy is the impulse function in the convolution of life