4 ms·
To make this even more robust, steal a clever mechanism from Smalltalk -- the Change Log. Basically, all code changes and basically all of the manual manipulati
by stcredzero 14y ago
To make this even more robust, steal a clever mechanism from Smalltalk -- the Change Log. Basically, all code changes and basically all of the manual manipulation of state was kept in a transactional log, so you could be as daring as you'd like with exploratory programming without the fear of losing any code. (Mandatory for Smalltalk, because all coding was interactive runtime exploratory programming.)
For iPython, you'd want to implement one change log per source file, so for a source.py file, there'd be a source.py.log file in the same directory. Runtime changes would first write a patch to the source.py.log file at parse/compile time. Then if you ever crash iPython after doing an hour of exploratory coding, iPython could reload your changes after the source.py file. (Actually, you'd want a little ui to come up, giving you the option of leaving off the last few changes, so you can omit something that causes a crash.)
- voltagex_ 14y agoWould automating Git be too slow?
- intour779 14y agohttp://www.intour.com.vn/tour-du-lich-thai-lan.html http://www.intour.com.vn/tour-du-lich-thai-lan.html
- stcredzero 14y agoThere are problems with writing back out to source files and keeping pointers in source files from debugging sessions indexed correctly. The change log mechanism handily avoids this.