8.11: adda/oop/self's id:
7.28: intro:
. the expression tree being sent to number's type mgt
contains ptrs to the symbol table nodes;
and, those nodes include type tags .
. the symbol table is constant,
being part of the function's template;
the code points to symbol table nodes,
and then those nodes point to the stack,
or have immediate data if constant .
8.11:
. how does an object know its own id?
an expression tree sent to a type mgt
has a context (process, act'rec)
that tells it who the caller is,
and all the obj references in the expr'tree
are relative to that context .
. messaging an obj means calling its type mgt,
and then that type mgt is calling the methods
which then have access to the current context
as a global just like in assembly language
where programs have access to a current
stack pointer and program counter .
Subscribe to:
Post Comments (Atom)
8.16: adda/oop/self's attributes:
ReplyDelete8.15: 8.16:
. the term"(self) can have several uses:
the current subprogram can say self`call
to do an anonymous recursion;
and, we need names for the various levels of self:
suppose we have a process that
launches a subprogram that instantiates a record
that includes an object that activates a method
who wants to know about self .
. (self`person) would refer to the object;
( self`client`root) would refer to
the subprogram's act'rec .
12.8.28: co.self/dream/adda/oop/obj ID:
ReplyDeletein a dream I thought this:
. the act'rec is our only obj ID because
the obj's inside are its private components;
ie, why give private components their own id?
[ actually, these components do have id's,
they are just relative to the act'rec's id .]