2576 - distinguish allocated addresses from others

This is the one major refinement on the C programming model I'm planning
to introduce in mu. Instead of Rust's menagerie of pointer types and
static checking, I want to introduce just one new type, and use it to
perform ref-counting at runtime.

So far all we're doing is updating new's interface. The actual
ref-counting implementation is next.

One implication: I might sometimes need duplicate implementations for a
recipe with allocated vs vanilla addresses of the same type. So far it
seems I can get away with just always passing in allocated addresses;
the situations when you want to pass an unallocated address to a recipe
should be few and far between.

1 files changed, 4 insertions, 0 deletions

diff --git a/031address.cc b/031address.cc
index 7f2937e5..cc818a87 100644
--- a/031address.cc
+++ b/031address.cc
@@ -50,14 +50,17 @@ void canonize(reagent& x) {
 void lookup_memory(reagent& x) {
   if (!x.type || x.type->value != get(Type_ordinal, "address")) {
     raise_error << maybe(current_recipe_name()) << "tried to /lookup " << x.original_string << " but it isn't an address\n" << end();
+    return;
   }
   // compute value
   if (x.value == 0) {
     raise_error << maybe(current_recipe_name()) << "tried to /lookup 0\n" << end();
+    return;
   }
   trace(9999, "mem") << "location " << x.value << " is " << no_scientific(get_or_insert(Memory, x.value)) << end();
   x.set_value(get_or_insert(Memory, x.value));
   drop_from_type(x, "address");
+  // End Drop Address In lookup_memory(x)
   drop_one_lookup(x);
 }
 
@@ -89,6 +92,7 @@ bool canonize_type(reagent& r) {
       return false;
     }
     drop_from_type(r, "address");
+    // End Drop Address In canonize_type(r)
     drop_one_lookup(r);
   }
   return true;