about summary refs log tree commit diff stats
path: root/034call.cc
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2015-07-04 09:40:50 -0700
committerKartik K. Agaram <vc@akkartik.com>2015-07-04 09:40:50 -0700
commit363be37f3f41db063ced940e310d6bba6ef82ef3 (patch)
tree66be4c5a6bf5b07f4fd5ed20eac64c3cfb062bd4 /034call.cc
parenta1968ebb48c06e1cbc2b813a73e4be235da7b3ee (diff)
downloadmu-363be37f3f41db063ced940e310d6bba6ef82ef3.tar.gz
1702 - experiment: start using 'ordinal' in names
It comes up pretty early in the codebase, but hopefully won't come up
in the mu level until we get to higher-order recipes. Potentially
intimidating name, but such prime real estate with no confusing
overloadings in other projects!
Diffstat (limited to '034call.cc')
-rw-r--r--034call.cc8
1 files changed, 4 insertions, 4 deletions
diff --git a/034call.cc b/034call.cc
index f36f987e..4c368bbf 100644
--- a/034call.cc
+++ b/034call.cc
@@ -34,10 +34,10 @@ recipe f [
 // recipe. When that finishes, we continue this one where we left off.
 // This requires maintaining a 'stack' of interrupted recipes or 'calls'.
 struct call {
-  recipe_number running_recipe;
+  recipe_ordinal running_recipe;
   long long int running_step_index;
   // End call Fields
-  call(recipe_number r) {
+  call(recipe_ordinal r) {
     running_recipe = r;
     running_step_index = 0;
     // End call Constructor
@@ -49,12 +49,12 @@ typedef list<call> call_stack;
 struct routine {
   call_stack calls;
   // End routine Fields
-  routine(recipe_number r);
+  routine(recipe_ordinal r);
   bool completed() const;
   const vector<instruction>& steps() const;
 };
 :(code)
-routine::routine(recipe_number r) {
+routine::routine(recipe_ordinal r) {
   calls.push_front(call(r));
   // End routine Constructor
 }