With this change input from stdin is compiled and output is written to stdout.
This makes few things a lot easier for example cat src/lispy.ls | lispy will print compile output.
This patch depends on other changes I have submitted (#10, #8, #7, #6), once their are pulled diff here will appear a lot smaller.
cat src/lispy.ls | lispy
While working on this I have noticed that valid lisp (if true true) compiles to an invalid JS true ? true : ; so I fixed that so that it complies to true ? true : undefined; instead.
(if true true)
true ? true : ;
true ? true : undefined;
Create a pre publish script that compiles lisp before publishing.
Update Install / Use instructions.
Add syntax highlighting to the readme.
Simplify lispy binary.
Use relative module id's instead of resolving paths.
Merge branches 'feature/docs', 'feature/pre-publish' and 'feature/rel…
Merge branch 'feature/comment'
Make `false` expression for `if` form optional.
Add support for stdio compilation.
Allow function references in try form.
Fix bug that causing compile errors to be not reported.
I believe 9663ce0 solves #12
This would be a really great addition to LispyScript as it would make it a lot easier to integrate it with other software.
@rbgrouleff You could try them out in my fork https://github.com/gozala/lispyscript
Also I wrote a small web page that does translation on the fly http://jeditoolkit.com/lispyscript/