diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2015-08-06 17:34:28 -0700 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2015-08-06 17:35:29 -0700 |
| commit | af16d897d0ef023d8b653244a001b74f42cb5f66 (patch) | |
| tree | 36cff796b2c700f35ee89bc52703d4a9de449f91 /010vm.cc | |
| parent | 1132c9878e893e6dc356171dbf7826bfa47b4a38 (diff) | |
| download | mu-af16d897d0ef023d8b653244a001b74f42cb5f66.tar.gz | |
1945
Turns out it is indeed useful to insert code at multiple duplicate labels within a single (long) recipe. Like handle-keyboard-event in edit.mu.
Diffstat (limited to '010vm.cc')
| -rw-r--r-- | 010vm.cc | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/010vm.cc b/010vm.cc index 9e6b4e24..41a63e2c 100644 --- a/010vm.cc +++ b/010vm.cc @@ -35,6 +35,7 @@ struct instruction { recipe_ordinal operation; // Recipe_ordinal[name] vector<reagent> ingredients; // only if !is_label vector<reagent> products; // only if !is_label + // End instruction Fields instruction(); void clear(); string to_string() const; @@ -171,7 +172,9 @@ Next_recipe_ordinal = 1000; // consistent new numbers for each test //:: Helpers :(code) -instruction::instruction() :is_label(false), operation(IDLE) {} +instruction::instruction() :is_label(false), operation(IDLE) { + // End instruction Constructor +} void instruction::clear() { is_label=false; label.clear(); operation=IDLE; ingredients.clear(); products.clear(); } // Reagents have the form <name>:<type>:<type>:.../<property>/<property>/... |