go-vise

Constrained Size Output Virtual Machine
Info | Log | Files | Refs | README | LICENSE

commit 98e738aa9299fcacd36a73d0067be94ac1dd7392
parent a0069d7818ac8b212b3e02e37b630c74e9976cd4
Author: lash <dev@holbrook.no>
Date:   Sat,  1 Apr 2023 15:37:11 +0100

Remove sink opcode

Diffstat:
MREADME.md | 3+--
Mgo/vm/opcodes.go | 1-
2 files changed, 1 insertion(+), 3 deletions(-)

diff --git a/README.md b/README.md @@ -9,7 +9,7 @@ Original motivation was to create a simple templating renderer for USSD clients, 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). * `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`. @@ -31,4 +31,3 @@ For example, in this example - param `three` is a _sink_. The renderer may use up to `256 - 120 - 5 - 12 = 119` bytes from the _sink_ when rendering the output. - diff --git a/go/vm/opcodes.go b/go/vm/opcodes.go @@ -12,7 +12,6 @@ const ( LOAD RELOAD MAP - SINK MOVE _MAX )