-
I don't remember why this wasn't implemented to start with.
```lisp
(global (lambda text (int text (list string))) lambda0
(lambda ((int i) (text t) ((list string) l)
(text_join (var t) …
-
Following https://github.com/nsensfel/tonkadur/issues/17, the user can declare extra computations and extra instructions. It is still not possible to use Fate to define constructs containing instructi…
-
-
```Scheme
(list 0 1 2 3 4)
```
Should be a shortcut for
```Scheme
(add 0 1 2 3 4 (default (list int)))
```
```Scheme
(set 0 1 2 3 4)
```
Should be a shortcut for
```Scheme
(add 0 1 2 3 4 (…
-
1st level instructions excluded.
-
The `value` and `text` rules in the parser both have an ENABLE_TEXT_EFFECT rule. This is likely not a good idea.
-
Add a `(join [TEXT] [TEXT COLLECTION])` computation, which returns a `[TEXT]` value corresponding to the members of `[TEXT COLLECTION]` separated by the `[TEXT]` argument.
-
The `(new [TYPE])` computation is currently listed as an exception to the rule of computations not modifying the memory. This is a terrible idea and can easily lead to memory being allocated without t…
-
Scripting languages need the ability to perform application-specific computations and instructions.
Currently, Tonkadur provides this for instructions, although the naming ( `declare_event_type`/`eve…
-
Knowing whether to use `string` or `text`, or even what is currently returned by some computation, is too difficult.
Removing the `string` type might be a solution.