| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
with an output stack
Previously a store state was a parent of another state machine that it would run inside of itself in order to capture the output to be stored.
This was limited as the greedyness of the child would not be transferred to the parent.
The new implementation gives states more control over the output state and turns it into a stack.
By pushing to the stack before the child and popping afterwards, all of the child's output can be retrieved while the child is very much part of the complete machine.
|
| |
|
|
|
|
| |
that run machines within themselves
|
|
|
|
| |
Something like $a($b(test)..."$b") wouldn't work as expected, this works now
|
|
|
|
| |
Currently doesn't parse strings as each atom is considered independantly. Instead individual characters in strings can be cast
|
|
|
|
|
|
| |
probably more
The repeat construct repeats a subex a number of times, this number is based on a provided list which is ordered by priority and can be unbounded.
|
| |
|
|
|
|
| |
main/subexstate.go
|
| |
|
|
|
|
|
|
| |
semantics of append
When doing append, be very careful as it does make changes in place to the underlying array of the slice which may affect other slices
|
|
|
|
|
|
| |
Currently no way to reassemble the data on the other side
Much of the potential data cannot be interacted with meaningfully, only the string functionality is implemented
Should rename data to something else
|
|
Doesn't integrate it at all yet
|