Newsgroups: comp.lang.dylan,comp.lang.lisp,comp.lang.lisp.mcl
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!howland.reston.ans.net!news.sprintlink.net!uunet!franz.com!prl.ufl.edu!kem
From: kem@prl.ufl.edu (Kelly Murray)
Subject: Re: A Dylan implemented on Common Lisp
Message-ID: <1995Mar6.221932.28468@franz.com>
Sender: kem@math.ufl.edu (Kelly Murray)
Nntp-Posting-Host: bell
Organization: University of Florida Parallel Research Lab
References:  <3jdh0j$ib4@news.internex.net>
Date: Mon, 6 Mar 1995 22:19:32 GMT
Lines: 18
Xref: glinda.oz.cs.cmu.edu comp.lang.dylan:3580 comp.lang.lisp:16966 comp.lang.lisp.mcl:6544

In article <3jdh0j$ib4@news.internex.net>, yost@rclsgi.eng.ohio-state.edu (Dave Yost) writes:
>> It would seem to me to be a very worthy university project to
>> build a portable Dylan implementation on top of Common Lisp.
>> Would someone please do it?
>> 

This would be a good idea.  Is it possible to define a Common Lisp 
subset that would map into Dylan?  Then all that is needed is 
the CommonLisp-to-Dylan syntax translation, which I think would
be easy.  Hmm, isn't nil /= false in Dylan.  That's hard to fix in syntax.
If the CL->Dylan mapping isn't 100%, maybe we could
push hard to get Dylan changed so it would be.  

Why not make it CL-subset-able?

-Kelly Murray


