kamikazechaser/vise
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove sink opcode

Browse Source
This commit is contained in:
lash 2023-04-01 15:37:11 +01:00
parent a0069d7818
commit 98e738aa92
Signed by untrusted user who does not match committer: lash
GPG Key ID: 21D2E7BB88C2A746
2 changed files with 1 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@ -9,7 +9,7 @@ Original motivation was to create a simple templating renderer for USSD clients,
The VM defines the following opcode symbols: The VM defines the following opcode symbols:
* `BACK` - Return to the previous execution frame (will fail if at top frame). * `BACK` - Return to the previous execution frame (will fail if at top frame). It leaves to the state of the execution layer to define what "previous" means.
* `CATCH <symbol> <signal>` - Jump to symbol if signal is set (see `signal` below). * `CATCH <symbol> <signal>` - Jump to symbol if signal is set (see `signal` below).
* `CROAK <signal>` - Clear state and restart execution from tip if signal is set (see `signal` below). * `CROAK <signal>` - Clear state and restart execution from tip if signal is set (see `signal` below).
* `LOAD <symbol> <size>` - Execute the code symbol `symbol` and cache the data, constrained to the given `size`. * `LOAD <symbol> <size>` - Execute the code symbol `symbol` and cache the data, constrained to the given `size`.
@ -31,4 +31,3 @@ For example, in this example
- param `three` is a _sink_. - param `three` is a _sink_.
The renderer may use up to `256 - 120 - 5 - 12 = 119` bytes from the _sink_ when rendering the output. The renderer may use up to `256 - 120 - 5 - 12 = 119` bytes from the _sink_ when rendering the output.

1
go/vm/opcodes.go
View File

@ -12,7 +12,6 @@ const (
LOAD LOAD
RELOAD RELOAD
MAP MAP
SINK
MOVE MOVE
_MAX _MAX
) )