4 ms·
AFAIK, there is always a separation between the program (represented by the code) and the process (the execution of the program by the machine). To “hyperprogra
by skydhash 4y ago
AFAIK, there is always a separation between the program (represented by the code) and the process (the execution of the program by the machine). To “hyperprogram”, we would need to merge the two. I view the program as a space-based entity and the process as a time-based entity. How do we map time to space? Especially if it's a non-deterministic process?
Lisp macros allow us to specify multiple versions of code at compile time. And Lisp conditions allow us to redefine or discard runtime contexts. But this time-based manipulation is simpler than what you seemingly want. The easiest way I can think of is to offer an API to track the evolution of types, but I'm guessing the performance hit would be heavy.
- pavlov 4y agoSmalltalk traditionally breaks this source vs. executable state dichotomy by using a single memory image where everything is an editable object, including the classes that contain the code. For persistence, the image is simply stored and reloaded in its entirety.