Newsgroups: comp.lang.lisp.x
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornellcs!newsstand.cit.cornell.edu!portc01.blue.aol.com!newsxfer3.itd.umich.edu!howland.erols.net!newsfeed.internetmci.com!hunter.premier.net!news.lightlink.com!mv!usenet
From: David Betz <dbetz@xlisper.mv.com>
Subject: Re: XLISP 3.0
Content-Type: text/plain; charset=us-ascii
Reply-To: dbetz@xlisper.mv.com
To: jjames@interval.com
Content-Transfer-Encoding: 7bit
Organization: MV Communications, Inc.
Message-ID: <32F08E44.66AB@xlisper.mv.com>
References: <32D57891.1823@xlisper.mv.com> <5c5sa6$ja@tiptoe.fhda.edu> <uvi8gpabe.fsf@interval.com>
X-Mailer: Mozilla 3.01 (Win95; I)
Mime-Version: 1.0
X-Nntp-Posting-Host: xlisper.mv.com
Date: Thu, 30 Jan 1997 12:04:20 GMT
Lines: 31

jjames@interval.com wrote:
> 
> David Betz (dbetz@xlisper.mv.com) wrote:
> >Does anyone have any interest in a new version of XLISP?  I've created
> >an XLISP 3.0 that is actually the successor to XLISP 2.1 and XScheme.
> >It uses the Scheme syntax but adds optional and keyword arguments and
> >multiple values.  I've also cleaned up the object system a bit and added
> >a bunch of macros to make it easier to define classes and methods.
> 
> I assume this is different from XLISP-PLUS 3.0, by Tom Almy.

Yes, it is different from XLISP-PLUS.  My original goal in designing
XLISP was to keep it small.  Trying to be compatible with Common Lisp
made that nearly impossible.  So, instead of trying to be a Common Lisp
subset, I've taken some of the features I like in Common Lisp and added
them to my Scheme-based Lisp.  This includes multiple values and
optional and keyword arguments.  Tom has taken the different approach of
adding more and more Common Lisp features the old XLISP 2.1 base code. 
He's done a nice job (along with Luke Tierney) of improving the numeric
support along with fixing a bunch of bugs in the original source code
and adding lots of new features.  I decided a while back that I wasn't
comfortable moving forward with my original source and switched to a
pretty much completely new system based on a bytecode
compiler/interpreter.  Unfortunately, we both moved to version 3.0 at
similar times and that is what is confusing.

-- 
David Betz
DavidBetz@aol.com
dbetz@xlisper.mv.com
(603) 472-2389
