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. --- global.mu | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'global.mu') diff --git a/global.mu b/global.mu index 756469c1..b78ba47b 100644 --- a/global.mu +++ b/global.mu @@ -2,7 +2,7 @@ recipe main [ # allocate 5 locations for globals - global-space:address:array:location <- new location:type, 5 + global-space:address:shared:array:location <- new location:type, 5 # read to globals by using /space:global 1:number/space:global <- copy 3 foo @@ -10,5 +10,5 @@ recipe main [ recipe foo [ # ditto for writing to globals - $print 1:number/space:global + $print 1:number/space:global, 10/newline ] -- cgit 1.4.1-2-gfad0