Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/17/84; site hplabsc.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!pesnta!hplabsc!kempf
From: kempf@hplabsc.UUCP (Jim Kempf)
Newsgroups: net.lang.lisp,net.lang.st80,net.ai,net.micro.mac
Subject: Re: Common Lisp Objects
Message-ID: <2614@hplabsc.UUCP>
Date: Mon, 10-Jun-85 10:27:04 EDT
Article-I.D.: hplabsc.2614
Posted: Mon Jun 10 10:27:04 1985
Date-Received: Tue, 11-Jun-85 08:31:41 EDT
Distribution: net
Organization: Hewlett Packard Labs, Palo Alto CA
Lines: 34
Xref: watmath net.lang.lisp:484 net.lang.st80:243 net.ai:2825 net.micro.mac:1670

There is currently no Common Lisp standard for object oriented
programming, since Steele's book does not define one as part
of the language. However, some work has been done here at HP Labs to
develop an object oriented extension to Common Lisp which is
efficient and less complex than ZetaLisp flavors, but which
provides much of the dynamic binding of Smalltalk. In addition,
our Common Lisp Objects language definition has features to
help encourage modularity and data hiding, like Modula.

Interested parties can obtain a document describing the language
by writing:

        Distributed Computing Center
        Hewlett-Packard Company
        1501 Page Mill Rd.
        Palo Alto, CA
        94304

and requesting the report:

        ATC-85-1

        "Object-Oriented Programming for Common Lisp"
        by Alan Snyder

Incidently, lexical closures are not necessarily needed to
implement an object oriented language in Lisp, and, in fact,
may not result in the fastest runtime implementation. However,
because Common Lisp has lexical closures, using them in an
object oriented language would seem to be logical for a
first cut implementation.


                jim kempf ARPA: kempf@hplabs USNET: hplabs!kempf