about summary refs log tree commit diff stats
path: root/036call_ingredient.cc
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2015-05-12 18:08:47 -0700
committerKartik K. Agaram <vc@akkartik.com>2015-05-12 18:08:47 -0700
commitfca0ebbe0cc01d37e47822d8a62ea062a845f33d (patch)
tree557ef7d0bd5d3ddc98ab47cf0273c99cc4a09630 /036call_ingredient.cc
parent98f3a94201df11501d417ac2e75a756ab54ac873 (diff)
downloadmu-fca0ebbe0cc01d37e47822d8a62ea062a845f33d.tar.gz
1360 - store doubles in memory
This is a far cleaner way to provide *some* floating-point support. We
can only represent signed integers up to 2^51 rather than 2^63. But in
exchange we don't have to worry about it elsewhere, and it's probably
faster than checking tag bits in every operation.

Hmm, yeah, surprised how easy this was. I think I'll give up on the
other approach.

I still don't have non-integer literals. But we won't bother with those
until we need them. `3.14159:literal` seems ugly.
Diffstat (limited to '036call_ingredient.cc')
-rw-r--r--036call_ingredient.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/036call_ingredient.cc b/036call_ingredient.cc
index 5c321ef9..fe3ef1ed 100644
--- a/036call_ingredient.cc
+++ b/036call_ingredient.cc
@@ -23,7 +23,7 @@ recipe f [
 +mem: storing 0 in location 12
 
 :(before "End call Fields")
-vector<vector<long long int> > ingredient_atoms;
+vector<vector<double> > ingredient_atoms;
 index_t next_ingredient_to_process;
 :(replace{} "call(recipe_number r)")
 call(recipe_number r) :running_recipe(r), running_step_index(0), next_ingredient_to_process(0) {}