Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!bu.edu!rpi!zaphod.mps.ohio-state.edu!think!barmar
From: barmar@think.com (Barry Margolin)
Newsgroups: comp.lang.lisp
Subject: Re: CLOS metaobject protocol status?
Keywords: CLOS
Message-ID: <41105@think.Think.COM>
Date: 28 Jul 90 18:37:37 GMT
References: <13918@shlump.nac.dec.com>
Sender: news@Think.COM
Organization: Thinking Machines Corporation, Cambridge MA, USA
Lines: 22

In article <13918@shlump.nac.dec.com> adler@aiag.enet.dec.com () writes:
>Does anyone know the current status of the CLOS metaobject
>protocol within the X3J13 committee?  We have heard that it
>was rejected, but it is included in the CLOS implementations
>in Lucid Common Lisp and TI's Explorer Common Lisp.

The metaobject protocol couldn't have been "rejected", since it was never
proposed for adoption.  The designers still haven't finished designing it.
The only decision regarding the metaobject protocol that X3J13 made was
that we didn't need to hold up the standard for it.

Many CLOS implementations include *a* metaobject protocol.  Most are
presumably based on the draft specs that have been published within X3J13
from time to time.  If the CLOS developers from those vendors have also
been involved in the metaobject protocol design then they may even be more
up-to-date than the specs.  But there will undoubtedly have to be changes
made when the final metaobject protocol is adopted.
--
Barry Margolin, Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar