From 455fbac64f101b05f7eaca89b84470569e4df3fd Mon Sep 17 00:00:00 2001 From: "Kartik K. Agaram" Date: Tue, 19 Jan 2016 23:18:03 -0800 Subject: 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. --- 050scenario.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to '050scenario.cc') diff --git a/050scenario.cc b/050scenario.cc index 5753be73..0680266e 100644 --- a/050scenario.cc +++ b/050scenario.cc @@ -99,9 +99,9 @@ scenario foo [ :(scenario read_scenario_with_bracket_in_comment_in_nested_string) scenario foo [ - 1:address:array:character <- new [# not a comment] + 1:address:shared:array:character <- new [# not a comment] ] -+run: 1:address:array:character <- new [# not a comment] ++run: 1:address:shared:array:character <- new [# not a comment] //:: Run scenarios when we run 'mu test'. //: Treat the text of the scenario as a regular series of instructions. -- cgit 1.4.1-2-gfad0