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. --- 055parse_tree.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to '055parse_tree.cc') diff --git a/055parse_tree.cc b/055parse_tree.cc index 947093b9..f9b15adb 100644 --- a/055parse_tree.cc +++ b/055parse_tree.cc @@ -71,7 +71,7 @@ container bar [ :(scenario dilated_reagent_with_new) recipe main [ - x:address:address:number <- new {(address number): type} + x:address:shared:address:number <- new {(address number): type} ] +new: size of <"address" : <"number" : <>>> is 1 -- cgit 1.4.1-2-gfad0 /a> summary refs log tree commit diff stats

path: root/tools/iso/kernel.soso/device.h

blob: ac85634b6a066bd076d5738f639d1cb6c81825f2 (plain) (blame)