A simple implementation of Standard Lisp written in JavaScript.
Tag Archives: Lisp
Genyris
In the Genyris programming paradigm objects can belong to multiple classes independent from construction. Indentation reduces parentheses yet retains the power of Lisp. External Java libraries can be imported.
fun4j
fun4j is a framework that integrates major concepts from functional programming into the Java Platform. It also provides seamless integration of Java with Lisp coding, by using a lisp-to-bytecode compiler.
ClojureScript
This is a Clojure to JavaScript compiler which is written in Closure which is executed on a JVM.
rustlang
A Java interpreter for a lisp like language.
Schava
Scheme (dialect of Lisp) interpreter written in Java.
greebo
Greebo is a multi-paradigm programming language that borrows on concepts from Lisp, Dylan, Lua or IO. Some features are tail recursion optimization, both lexical and dynamic closures, zero special forms (‘def’ or ‘if’ can be used like any other procedure), first-class environments whose bindings and properties may be manipulated at wish, powerful macros, literal indexers and slices for anything that is a collection and more.
Alef++
Its author claims that “Alef++ is a new programming language like Perl and Lisp syntax, with a many changing in classical languages designs”. It is proposed as a dynamic language is based in Java Virual Machine and designed to OO-Style programmers. It is claimed to have a new design for flow controls, an easy manipulaction for arrays and hashs, many styles for subroutines, a crazy syntax and to be designed just for fun.
Armed Bear Common Lisp (ABCL)
Armed Bear Common Lisp (ABCL) is an implementation of ANSI Common Lisp that runs in a Java virtual machine. It provides a runtime system, a compiler that compiles Lisp source to JVM bytecode, and an interactive REPL for program development.
Lili
Lili is a new Lisp dialect, initially developped for using it as a sort of central executive or macro language in the Java – integration of an A.I. system called IPAL. There already exists a kind of ‘reference’-interpreter implemented in Java (that incorporates some Lili-Java-interoperability features not inherent to the Lili language specification.).