Update readme to reflect new direction
This commit is contained in:
parent
070e936c4a
commit
d5ebbf5a0d
1 changed files with 10 additions and 7 deletions
17
README.md
17
README.md
|
|
@ -1,11 +1,14 @@
|
||||||
# Tada
|
# Tada
|
||||||
|
|
||||||
Tada is an interpreted language inspired by lisp and lua. It's name means
|
Tada is an interpreted language inspired by Lua.
|
||||||
"tabular data" or "table data".
|
|
||||||
|
|
||||||
I've wanted to learn a lisp for a while now, but have never come further than
|
It started with the idea of making Lua more consistent. For example, why not
|
||||||
the absolute basics. Also, I've never created a proper programming language
|
return multiple values by returning and then destructuring a table? That would
|
||||||
before. So I decided to make one - inspired by my rudimentary understanding of
|
also allow accessing return values besides the first in expressions. Since we
|
||||||
lisp, combined with a bit of lua tables.
|
need destructuring anyways, why not use a table to pass arguments? Positional
|
||||||
|
and keyword arguments would directly fall out of that approach.
|
||||||
|
|
||||||
https://github.com/quchen/stgi
|
After some discussion, this turned into using tables as answer for pretty much
|
||||||
|
every design decision. Functions? Tables. Code blocks? Tables, their curly
|
||||||
|
braces fit pretty well already. Scopes? Tables. Function calls? Tables. Source
|
||||||
|
code? Tables, with most "normal" syntax being simple syntactic sugar.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue