Skip to content
A Modern Lisp for the Erlang VM
Erlang Cucumber Makefile Emacs Lisp Shell
Pull request Compare This branch is 72 commits ahead, 28 commits behind joxa:master.
Failed to load latest commit information.
build-support support building on r18 Sep 8, 2015
doc fix typo Apr 27, 2015
emacs Fix indentation function for defmacro/defmacro+ in joxa-mode.el Feb 18, 2014
examples added Joe's favorite server as an example Feb 7, 2014
features Fix concurrent compiler Dec 17, 2012
include Complex module support, module_info compilation Dec 10, 2011
priv add missing template for bootstrap Jan 22, 2012
src support building on r18 Sep 8, 2015
test support building on r18 Sep 8, 2015
.gitignore update git ignore with sphinx output Jun 24, 2012
.travis.yml Add R15B02 to the tested architectures for travis-ci Nov 12, 2012
INSTALL.md support building on r18 Sep 8, 2015
LICENSE.md Add Apache 2 license to the system Feb 17, 2012
Makefile Ensure Joxa can be built on (Open|Free)BSD as well Jan 4, 2013
README.md fix repo path Apr 26, 2015
rebar.config support building on r18 Sep 8, 2015
todo.txt

README.md

Joxa

Joxa is a small semantically clean, functional lisp. It is a general-purpose language encouraging interactive development and a functional programming style. Joxa runs on the Erlang Virtual Machine. Like other Lisps, Joxa treats code as data and has a full (unhygienic) macro system.

Joxa (pronounced 'jocksah') isn't Erlang, though its very compatible. Its not Clojure though there is plenty of shared syntax. It's not Common Lisp though that is the source of the macro system. While Joxa shares elements of many languages, it is its own specific language. of all these languages, and knowing these languages will help you get up to speed with Joxa, but it is its own unique language.

Documentation

More information can be found on the Joxa Website and the Joxa Manual. Install instructions are in INSTALL.md colocated with this Readme. Of course, the canonical source for all docs and code is the github repo

Something went wrong with that request. Please try again.