about summary refs log tree commit diff stats
path: root/082persist.cc
Commit message (Collapse)AuthorAgeFilesLines
* 1851Kartik K. Agaram2015-07-251-2/+2
|
* 1848 - core instructions now check for ingredientsKartik K. Agaram2015-07-251-3/+11
| | | | Also standardized warnings.
* 1844 - explicitly end each trace lineKartik K. Agaram2015-07-251-4/+4
| | | | | | | | | More verbose, but it saves trouble when debugging; there's never something you thought should be traced but just never came out the other end. Also got rid of fatal errors entirely. Everything's a warning now, and code after a warning isn't guaranteed to run.
* 1823 - restore sandboxes from previous sessionKartik K. Agaram2015-07-191-6/+16
| | | | | | Starting to feel some need to test this persistence support. Next time I'll create a fake storage handle and support for 'assume-storage filename'.
* 1822Kartik K. Agaram2015-07-191-2/+2
|
* 1817 - save for sandboxesKartik K. Agaram2015-07-181-7/+19
| | | | | | | No restore. We'll have to do that manually for the first lesson. The version control is also super ugly; every save creates a new commit. But that's ok; version control is just the backup of last resort.
* 1816 - ack, accidental namespace collisionKartik K. Agaram2015-07-181-4/+4
|
* 1815 - git commit only if lesson/.git existsKartik K. Agaram2015-07-181-0/+10
| | | | | We want to avoid accidentally mixing lessons into ourselves. Require users to git-enable it first.
* 1814 - save code in editorKartik K. Agaram2015-07-181-0/+50
Very rudimentary ability to read/write from file+version control. No control over name. Recipes now saved. But what to do about sandboxes?