ArkScript, A small, lisp-inspired, functional scripting language
-
I’ve been working on this (not so little anymore) project for some time now, and I’m finally happy with the branding, UX and docs state.
It’s a scripting language I made at first as a toy, to learn new parsing methods, explore compiler optimizations, and go back to VM land where everything is low level and amazing (at least for me) ; it’s now a fully fledged language that can be used as a scripting language like Python or Ruby, and can also be very easily embedded inside a project, as one would do with Lua.
Let me know your thoughts and opinions on the project!
-
I’ve been working on this (not so little anymore) project for some time now, and I’m finally happy with the branding, UX and docs state.
It’s a scripting language I made at first as a toy, to learn new parsing methods, explore compiler optimizations, and go back to VM land where everything is low level and amazing (at least for me) ; it’s now a fully fledged language that can be used as a scripting language like Python or Ruby, and can also be very easily embedded inside a project, as one would do with Lua.
Let me know your thoughts and opinions on the project!
What are the differences with other lisps?
-
What are the differences with other lisps?
First of all, the language is lisp inspired. ArkScript has s-expressions and code as data via its macros, its reads the same (left to right, prefix notation).
Keywords wise, we are not the same, which is a small but striking difference when comparing them side by side.
ArkScript has no classes nor structures, and no quoting/quasiquoting.
AFAICT both ArkScript and Common Lisp (a big lisp contender) have lexical scoping, so no real difference here.
ArkScript has strong dynamic typing too, like many other lisp.
The big advantage I would say ArkScript has, is its embedded capabilities. You can very easily use it in a project, as its C++ API has been designed for this.
-
First of all, the language is lisp inspired. ArkScript has s-expressions and code as data via its macros, its reads the same (left to right, prefix notation).
Keywords wise, we are not the same, which is a small but striking difference when comparing them side by side.
ArkScript has no classes nor structures, and no quoting/quasiquoting.
AFAICT both ArkScript and Common Lisp (a big lisp contender) have lexical scoping, so no real difference here.
ArkScript has strong dynamic typing too, like many other lisp.
The big advantage I would say ArkScript has, is its embedded capabilities. You can very easily use it in a project, as its C++ API has been designed for this.
I'd like a blog on the language design. That said, I don't have a requirement to use it, I'm just very curious about it
