about summary refs log tree commit diff stats
path: root/cpp/011load
Commit message (Collapse)AuthorAgeFilesLines
* 1189 - add extensions to all layersKartik K. Agaram2015-04-241-301/+0
| | | | | | I'm sick of fighting vim's filetype detection. No modeline and files highlight in random colors. I add a modeline and it stops highlighting tangle comments. Even though it read my #$%# vimrc! Fuck this shite.
* 1155 - three phases of mu: load, transform, runKartik K. Agaram2015-04-241-5/+5
| | | | | | Each phase implicitly calls previous phases. Most C++ scenarios implicitly call one, two or three of the phases. More clear now that 'load' does more than just add recipes.
* 1077Kartik K. Agaram2015-04-171-0/+1
|
* 1055Kartik K. Agaram2015-04-121-1/+1
|
* 1051Kartik K. Agaram2015-04-121-1/+1
|
* 1039Kartik K. Agaram2015-04-081-2/+2
|
* 1038 - clean up layer organization a littleKartik K. Agaram2015-04-081-1/+14
| | | | | Things are quite intricate to avoid reloading all recipes before every test. But mu wasn't really intended to sidestep intrinsic intricacy.
* 1036Kartik K. Agaram2015-04-081-0/+1
|
* 1031 - stop clearing recipes after every testKartik K. Agaram2015-04-081-1/+6
| | | | | I think the string-equal scenarios are failing to fail. But we'll fix them once we wrap up test isolation.
* 1030 - better test isolation for break/loopKartik K. Agaram2015-04-071-2/+9
| | | | | | | I've been resetting all recipes after every single test, but the arc version has shown that this gets slow all too quickly. And the longer I wait to fix it the harder it gets to fix. Already, boy, were this and the next couple of commits hard to track down.
* 1024 - basic skeleton for running scenariosKartik K. Agaram2015-04-061-2/+9
| | | | For now every scenario parses to the same dummy scenario.
* 1023Kartik K. Agaram2015-04-061-0/+4
|
* 1021 - extensible top-level command handler loopKartik K. Agaram2015-04-061-7/+9
|
* 1020Kartik K. Agaram2015-04-061-1/+1
|
* 997Kartik K. Agaram2015-03-301-28/+28
|
* 996 - string literalsKartik K. Agaram2015-03-301-1/+2
|
* 995Kartik K. Agaram2015-03-301-1/+1
|
* 949 - paving the way for jumps to labelsKartik K. Agaram2015-03-171-28/+28
| | | | Addresses for reagents are now computed after all transforms.
* 941 - c++: basic break/loop conversionKartik K. Agaram2015-03-161-0/+1
|
* 940 - c++: some changes to instruction modelKartik K. Agaram2015-03-161-26/+34
|
* 939 - c++: fix an old parsing hackKartik K. Agaram2015-03-161-0/+58
|
* 935 - permit '{' and '}' as legal labelsKartik K. Agaram2015-03-161-4/+3
|
* 932 - clean up comments in the tangled c++Kartik K. Agaram2015-03-161-1/+1
|
* 930Kartik K. Agaram2015-03-161-5/+6
|
* 919 - c++: run .mu files from commandlineKartik K. Agaram2015-03-141-3/+6
|
* 916Kartik K. Agaram2015-03-141-1/+1
|
* 900 - c++: calling 'recipes'Kartik K. Agaram2015-03-131-4/+21
|
* 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?
* 806 - start parsing reagent metadataKartik K. Agaram2015-02-211-0/+6
|
* 804 - reagent can have multiple typesKartik K. Agaram2015-02-201-0/+10
|
* 802 - mu commentsKartik K. Agaram2015-02-201-5/+11
| | | | | | Comments at end of line are still hacky; we just rely on the fact that excess ingredients do no harm. We'll need to be smarter when we get our first vararg recipe.
* 782 - promote literate version to canonical C++ versionKartik K. Agaram2015-02-181-0/+150
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-25 02:01:23 +0000