Someone already mentioned Forth, but I would like to tell a little about the history of Fort. Traditionally, Forth is a programming language that is its own operating system. Traditional Forth saves the program directly to disk sectors without using a “real” file system. He could afford to do this because he did not work directly with the processor without an operating system, so he did not need to play well.
Indeed, some implementations have Forth not only as an operating system, but also a CPU (in fact, many modern stack-based processors are designed as Forth machines).
In the original Forth implementation, the code is always compiled every time a string is entered and saved to disk. This is possible because Forth is very easy to compile. You just start the interpreter, play with the Forth defining functions as needed, and then just walk away from the interpreter. The next time you start the interpreter, all your previous functions still exist. Of course, not all modern Forth implementations work this way.
slebetman
source share