Newsgroups: comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornellcs!newsstand.cit.cornell.edu!portc01.blue.aol.com!cliffs.rs.itd.umich.edu!howland.erols.net!www.nntp.primenet.com!nntp.primenet.com!netcom.com!www.algonet.se!user
From: ddyer@netcom.com (Dave Dyer)
Subject: Re: Javugh
Message-ID: <ddyer-2012961218500001@www.algonet.se>
Sender: ddyer@netcom19.netcom.com
Organization: Andromeda Software
References: <59bu4d$571@usenet.srv.cis.pitt.edu> <59c2g7$1ige@news.doit.wisc.edu>
Date: Fri, 20 Dec 1996 20:18:49 GMT
Lines: 41


>        The main things that Java borrows from Lisp are:
>
>            1) Garbage collection.
>            2) Exception handling (via C++, probably).
>            3) The interfaces business is a bit like the
>               "mixin" concept of Flavors.  (In case you didn't 
>               read about these, when interfaces are "implemented"
>               by a class definition you are expected to define
>               certain methods.  This avoids the stickiness of
>               multiple inheritance but guarantees that
>               certain functionality will exist for you.) 
>

You forgot to mention:

Objects/Inheritance (single inheritance only)
inescapable Array bounds checking
inescapable type safety
absence of pointer arithmetic

and in java 1.1: bignums, introspection

---

Plus, java incorporates a bunch of modern language features
that lisp lacks, or doesn't fully support.  

Encapsulated modules with defined interfaces, demand loading, and 
compile-time and load-time verification of interfaces, inter-module security 
etc. etc.

Method overloading

Serialization

And most important of all, Java has an *audience*.  Hardly anybody cares about
lisp anymore. (Ouch, I can feel the flames already!).

-- 
My home page: http://www.andromeda.com/people/ddyer/home.html
