Sexpr is free software, licensed under the GNU GPL.
Copyright (c) 2013-2014 Free Software Foundation, Inc.
Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved.
Sexpr is a Lisp parser and evaluator implemented in Lua.
It will replace the toy Lisp implementation in GNU Zile at some point, and so is modelled after Emacs Lisp. It does have a macro facility and flexible enough design that tweaking it to implement, say, a scheme environment would be quite straight forward.
Sexpr is written in Lua using lua-stdlib. It uses Specl to check that it meets specifications, and has LDoc comments that can be used to generate API documentation.
Nothing much to see here, but screenshots are always popular:
$ ./sexpr
sexpr version 0 Copyright (C) 2014 Gary V. Vaughan
enter ':q' to exit
> _
Run the Sexpr REPL from the source tree with: ./sexpr. There's
nothing to configure or build first, although there's a Makefile for
running specification checks, and building documentation.
- See file AUTHORS for the names of maintainers past and present.
- See file COPYING for copying conditions.
- See file THANKS for a list of important infuences and contributors.
- Directory build-aux contains helper scripts used to build Sexpr.
- Directory lib contains the source code for Sexpr.
- Directory specs contains the Sexpr specifications for Specl
- Sexpr development is co-ordinated from the Sexpr project page at github.
If this distribution doesn't work for you, before you report the problem, please try upgrading to the latest released version first, to see whether your issue has been fixed already. If you can, please also check whether the latest development sources for the next release still exhibit the problem.
Please file bug reports, feature requests and patches as github issues.
When you are ready to submit a report, first, please read this.
Sexpr has a suite of Specl specifications in the specs directory of the source distribution, which you can run with:
make check
If, when you report a bug, you can create a spec example that demonstrates it, the maintainers will be most grateful, and it will prevent them from accidentally reintroducing the bug in a subsequent release.