4 ms·

Excited to see that finally someone has written an imperative language in a functional runtime. Normally it's the other way around - countless Lisp implementat

Excited to see that finally someone has written an imperative language in a functional runtime. Normally it's the other way around - countless Lisp implementations running in C, because those are trivial to write. The most important feature of Eden IMHO is the copy-on-write semantics for collection that it inherited from Clojure. I hope this extends to nested structures like JSON data (it should). This opens the door to not having to distinguish between passing by value and passing by reference, although atom() is still available for mimicking references if needed. This opens the door for content-addressable memories and rapid application development where the user can focus on business logic, with less time wasted on the more mundane aspects of programming like resource management. I've written about all this stuff countless times in previous comments so kudus to Eden for being one of the first languages I've seen to start getting this stuff right!

jmaa 8y ago
> Excited to see that finally someone has written an imperative language in a functional runtime. Normally it's the other way around - countless Lisp implementations running in C, because those are trivial to write. This is not as hard as one might imagine; the first assignment for a compiler course I took, was to write a interpreter for a simple imperative language, running in SML, a mostly functional language. The rest of the course was to write a compiler for another imperative language, again in SML. As soon as you know the "tricks" (some might call them patterns, if we were talking OOP), writing imperative code in functional languages is relatively easy. The course followed "Modern Compiler Implementation in ML", if anyone is interested.
lispm 8y ago
> Excited to see that finally someone has written an imperative language in a functional runtime. Aren't there zillions of languages implemented on top of Lisp dialects? CL-USER 13 > (CLPYTHON.APP.REPL:REPL) Welcome to CLPython, an implementation of Python in Common Lisp. Running on: LispWorks 7.1.1 REPL shortcuts: `:q' = quit, `:h' = help. ;; Consider customizing variable *CLPYTHON-MODULE-SEARCH-PATHS* ;; to be a list of paths that are tried when locating a module in order to import it ;; (in addition to the current directory and `sys.path'). Typically it should at least ;; contain the path to the Python 2.x standard libraries, as those are not ;; distributed with CLPython. >>> for i in range(4): print i ... 0 1 2 3 >>> 3 + 14 17

jmaa 8y ago

> Excited to see that finally someone has written an imperative language in a functional runtime. Normally it's the other way around - countless Lisp implementations running in C, because those are trivial to write. This is not as hard as one might imagine; the first assignment for a compiler course I took, was to write a interpreter for a simple imperative language, running in SML, a mostly functional language. The rest of the course was to write a compiler for another imperative language, again in SML. As soon as you know the "tricks" (some might call them patterns, if we were talking OOP), writing imperative code in functional languages is relatively easy. The course followed "Modern Compiler Implementation in ML", if anyone is interested.

lispm 8y ago

> Excited to see that finally someone has written an imperative language in a functional runtime. Aren't there zillions of languages implemented on top of Lisp dialects? CL-USER 13 > (CLPYTHON.APP.REPL:REPL) Welcome to CLPython, an implementation of Python in Common Lisp. Running on: LispWorks 7.1.1 REPL shortcuts: `:q' = quit, `:h' = help. ;; Consider customizing variable *CLPYTHON-MODULE-SEARCH-PATHS* ;; to be a list of paths that are tried when locating a module in order to import it ;; (in addition to the current directory and `sys.path'). Typically it should at least ;; contain the path to the Python 2.x standard libraries, as those are not ;; distributed with CLPython. >>> for i in range(4): print i ... 0 1 2 3 >>> 3 + 14 17