Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site dreacad.UUCP
Path: utzoo!utcsri!garfield!dreacad!hemphill
From: hemphill@dreacad.UUCP (hemphill)
Newsgroups: net.lang.lisp,net.lang.prolog,net.lang.st80
Subject: Re: Re: evaluation of Lisp machines
Message-ID: <190@dreacad.UUCP>
Date: Sun, 16-Jun-85 12:43:37 EDT
Article-I.D.: dreacad.190
Posted: Sun Jun 16 12:43:37 1985
Date-Received: Tue, 18-Jun-85 03:20:01 EDT
References: <534@alberta.UUCP> <160@bcsaic.UUCP>
Distribution: net
Organization: Defence Research Est. Atl., Dartmouth, N.S., Can.
Lines: 30

> In article <534@alberta.UUCP> steve@alberta.UUCP (Steve Sutphen) asks for:
> 
> >	1    Compatibility with an Interlisp-D program (we have a
> >	     current research project developed in this environ-
> >	     ment).
> >
> >	2    Compatibility with Common-Lisp. This seems like a good
> >	     standard to aim future projects at.
> 
> The only machines that run both Interlisp and Common Lisp are 10's,
> 20's, and Vaxen.  The two dialects are quite dissimilar, and your
> chances of getting Interlisp on a Bolix or Common Lisp on a Dolphin
> are pretty close to zero...
> 
> 							stan shebs

Having been a DEC-20 Interlisp site for a number of years, we have recently
switched to Symbolics machines, and are in general quite pleased with them.
The Interlisp compatiblility package (available as optional software) allows
one to use most software developed in Interlisp although we are not
developing any new stuff in Interlisp.  With the eventual arrival of the
full Symbolics Common Lisp environment (the process has begun with Rel 6.0)
we will be doing all our developemnt in Common Lisp.
	G++

-- 

	Gavin Hemphill, Defence Research Establishment Atlantic
UUCP:   {garfield,utcsrgv,dalcs}!dreacad!hemphill
ARPA:	hemphill@nrl-aic