Changeset 93d0ed3 for doc/theses/andrew_beach_MMath/features.tex

Timestamp:

Aug 12, 2021, 8:46:58 AM (2 years ago)

Author:

Peter A. Buhr <pabuhr@…>

Branches:

ADT, ast-experimental, enum, forall-pointer-decay, jacob/cs343-translation, master, new-ast-unique-expr, pthread-emulation, qualifiedEnum

Children:

c9f9d4f

Parents:

bfd7b30

Message:

fix problem in virtual type examples and figure

File:

• doc/theses/andrew_beach_MMath/features.tex (modified) (2 diffs)

doc/theses/andrew_beach_MMath/features.tex

@@ -165 +165 @@
 % The root type has no ancestors.
 % A type's descendants are its children and its children's descendants.
-Every virtual type also has a pointer to a virtual table with list of virtual members. Children inherit
-their parent's list of virtual members but may add new members to it.
-For example,
+Every virtual type (tree node) has a pointer to a virtual table with a unique
+@Id@ and a list of virtual members (see \autoref{s:VirtualSystem} for
+details). Children inherit their parent's list of virtual members but may add
+and/or replace members.  For example,
 \begin{cfa}
 vtable W0 | { int ?<?( int, int ); int ?+?( int, int ); }
-vtable W1 | { int w, int ?==?( int, int ); int ?-?( int, int ); }
+vtable W1 | { int ?+?( int, int ); int w, int ?-?( int, int ); }
 \end{cfa}
 creates a virtual table for @W0@ initialized with the matching @<@ and @+@
-operations visible at this declaration.  Similarly, @W1@ is initialized with
-@<@ and @+@ from the inheritance with @W0@, plus the @==@ and @-@ operations
-visible at this declaration. It is important to note that these are virtual
-members, not virtual methods of object-orientated programming, and can be of
-any type.
+operations visible at this declaration context.  Similarly, @W1@ is initialized
+with @<@ from inheritance with @W0@, @+@ is replaced, and @-@ is added, where
+both operations are matched at this declaration context. It is important to
+note that these are virtual members, not virtual methods of object-orientated
+programming, and can be of any type. Finally, trait names can be used to
+specify the list of virtual members.
 
 \PAB{Need to look at these when done.
@@ -187 +189 @@
 as if it were a method.
 \todo{Clarify (with an example) virtual methods.}
-
-Each virtual type has a unique id.
-This id and all the virtual members are combined
-into a virtual table type. Each virtual type has a pointer to a virtual table
-as a hidden field.
-\todo{Might need a diagram for virtual structure.}
 }%