fix(core): silent ABORT, and name the compile-only condition

Two reporting bugs found from the browser shell.

An uncaught ABORT printed 'ABORT (throw -1)'. The standard defines ABORT
as 'empty the data stack and perform the function of QUIT', and QUIT
displays no message; gforth and SwiftForth are both silent. It now takes
the same silent path QUIT got in 0.2.5. CATCH still reports -1 and still
restores the stack depth, and ABORT" still prints its text -- different
word, different code (-2).

Compile-only constructs used in interpretation state claimed to be an
'unknown word', which is misleading for a word the system obviously
knows: ABORT", IF, THEN, LOOP, LITERAL, RECURSE and friends. They now
report 'interpreting a compile-only word: <name> (throw -14)', the
standard condition both reference engines give. The check reuses the
existing INTERPRETER_TOKENS table at the point where interpretation has
already failed, so a genuine typo still reports 'unknown word'.

Ships as v0.2.6.

This commit is contained in:

Oleksandr Kozachuk

2026-08-07 13:10:42 +02:00

parent 8e2fd0d7d4

commit e110ca9516

6 changed files with 92 additions and 10 deletions

									
										crates/cli/Cargo.toml
									
		+1
		-1
	
												View File
												
				@@ -9,7 +9,7 @@ license.workspace = true

				workspace = true

				[dependencies]

				wafer-core = { path = "../core", version = "0.2.5" }

				wafer-core = { path = "../core", version = "0.2.6" }

				wasmtime = { workspace = true }

				anyhow = { workspace = true }

				clap = { version = "4", features = ["derive"] }