about summary refs log tree commit diff stats
path: root/042name.cc
Commit message (Collapse)AuthorAgeFilesLines
* 1962Kartik K. Agaram2015-08-091-1/+1
| | | | Standardize test names.
* 1921 - show trace by clicking on codeKartik K. Agaram2015-08-021-1/+1
| | | | | | | Region to click on to edit is now reduced to just the menu bar for the sandbox (excluding the 'x' for deleting the sandbox). The symmetry there might be useful, but we'll see if the relative click area is in line with how commonly the actions are performed.
* 1909 - clean up all null pointers of that ilkKartik K. Agaram2015-07-311-0/+3
|
* 1904 - click on sandbox to edit itKartik K. Agaram2015-07-301-1/+1
|
* 1902Kartik K. Agaram2015-07-301-0/+2
| | | | Now fix the proximal cause of the write to address 0.
* 1882Kartik K. Agaram2015-07-291-2/+2
|
* 1875Kartik K. Agaram2015-07-281-1/+0
|
* 1873Kartik K. Agaram2015-07-281-11/+11
|
* 1872Kartik K. Agaram2015-07-281-22/+0
|
* 1869 - rename the /deref property to /lookupKartik K. Agaram2015-07-281-2/+2
| | | | Should be a little bit more mnemonic.
* 1868 - start using naked literals everywhereKartik K. Agaram2015-07-281-13/+13
| | | | First step to reducing typing burden. Next step: inferring types.
* 1848 - core instructions now check for ingredientsKartik K. Agaram2015-07-251-5/+8
| | | | Also standardized warnings.
* 1844 - explicitly end each trace lineKartik K. Agaram2015-07-251-10/+10
| | | | | | | | | 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.
* 1832Kartik K. Agaram2015-07-241-1/+1
|
* 1829Kartik K. Agaram2015-07-231-6/+8
|
* 1826 - edit: start carefully showing all errorsKartik K. Agaram2015-07-211-1/+1
| | | | | | | | | | | | | | | | | | | | | Eventually we might be able to get rid of die entirely. This is just a preliminary stab at a random error. In the process I ran into two issues that have impeded debugging before: a) Naming conflicts within scenarios are a real no-no. I need to warn on them, but the rules are getting complicated: Always print warnings on redefine But not in interactive mode Or in scenarios checking warning behavior Unless the scenario recipe itself is overridden b) Now that we've added collect_layers and a long time can go between traces, debugging is a minefield because trace lines don't print to screen immediately after they're created. Need to do something about that. Maybe explicitly trigger collection by tracing '\n' or something. These are the next two items on my todo list.
* 1768Kartik K. Agaram2015-07-131-0/+268