summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authoruser <user@localhost.localdomain>2019-08-26 07:38:48 -0400
committeruser <user@localhost.localdomain>2019-08-26 07:38:48 -0400
commitff67ef239130f37ceb65fb27dc570ded3420a093 (patch)
tree0f23d6318a8b9cfe8b56a6a634fd5539cc14afb6
parentc179ae14d5dc6e35031dec3cc7b62e99d6f392be (diff)
downloadstandingwithresilience-ff67ef239130f37ceb65fb27dc570ded3420a093.tar.gz
standingwithresilience-ff67ef239130f37ceb65fb27dc570ded3420a093.zip
small note
-rw-r--r--CORE1.cpp2
1 files changed, 2 insertions, 0 deletions
diff --git a/CORE1.cpp b/CORE1.cpp
index ee0ffa6..5fe8349 100644
--- a/CORE1.cpp
+++ b/CORE1.cpp
@@ -21,6 +21,7 @@ using namespace std;
// maybe then backtracking from a failure to the steps that caused it, and opening those steps up into substeps
// GDB HAS A MACHINE INTERFACE MODE THAT COULD BE USED TO MANAGE EXECUTION WITH LEARNING
+// It likely also handles segfaults.
#include "Context.hpp"
@@ -46,6 +47,7 @@ using namespace std;
// Assuming you want to SHARE it, YES.
// Until you make an AI, only a handful of select people on earth will have one.
// These people will be effectively running the world, leaving many concerns out.
+// They have a head start on you, so it is likely only possible if you don't harm them in the work.
///// Core expansion
// need step-concept, made of substeps, with state-parts that interconnect?