Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!CIS.OHIO-STATE.EDU!welch
From: welch@CIS.OHIO-STATE.EDU (Arun Welch)
Newsgroups: comp.sys.xerox
Subject: Loops -> PCL
Message-ID: <8904071621.AA06061@cheops.cis.ohio-state.edu>
Date: 7 Apr 89 16:21:58 GMT
References: <8904071453.AA26393@tut.cis.ohio-state.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 24


We've taken the reimplementation route, since we decided that our code
was ready for a redesign anyway, but building a Loops on top of CLOS'
meta-object protocol should be doable, at least to the user interface level.
For example, send is implementable as
(defmacro send (message object &rest args)
	`(,message ,object ,@args))

Internally it's behavior is quite different, but externally it's the
same. 

As for the rest of the Loops world, I've just about finished porting
the CLOS browser  to the Dec PCL.  It now works, but I've got to
straighten out the import/exprt/other-package-crap, which should take
a couple hours.  I've been using it for my stuff, and it's pretty
whippy on a Sun-4.  We're waiting for the windowing issues to shake
themselves out, so portability is still a problem.  Personally, I
think CLX is at too low a level, CLUE is a step in the right
direction, and CommonWindows is getting closer.  What would be nice is
a Public-domain or cheap window system that's really portable, and is
at the right level of abstraction. *sigh*, I've been spoiled on the
dmachines.

...arun