The BIG problem is that Common Lisp is mutable.
Creating a DSL for common lisp, creatin cons, managing syntax, and so on,
no probl. Even manage a Lisp-2.
But as you have that fucken fset, you have to do counterClojure.
Ask Deuce guy :
http://skillsmatter.com/podcast/scala/deuce-is-not-yet-emacs-u
Deuce translates Emacs Lisp to Clojure and has to deal with some similar
issues. Doing 80% and deal with the rest by hand wasn't an option here (but
at times tempting). Initially I tried generating mildly "idiomatic"
Clojure, but gave up in favor of getting it to work first. For example,
Emacs
On Jun 16, 2013, at 8:27 AM, Rich Morin wrote:
> This is undoubtedly an open-ended (and probably naive) question, but I'm
> wondering
> how much of the task of translating Common Lisp code into Clojure could be
> done by
> a program and how useful (eg, idiomatic) the result would be.
>
> I ca
On Jun 16, 2013, at 05:27, Rich Morin wrote:
> ... Common Lisp implementations on the JVM (eg, ABCL, Kawa, SISC), ...
Oops, my bad. Kawa and SISC are actually Scheme implementations.
-r
--
http://www.cfcl.com/rdmRich Morin
http://www.cfcl.com/rdm/resume r...@cfcl.com
http://ww
This is undoubtedly an open-ended (and probably naive) question, but I'm
wondering
how much of the task of translating Common Lisp code into Clojure could be done
by
a program and how useful (eg, idiomatic) the result would be.
I can think of various kinds of differences that would need to be a
