remove next_list from NamedList
Was legacy from the days of (linked) Frames Now only messages are linked
This commit is contained in:
@ -1,5 +1,5 @@
|
||||
|
||||
# A NamedList is for local variables arguments when calling methods.
|
||||
# A NamedList is used to store local variables and arguments when calling methods.
|
||||
# Also temporary variables, which are local variables named by the system
|
||||
|
||||
# The items are named (and typed) by the objects type instance. In effect the
|
||||
@ -9,9 +9,10 @@
|
||||
# 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 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
|
||||
# just constantly reused. Each message has two 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 named_list 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.*
|
||||
@ -21,7 +22,6 @@
|
||||
#
|
||||
module Parfait
|
||||
class NamedList < Object
|
||||
attribute :next_list
|
||||
|
||||
end
|
||||
end
|
||||
|
Reference in New Issue
Block a user