aboutsummaryrefslogtreecommitdiff
path: root/cm/ex03.cm
diff options
context:
space:
mode:
authorrtk0c <[email protected]>2025-10-09 19:41:45 +0000
committerrtk0c <[email protected]>2025-10-15 20:28:15 +0000
commitbc8c20d1e93b5c18e8915d356e74024092a74ce8 (patch)
tree68572587354e928075f84bfbb3f71db21e9d174e /cm/ex03.cm
parentab49edbb106c25b980bac0227a3db55b74378784 (diff)
Extra thoughts
Diffstat (limited to 'cm/ex03.cm')
-rw-r--r--cm/ex03.cm4
1 files changed, 4 insertions, 0 deletions
diff --git a/cm/ex03.cm b/cm/ex03.cm
index 34275df..417799f 100644
--- a/cm/ex03.cm
+++ b/cm/ex03.cm
@@ -31,6 +31,10 @@
// should bindings be baked into the environment image (i.e. design the bytecode format to include this? however it should be done; can't really imagine it now?)
// or should they be generated e.g. `bind_function("func_name", &func_written_in_C);`?
+// REUSING EXSITING SCRIPTING LANGUAGE
+// We don't want to reimplement a language from scratch
+// Hacking e.g. PUC-Lua's parser? Kind of like Terra
+
// terminology akin to Janet (from _Janet for Mortals_):
// compile: evaluating the program sources to produce an environment
// runtime: evaluating the environment