diff options
| author | Irene Knapp <ireneista@irenes.space> | 2026-05-21 10:55:33 -0700 |
|---|---|---|
| committer | Irene Knapp <ireneista@irenes.space> | 2026-05-21 13:25:03 -0700 |
| commit | 09e1758b4380767647a238f88f51baa85e6e4df5 (patch) | |
| tree | 3d024eaa5dc1de0adef8036bde602902683140d0 /core.e | |
| parent | fe5ad105a8ca461eae368178706655753219ab92 (diff) | |
Add high-level flow control to the log-load transform
that was a lot Change-Id: I6ae9c371fe1fe6fd2757d20df73a748339fa89d1 Force-Push: yes
Diffstat (limited to 'core.e')
| -rw-r--r-- | core.e | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/core.e b/core.e index 491b73c..eeeb1fc 100644 --- a/core.e +++ b/core.e @@ -757,6 +757,7 @@ here ! ~ Jonesforth also offers C@C! as another name for its CCOPY, but neither ~ "@!" nor "mem@mem!" seems particulaly nice. ~ +~ TODO these parameters feel backwards ~ (destination, source, length --) : memcopy [ here @ @@ -776,6 +777,7 @@ here ! ~ careful about which end the transfer starts from. This "move" vs. "copy" ~ distinction mirrors C terminology. ~ +~ TODO these parameters feel backwards ~ (destination, source, length --) : memmove [ here @ |