about summary refs log tree commit diff stats
path: root/cpp/010vm
Commit message (Collapse)AuthorAgeFilesLines
* 1094 - demarcate sections in layersKartik K. Agaram2015-04-171-1/+1
| | | | | | We have tangled vs regular comments, but they highlight the same. So we're still at 3 colors for comments. Anything more starts to seem gratuitous.
* 1077Kartik K. Agaram2015-04-171-4/+4
|
* 1073 - stop fixing the values of primitive recipesKartik K. Agaram2015-04-171-9/+7
| | | | | In the process I give up trace stability when I move files around, but I gain in exchange the ability to move files around.
* 1069 - rename record/field to container/elementKartik K. Agaram2015-04-161-10/+22
| | | | | | | | | This seems more obvious to laypeople. I've also come up with a design for sum types: I'm going to call them exclusive containers. You call 'get' on containers, 'index' on arrays, and 'maybe-convert' on exclusive containers (as well as tagged types, but that's even later).
* 1067 - no need to indent methods anymoreKartik K. Agaram2015-04-151-50/+49
|
* 1066 - bugfix: support string literals with colonsKartik K. Agaram2015-04-151-4/+0
|
* 1063 - variable names for surrounding spaces now workKartik K. Agaram2015-04-141-2/+2
| | | | This was a pain to debug.
* 1052Kartik K. Agaram2015-04-121-1/+1
|
* 1051Kartik K. Agaram2015-04-121-5/+5
|
* 1045Kartik K. Agaram2015-04-091-3/+5
|
* 1043 - clean up indent in generated mu.ccKartik K. Agaram2015-04-081-9/+9
|
* 1039Kartik K. Agaram2015-04-081-1/+2
|
* 1038 - clean up layer organization a littleKartik K. Agaram2015-04-081-2/+2
| | | | | Things are quite intricate to avoid reloading all recipes before every test. But mu wasn't really intended to sidestep intrinsic intricacy.
* 1035Kartik K. Agaram2015-04-081-1/+1
|
* 1034 - more test isolationKartik K. Agaram2015-04-081-0/+2
| | | | The layers are a mess now, but we'll take care of that later.
* 1032 - stop clearing types after every testKartik K. Agaram2015-04-081-1/+1
|
* 1031 - stop clearing recipes after every testKartik K. Agaram2015-04-081-2/+8
| | | | | I think the string-equal scenarios are failing to fail. But we'll fix them once we wrap up test isolation.
* 1011 - string-equal now workingKartik K. Agaram2015-04-031-0/+2
|
* 1007Kartik K. Agaram2015-04-031-1/+6
|
* 1004Kartik K. Agaram2015-04-031-1/+5
|
* 997Kartik K. Agaram2015-03-301-2/+2
|
* 996 - string literalsKartik K. Agaram2015-03-301-0/+10
|
* 994 - spaces now check boundsKartik K. Agaram2015-03-291-0/+1
| | | | I'm not testing for bounds-check errors yet, though.
* 986Kartik K. Agaram2015-03-271-0/+2
|
* 983 - arc 'integer-array' => c++ 'array:integer'Kartik K. Agaram2015-03-261-3/+3
|
* 982Kartik K. Agaram2015-03-261-1/+0
|
* 981Kartik K. Agaram2015-03-261-1/+1
|
* 980Kartik K. Agaram2015-03-261-5/+2
|
* 971Kartik K. Agaram2015-03-251-4/+2
|
* 966 - c++: starting on default-spaceKartik K. Agaram2015-03-211-0/+1
|
* 961 - done converting names?Kartik K. Agaram2015-03-201-0/+5
| | | | | | | | | | | I'm making two changes to how I compute field offsets: a) I just replace offset names up front, before I even manage field names. I don't bother disallowing x:integer and x:offset in the same function. Let's see if that leads us astray. Certainly saves code. b) I don't bother canonizing the first arg of a get since we know it has to have a type that is some number of 'address' followed by a record. Just assume that we have the right number of 'deref's.
* 959Kartik K. Agaram2015-03-201-0/+1
|
* 956Kartik K. Agaram2015-03-181-2/+3
| | | | Cleaner way to signal that a reagent's value has been computed.
* 949 - paving the way for jumps to labelsKartik K. Agaram2015-03-171-3/+2
| | | | Addresses for reagents are now computed after all transforms.
* 946 - selectively run just some testsKartik K. Agaram2015-03-171-7/+0
|
* 940 - c++: some changes to instruction modelKartik K. Agaram2015-03-161-16/+32
|
* 934 - extensible transform framework for mu's lightweight toolsKartik K. Agaram2015-03-161-0/+1
|
* 932 - clean up comments in the tangled c++Kartik K. Agaram2015-03-161-4/+6
|
* 917Kartik K. Agaram2015-03-141-0/+6
|
* 901Kartik K. Agaram2015-03-131-1/+4
|
* 832 - call-stack for C++ versionKartik K. Agaram2015-02-251-0/+1
| | | | | | | | | | These #defines and references now span many different layers. Let's see if the lack of encapsulation causes problems. Also interesting to run into a case where I need to modify a foundational layer and touch every single scenario/trace. Only alternative was to duplicate all the different layers that add instructions. Sign of problems with this model?
* 821Kartik K. Agaram2015-02-221-6/+2
|
* 815Kartik K. Agaram2015-02-221-4/+1
|
* 814Kartik K. Agaram2015-02-221-0/+4
|
* 810Kartik K. Agaram2015-02-211-1/+2
|
* 806 - start parsing reagent metadataKartik K. Agaram2015-02-211-2/+18
|
* 804 - reagent can have multiple typesKartik K. Agaram2015-02-201-10/+18
|
* 798 - start of record supportKartik K. Agaram2015-02-191-2/+9
|
* 789Kartik K. Agaram2015-02-191-6/+7
|
* 787 - arithmetic operationsKartik K. Agaram2015-02-191-4/+4
| | | | Lots of duplication here; we'll clean it up later.