some notes in the readme, vim folding in .s

1 files changed, 27 insertions, 0 deletions

diff --git a/readme.md b/readme.md
index 03ea80f..d77c014 100644
--- a/readme.md
+++ b/readme.md
@@ -9,6 +9,20 @@ the plan right now is that this will be an STC forth.
 if this proves Too Complicated To Deal With the plan may be changed
 to a DTC forth instead.
 
+## dictionary
+the dictionary follows a fairly standard format.
+
+| field | size |
+| :---- | :--- |
+| link to previous | 8 bytes |
+| flag | 1 byte |
+| string length | 2 bytes |
+| string | variable length |
+| code | variable length |
+
+probably, some bitmask antics could be done to store the string length
+and flags together. but alternatively: no.
+
 ## forth registers
 there are a set of 'virtual registers' (see moving forth part 1)
 
@@ -33,3 +47,16 @@ so a wonky but hopefully not too slow solution is to compile
 
 - `mov r11, [cfa]` = `94 BB [CFA]`
 - `call r11` = `41 FF D3`
+
+# Some Links
+
+- starting forth part 1: http://www.bradrodriguez.com/papers/moving1.htm
+- a forum thread about determining empty stack with TOS register: http://forum.6502.org/viewtopic.php?t=8424
+
+## silly little plans
+
+### in-forth assembler
+this would reap the most benefits from STC.
+probably look at dusk's assemblers for how it should look like
+or liek something liek dusk's lib/bm?
+idk something to do stuff Fast if u need. would be fun