1252 - big-picture memory layout

2 files changed, 16 insertions, 1 deletions

diff --git a/cpp/999spaces.cc b/cpp/999spaces.cc
new file mode 100644
index 00000000..ace149fc
--- /dev/null
+++ b/cpp/999spaces.cc
@@ -0,0 +1,15 @@
+//: Since different layers all carve out different parts of various namespaces
+//: (recipes, memory, etc.) for their own use, there's no previous place where
+//: we can lay out the big picture of what uses what. So we'll do that here.
+//:
+//:: Memory
+//:
+//: Location 0 - unused (since it can help uncover bugs)
+//: Locations 1-999 - reserved for tests
+//: Locations 1000 ('Reserved_for_tests') onward - available to the allocator in chunks of size Initial_memory_per_routine.
+//:
+//:: Recipes
+//:
+//: 0 - unused (IDLE; do nothing)
+//: 1-999 - all fixed code
+//: 1000 onwards - reserved for tests, cleared between tests
diff --git a/cpp/vimrc.vim b/cpp/vimrc.vim
index fa9adc79..42d17fc0 100644
--- a/cpp/vimrc.vim
+++ b/cpp/vimrc.vim
@@ -26,7 +26,7 @@ function! HighlightTangledFile()
 endfunction
 call HighlightTangledFile()
 autocmd BufRead,BufNewFile *.mu set ft=mu
-autocmd BufRead,BufNewFile 0* call HighlightTangledFile()
+autocmd BufRead,BufNewFile [0-9]* call HighlightTangledFile()
 
 " Scenarios considered:
 "   opening or starting vim with a new or existing file without an extension (should interpret as C++)