diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2015-02-25 01:24:11 -0800 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2015-02-25 01:24:11 -0800 |
commit | 6f5d7864f6c0c62b8849349cb182c61f8dbed452 (patch) | |
tree | c4c22032dc09eefbc3b55268044d29607804c4fd /cpp/010vm | |
parent | dc3803320013059ad400853e3f6a2851f7f82c04 (diff) | |
download | mu-6f5d7864f6c0c62b8849349cb182c61f8dbed452.tar.gz |
832 - call-stack for C++ version
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?
Diffstat (limited to 'cpp/010vm')
-rw-r--r-- | cpp/010vm | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/cpp/010vm b/cpp/010vm index 28cdd2c0..a734305f 100644 --- a/cpp/010vm +++ b/cpp/010vm @@ -10,6 +10,7 @@ int Next_recipe_number = 1; // Recipes are lists of instructions. To run a recipe, the computer runs its // instructions. struct recipe { + string name; vector<instruction> steps; }; |