| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
Negates all of the numbers produced by its content subex
|
|
|
|
|
|
| |
for it's operation
Creates arithmetic.go which will house all of these functions
|
| |
|
|
|
|
| |
This potentially avoids bugs/errors and also improves the performance of pruning
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Currently doesn't parse strings as each atom is considered independantly. Instead individual characters in strings can be cast
|
|
|
|
| |
These are no longer necessary and have been replaced by repeat
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
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
|