about summary refs log tree commit diff stats
path: root/003trace.cc
Commit message (Collapse)AuthorAgeFilesLines
* 1921 - show trace by clicking on codeKartik K. Agaram2015-08-021-2/+10
| | | | | | | 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.
* 1844 - explicitly end each trace lineKartik K. Agaram2015-07-251-17/+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.
* 1782 - stop tracing anything but warnings inside editKartik K. Agaram2015-07-141-3/+5
| | | | | | | | | Speeds up edit.mu tests by 10x, and shrinks memory usage by 100x. We need a more efficient implementation of traces, but we can keep going for now. We didn't really need to reclaim memory just yet, after all. Mu is pretty memory-efficient.
* 1781 - the hog is Trace_stream, not MemoryKartik K. Agaram2015-07-141-0/+1
| | | | | I keep forgetting about it. Until, that is, I run gprof. Even if I think I need a memory profile, a cpu profile is a pretty good proxy.
* 1669 - now it fails in the right placeKartik K. Agaram2015-06-271-2/+5
| | | | ..when building until layer 41
* 1640Kartik K. Agaram2015-06-241-1/+1
| | | | | | | | Another bug in manually running the editor. At least show the error message when you raise warnings in console mode. Later we'll want to create a separate side channel and transparently plumb warnings to the 'menu bar' of the editor..
* 1614Kartik K. Agaram2015-06-211-0/+3
|
* 1501Kartik K. Agaram2015-05-281-5/+5
|
* 1417 - draft zoom levels in tracesKartik K. Agaram2015-05-211-4/+37
|
* 1416Kartik K. Agaram2015-05-211-15/+22
|
* 1415Kartik K. Agaram2015-05-211-25/+3
|
* 1414 - traces now robust to new recipes/typesKartik K. Agaram2015-05-211-6/+22
|
* 1413Kartik K. Agaram2015-05-211-28/+3
|
* 1412 - starting to clean up trace formatKartik K. Agaram2015-05-211-144/+26
| | | | | Many features of my trace layer were just inherited blindly from wart but lying unused in this project. Throw them out while we're at it.
* 1411Kartik K. Agaram2015-05-201-2/+5
|
* 1391 - avoid unsigned integersKartik K. Agaram2015-05-171-25/+25
|
* 1357 - temporarily revert floating-point supportKartik K. Agaram2015-05-121-1/+1
|
* 1356 - snapshot #2: floating point supportKartik K. Agaram2015-05-121-1/+1
| | | | | | | | | | | | | | | I added one test to check that divide can return a float, then hacked at the rippling failures across the entire entire codebase until all tests pass. Now I need to look at the changes I made and see if there's a system to them, identify other places that I missed, and figure out the best way to cover all cases. I also need to show real rather than encoded values in the traces, but I can't use value() inside reagent methods because of the name clash with the member variable. So let's take a snapshot before we attempt any refactoring. This was non-trivial to get right. Even if I convince myself that I've gotten it right, I might back this all out if I can't easily *persuade others* that I've gotten it right.
* 1354Kartik K. Agaram2015-05-121-4/+4
|
* 1308Kartik K. Agaram2015-05-081-0/+1
|
* 1299 - stop using [] in any vectorKartik K. Agaram2015-05-071-14/+14
| | | | | | | | | Useful check: $ grep "[^ '\"]\[[^\"]" *.cc \ |perl -pwe 's/\Wargv\[|\WTests\[|\Wframe\[|\WMemory\[|\WName\[|\WSurrounding_space\[|\WRecipe\[|\WType\[|\WRecipe_number\[|\WType_number\[|\WBefore_fragments\[|\WAfter_fragments\[//g' \ |perl -pwe 's/\Wargv\[|\WTests\[|\Wframe\[|\WMemory\[|\WName\[|\WSurrounding_space\[|\WRecipe\[|\WType\[|\WRecipe_number\[|\WType_number\[|\WBefore_fragments\[|\WAfter_fragments\[//g' \ |grep '[^ ]\['
* 1276 - make C++ version the defaultKartik K. Agaram2015-05-051-0/+478
I've tried to update the Readme, but there are at least a couple of issues.