- Add the ability to protect VirtualMemory.

runtime/vm/object.cc

Index: runtime/vm/object.cc
===================================================================
--- runtime/vm/object.cc	(revision 9969)
+++ runtime/vm/object.cc	(working copy)
@@ -780,7 +780,6 @@
   cls = dynamic_class_;
   type = Type::NewNonParameterizedType(cls);
   object_store->set_dynamic_type(type);
-  core_lib.AddClass(cls);
 
   // Allocate pre-initialized values.
   Bool& bool_value = Bool::Handle();
@@ -6051,6 +6050,10 @@
   core_lib.AddImport(core_impl_lib);
   core_impl_lib.AddImport(core_lib);
   isolate->object_store()->set_root_library(Library::Handle());
+
+  // Hook up predefined classes without setting their library pointers.

[siva, 2012/07/27 01:55:00]

The comment on top seems more meaningful i.e.

// The class 'Dynamic' is registered in the class dictionary because it's name
is a built-in identifier, rather than a reserved keyword. It's name is not heap
allocated, because the class resides in the VM isolate. This class is registered
into the dictionary without setting the corresponding library pointer in the
class as it is in the VM isolate which is read only.

[Ivan Posva, 2012/07/27 18:02:56]

Added a better comment. The name should actually be setup for the shared classes
once we can properly use strings from the VM isolate.

+  const Class& cls = Class::Handle(Object::dynamic_class());
+  core_lib.AddObject(cls, String::Handle(cls.Name()));
 }