| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 900 - c++: calling 'recipes' | Kartik K. Agaram | 2015-03-13 | 1 | -4/+21 |
| | | |||||
| * | 832 - call-stack for C++ version | Kartik K. Agaram | 2015-02-25 | 1 | -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 metadata | Kartik K. Agaram | 2015-02-21 | 1 | -0/+6 |
| | | |||||
| * | 804 - reagent can have multiple types | Kartik K. Agaram | 2015-02-20 | 1 | -0/+10 |
| | | |||||
| * | 802 - mu comments | Kartik K. Agaram | 2015-02-20 | 1 | -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++ version | Kartik K. Agaram | 2015-02-18 | 1 | -0/+150 |