about summary refs log tree commit diff stats
path: root/082persist.cc
Commit message (Collapse)AuthorAgeFilesLines
* 2258 - separate warnings from errorsKartik K. Agaram2015-10-061-7/+7
| | | | | | | At the lowest level I'm reluctantly starting to see the need for errors that stop the program in its tracks. Only way to avoid memory corruption and security issues. But beyond that core I still want to be as lenient as possible at higher levels of abstraction.
* 2232Kartik K. Agaram2015-10-011-18/+39
|
* 2226 - standardize warning formatKartik K. Agaram2015-10-011-5/+5
| | | | | | | | Always show recipe name where error occurred. But don't show internal 'interactive' name for sandboxes, that's just confusing. What started out as warnings are now ossifying into errors that halt all execution. Is this how things went with C and Unix as well?
* 2196Kartik K. Agaram2015-09-141-3/+0
|
* 2183 - environment + external editor using tmuxKartik K. Agaram2015-09-121-1/+6
| | | | Thanks Jack and Caleb Couch for the idea.
* 2095Kartik K. Agaram2015-08-281-2/+0
| | | | | | | | | | | | Finally terminate the experiment of keeping debug prints around. I'm also going to give up on maintaining counts. What we really need is two kinds of tracing: a) For tests, just the domain-specific facts, organized by labels. b) For debugging, just transient dumps to stdout. b) only works if stdout is clean by default. Hmm, I think this means 'stash' should be the transient kind of trace.
* 1987Kartik K. Agaram2015-08-131-6/+0
|
* 1923Kartik K. Agaram2015-08-021-1/+1
| | | | | | | | | | Still iterating on the right way to handle incorrect number of ingredients. My first idea of creating null results doesn't really work once they're used in later instructions. Just add a warning at one place in the run loop, but otherwise only add products when there's something to save in them. Undoes some work around commit 1886.
* 1915 - restore expected response from diskKartik K. Agaram2015-08-011-5/+9
|
* 1913 - save expected response for each sandboxKartik K. Agaram2015-08-011-7/+15
|
* 1900Kartik K. Agaram2015-07-301-1/+2
|
* 1886 - gracefully handle malformed ingredientsKartik K. Agaram2015-07-291-2/+4
| | | | | | | | For example: x:number <- index y:address:array:number, 3 (forgetting to do a lookup) Thanks Caleb Couch.
* 1867 - keep tests from corrupting lesson/ directoryKartik K. Agaram2015-07-281-2/+4
|
* 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?