summaryrefslogtreecommitdiff
path: root/dylfunc_call.cpp
diff options
context:
space:
mode:
authoruser <user@localhost.localdomain>2019-08-27 19:16:51 -0400
committeruser <user@localhost.localdomain>2019-08-27 19:16:51 -0400
commitd180cc071b592940d4b4cf0283823d29578f1422 (patch)
treef00b55fee23982c1fcb885be57e5216c5a1639ec /dylfunc_call.cpp
parentc179ae14d5dc6e35031dec3cc7b62e99d6f392be (diff)
downloadstandingwithresilience-d180cc071b592940d4b4cf0283823d29578f1422.tar.gz
standingwithresilience-d180cc071b592940d4b4cf0283823d29578f1422.zip
some files to help me jog my memory elsewhere
Diffstat (limited to 'dylfunc_call.cpp')
-rw-r--r--dylfunc_call.cpp9
1 files changed, 9 insertions, 0 deletions
diff --git a/dylfunc_call.cpp b/dylfunc_call.cpp
new file mode 100644
index 0000000..bbd2ea7
--- /dev/null
+++ b/dylfunc_call.cpp
@@ -0,0 +1,9 @@
+// this process loads a dynamic library built by dylfunc_compile
+// and executes it with the passed data
+
+// we are moving towards judging that we no longer need dynamic loading
+// and could just compile new code ... it seems valuable but slow-start.
+// why not just build processes?
+// need to structure input and output
+//
+// okay, let's look into atomspace serialization