RUN - LeFreq/Singularity GitHub Wiki
Biologically, RUN takes a graph of linked nodes and send a unit (as desired and available) of colored light through the graph. This transforms the light. It can be transformed into scent, and vice versa, similar to binary words (ASCII) into "text" and vice vera. Scents forms the Soup view of the Cloud??? (which is form + flow??).
When this code is NAMED, it forms a file or object.
Ctrl-Break: Data spills. Run stack unwinds. Depending on debug level, messages arrive at console (data in object shown for DEBUG, exceptions thrown at INFO, Warnings at WARN, Errors at ERROR (default: meaning no messages come to console when canceling an app). So when object contents spill out, they are seen by the composter side of organism as scent. Scent, then, presumably is a more primordial form of order and is connected to the goddess/female, rather than god/male side.
Every object/app, when run, gives a prompt if an uncaught exception is thrown (or Control-Break):
- Abort: cancel object run, and close down the code as well as possible (user changed mind)
- Retry: retry command-line (or resume)
- Fail: The object didn't do what was thought to (should have) happen. Mark object for removal? or downvote object (write to log).
- Alert: Send an alert message back to object creator that object failed (or going to do something destructive), with context as available.