more renaming of frame

lib/typed/parfait/message.rb

@@ -9,7 +9,7 @@
 
 module Parfait
   class Message < Object
-    attributes [:next_message , :receiver , :frame , :return_address ]
+    attributes [:next_message , :receiver , :named_list , :return_address ]
     attributes [:return_value, :caller , :name ]
 
     include Indexed
@@ -17,7 +17,7 @@ module Parfait
 
     def initialize next_m
       self.next_message = next_m
-      self.frame = NamedList.new()
+      self.named_list = NamedList.new()
       self.caller = nil
       super()
     end

lib/typed/parfait/named_list.rb

@@ -8,10 +8,10 @@
 # A Message with is arguments, and a NamedList make up the two sides of message passing:
 # A Message (see details there) is created by the caller and control is transferred
 # A NamedList is created by the receiver
-# PS: it turns out that both messages and frames are created at compile, not run-time, and
-#  just constantly reused. Each message has a frame object ready and is also linked
+# PS: it turns out that both messages and named_lists are created at compile, not run-time, and
+#  just constantly reused. Each message has a named_list object ready and is also linked
 #  to the next message.
-# The better way to say above is that a message is *used* by the caller, and a frame by the callee.
+# The better way to say above is that a message is *used* by the caller, and a named_list by the callee.
 
 # Also at runtime Messages and NamedLists remain completely "normal" objects.
 # Ie they have have type and instances and so on.*