hebigo VS gomacro

The Lissp transpiler incrementally compiles and executes each top-level form to Python. It needs to do this in case there's a macro definition that might affect the compilation of a subsequent form. If it's only executing definitions, this is harmless, but if you want to precompile the main module, it needs the guard, or the side effects will happen too.

If you want Python to be as customizable as Lissp, check out Hissp (and Hebigo).

Python's lambdas can have as many lines as you want. Just wrap parens around it. Hissp uses this form as a compilation target. Its REPL shows the Python compilation. Play around with it til you get it: https://github.com/gilch/hissp

The original Lisp's S-expression syntax was just supposed to be an intermediate language used by the compiler when processing the real language based on M-expressions, which kind of never took off. Numerous alternatives to S-expressions have been proposed, and some retain homoiconicity, another feature diagnostic of a Lisp (and one that ECMAScript lacks). For example, see Hebigo's readme, which shows a direct correspondence between its Python-like syntax and that of Hissp's default reader (Lissp), which uses the S-expressions. Julia can also be written in S-expressions, but this usually only used in macro definitions.

I think LoL is too CL-specific. If you know both languages first, you can pretty much translate, but since they'd be trying to learn Lisp in the first place, this is a bad idea.

On the other hand, [Hissp][1] has a pretty good tutorial for anyone coming from a Python background.

[1]: https://github.com/gilch/hissp

Hebigo: a whitespaceLisp isomorphic to Hissp that looks like Python.

gomacro added macros and generics several years before generics reached release.

I use https://github.com/cosmos72/gomacro when I want to quickly try some code.

Officially, it's not much scripting friendly, but there are unofficial support to make it a proper scripting option like the gomacro.

If it's a simple program I guess you could use gomacro:https://github.com/cosmos72/gomacro

Thanks to gomacro we can import no standard libraries on the notebook :P

For our use (debugging and running small scripts to update data), gomacro should work well enough, despite being an "almost complete" Go interpreter. This isn't the same as the Python REPL which uses entirely the same code to run, but it should be up to the task.

I keep meaning to play with https://github.com/cosmos72/gomacro