From 87691594710f5c6213388641ce51b30e7e486299 Mon Sep 17 00:00:00 2001 From: Marshall Lochbaum Date: Thu, 18 Nov 2021 20:36:48 -0500 Subject: Fix definition of dummy _fillBy_ (needs to be a 2-modifier) --- docs/implementation/vm.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/implementation') diff --git a/docs/implementation/vm.html b/docs/implementation/vm.html index 0934ff7d..6674ced8 100644 --- a/docs/implementation/vm.html +++ b/docs/implementation/vm.html @@ -729,7 +729,7 @@

Two formatter arguments Glyph and FmtNum are not part of the runtime. Glyph assumes 𝕩 is a primitive and returns the character (not string) that represents it, and FmtNum assumes 𝕩 is a number and returns a string representing it.

Testing

I recommend roughly the following sequence of tests to get everything working smoothly. It can be very difficult to figure out where in a VM things went wrong, so it's important to work methodically and make sure each component is all right before moving to the next. In order to run test cases before the compiler runs, I strongly recommend building an automated system to compile the test to bytecode using an existing BQN implementation, and run it with the VM being developed.

-

Because the compiler works almost entirely with lists of numbers, a correct fill implementation is not needed to run the compiler. Instead, you can define Fill as 0⊘⊢ and _fillBy_ as {𝔽} to always use a fill element of 0.

+

Because the compiler works almost entirely with lists of numbers, a correct fill implementation is not needed to run the compiler. Instead, you can define Fill as 0⊘⊢ and _fillBy_ as {𝕘⋄𝔽} to always use a fill element of 0.