make a decision on where to keep find-in and document it

Force-Push: yes
Change-Id: I5e8d8ae4a6e07c2dfa38abc7b19a962932a210bf

2 files changed, 5 insertions, 3 deletions

diff --git a/core.e b/core.e
index 91cf849..1effc11 100644
--- a/core.e
+++ b/core.e
@@ -1231,7 +1231,6 @@ here !
 : unpack16 dup 16@ swap 2 + swap ;
 : unpack8 dup 8@ swap 1 + swap ;
 
-~ TODO does this need to have a separate name?
 ~ (proposed size, alignment byte count -- adjusted size)
 : align-size
   dup 3unroll dup 3unroll
@@ -1320,7 +1319,8 @@ here !
 ~ "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?
+~   The definition of "find" is in dynamic.e, with the other stuff that needs
+~ to access the log.
 ~
 ~ (dictionary pointer, string pointer -- entry pointer or 0)
 : find-in
diff --git a/dynamic.e b/dynamic.e
index d10a9c4..79944b2 100644
--- a/dynamic.e
+++ b/dynamic.e
@@ -306,7 +306,9 @@
 : recurse latest @ entry-to-execution-token , ; make-immediate
 
 
-~   The implementation of find-in is in log-load.e, for now.
+~   The implementation of "find-in" is in core.e, since it's used by the label
+~ and transformation facilities. Once we have full log access, we get the
+~ nicety of using "find" instead.
 ~
 ~ (string pointer -- entry pointer or 0)
 : find latest swap find-in ;