summary refs log tree commit diff
path: root/log-load.e
diff options
context:
space:
mode:
authorIrene Knapp <ireneista@irenes.space>2026-05-21 17:57:18 -0700
committerIrene Knapp <ireneista@irenes.space>2026-05-21 17:57:18 -0700
commitff09b120141e9d8acbd930d44c3f0596eb05a016 (patch)
treea773f714dcf79d864d476d880cf31520c5d7caf7 /log-load.e
parenta7a670e41bdaf9c57bfe7bbd802158de91d7d94d (diff)
dynamic.e is split up again, and more progress
see dynamic.e, input.e, interpret.e, and flow-control.e

there were a couple things in the log-load transform that need to work in compile mode, too

Force-Push: yes
Change-Id: I7caac3b9205f36f7e082a3fd280561d67e27942c
Diffstat (limited to 'log-load.e')
-rw-r--r--log-load.e12
1 files changed, 7 insertions, 5 deletions
diff --git a/log-load.e b/log-load.e
index 1406270..2b7cbd2 100644
--- a/log-load.e
+++ b/log-load.e
@@ -125,6 +125,8 @@
 ~ "find". The warm-start routine (see execution.e and transform.e) has the
 ~ job of fixing that, and it makes extensive use of find-in to do so.
 ~
+~ TODO this probably deserves its own file?
+~
 ~ (dictionary pointer, string pointer -- entry pointer or 0)
 : find-in
   ~ It will be more convenient to have the entry pointer on top.
@@ -210,7 +212,7 @@
   } if-else ;
 
 
-~   This is the same as "create", from interpret.e, except that it takes the
+~   This is the same as "create", from dynamic.e, except that it takes the
 ~ log's address as a parameter rather than hardcoding it, so that it can be
 ~ used in situations where the normal compilation process isn't yet available.
 ~
@@ -245,7 +247,7 @@
   over log-load-here swap drop ! ;
 
 
-~   This is the same as ",", from interpret.e, except that it takes the log's
+~   This is the same as ",", from dynamic.e, except that it takes the log's
 ~ address as a parameter rather than hardcoding it, so that it can be used in
 ~ situations where the normal compilation process isn't yet available.
 ~
@@ -262,7 +264,7 @@
   ! ;
 
 
-~   This is the same as `;asm`, from interpret.e, except that it takes the
+~   This is the same as `;asm`, from dynamic.e, except that it takes the
 ~ log's address as a parameter rather than hardcoding it, so that it can be
 ~ used in situations where the normal compilation process isn't yet available.
 ~
@@ -287,7 +289,7 @@
   dup 8 + swap ! ;
 
 
-~   This is the same as "variable", from interpret.e, except that it takes the
+~   This is the same as "variable", from dynamic.e, except that it takes the
 ~ log's address as a parameter rather than hardcoding it, so that it can be
 ~ used in situations where the normal compilation process isn't yet available.
 ~
@@ -314,7 +316,7 @@
 
 
 ~   A keyword is a word that evaluates to its own address, which makes it
-~ suitable for use as a constant. See more detail on that in interpret.e,
+~ suitable for use as a constant. See more detail on that in dynamic.e,
 ~ where "keyword" is defined.
 ~
 ~   Unlike Common Lisp, the lexer doesn't create keywords for us, we have to