Games/game-engines often can change scripts or even C code out on the fly, so they are at least partially build live.
Working in Smalltalk images can be "live-editing", if you run your application at the same time.
Both of these examples work on a method-basis: you change the code, trigger a rebuild the method and it is used from then on, not automatically after each change/keypress.
There is a bunch of live-coding stuff for creating music, but that often is used with smaller programs and writing the entire program as part of the performance.
I think here the more important thing is that it doesn't work on source code that is then parsed and compiled, but directly on a tree structure representing the program. Live-coding is sort of a side effect, because you a) don't have to reparse everything and b) always can have a state that is a valid program.
Working in Smalltalk images can be "live-editing", if you run your application at the same time.
Both of these examples work on a method-basis: you change the code, trigger a rebuild the method and it is used from then on, not automatically after each change/keypress.
There is a bunch of live-coding stuff for creating music, but that often is used with smaller programs and writing the entire program as part of the performance.
I think here the more important thing is that it doesn't work on source code that is then parsed and compiled, but directly on a tree structure representing the program. Live-coding is sort of a side effect, because you a) don't have to reparse everything and b) always can have a state that is a valid program.