about summary refs log tree commit diff stats
path: root/003trace.test.cc
Commit message (Collapse)AuthorAgeFilesLines
* 3547Kartik K. Agaram2016-10-221-1/+0
|
* 3294Kartik K. Agaram2016-09-021-3/+3
|
* 3267Kartik K. Agaram2016-08-281-2/+0
|
* 2547Kartik K. Agaram2015-12-241-0/+6
|
* 2258 - separate warnings from errorsKartik K. Agaram2015-10-061-4/+4
| | | | | | | 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.
* 1844 - explicitly end each trace lineKartik K. Agaram2015-07-251-17/+17
| | | | | | | | | 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.
* 1669 - now it fails in the right placeKartik K. Agaram2015-06-271-0/+5
| | | | ..when building until layer 41
* 1414 - traces now robust to new recipes/typesKartik K. Agaram2015-05-211-0/+21
|
* 1413Kartik K. Agaram2015-05-211-39/+12
|
* 1412 - starting to clean up trace formatKartik K. Agaram2015-05-211-47/+0
| | | | | 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.
* 1299 - stop using [] in any vectorKartik K. Agaram2015-05-071-10/+10
| | | | | | | | | 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/+169
I've tried to update the Readme, but there are at least a couple of issues.