From a5a6c74a69a1e7bf3fdedb1886ee10cc5a3788cf Mon Sep 17 00:00:00 2001
From: kitty <nepeta@canaglie.net>
Date: Tue, 17 Feb 2026 12:29:48 +1100
Subject: some notes on DOES>

---
 readme.md | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/readme.md b/readme.md
index 38a17ab..e02280c 100644
--- a/readme.md
+++ b/readme.md
@@ -39,9 +39,10 @@ so a wonky but hopefully not too slow solution is to compile
 
 ### Some Links
 
-- starting forth part 1: http://www.bradrodriguez.com/papers/moving1.htm
 - jonesforth, public domain forth tutorial implementation which was significantly cribbed from and studied: http://git.annexia.org/?p=jonesforth.git;a=tree
 - jonesforth nasm port: http://ratfactor.com/repos/nasmjf/
+- starting forth part 1: http://www.bradrodriguez.com/papers/moving1.htm
+- page describing `<BUILDS`: https://amforth.sourceforge.net/TG/recipes/Builds.html
 
 ## silly little plans
 
@@ -50,3 +51,13 @@ 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
+
+### DOES>
+ah yes, the infamous `DOES>`. i don't have a DOCOL segment so i'm not
+sure how exactly to implement this?
+
+https://news.ycombinator.com/item?id=44231594 top comment here discusses
+the forth `<BUILDS` which i've never heard of elsewhere. in fact if i look up
+`forth "<BUILDS"` on duckduckgo that link is the only result.
+i debased myself and looked it up on google too, and found a few more results
+maybe i can do something with that because i like `DOES>` and i wanna use it
-- 
cgit v1.2.3