Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!cs.utexas.edu!uunet!tut.cis.ohio-state.edu!unreplyable!garbage
From: jonl%kuwait@LUCID.COM (Jon L White)
Newsgroups: comp.lang.clos
Subject: Creating metaclasses
Message-ID: <9105030234.AA00420@kuwait>
Date: 3 May 91 02:34:22 GMT
References: <9105020128.AA28067@cs.rpi.edu>
Sender: welch@tut.cis.ohio-state.edu
Distribution: inet
Organization: CommonLoops
Lines: 10

Ah, Gregor's message made me think that I may have misread how much
you wanted to be "possible"; indeed, he and I verbally confirmed that
the new MOP book doesn't _require_ implementations to handle the
CHANGE-CLASS case you brought up, but of course it doesn't _prohibit_
it either.  On the other hand, we both hope that more implementations
will actually do it, and then the portability question essentially
becomes moot.


-- JonL --