[svn-upgrade] Integrating new upstream version, ion3 (20070203)

[ion3-doc.git] / ionnotes / node3.html

diff --git a/ionnotes/node3.html b/ionnotes/node3.html
index 4f17c4e0a75dd3d340f55a7640d488083d85142a..0309e19e39ec3072217a2c6ac64b8e89aff4c0e4 100644 (file)
--- a/ionnotes/node3.html
+++ b/ionnotes/node3.html
@@ -64,11 +64,11 @@ original version by:  Nikos Drakos, CBLU, University of Leeds
 
 <P>
 First, to get things clear, what are considered objects here are C
-structures containing a properly initialized <A NAME="428"></A>
+structures containing a properly initialized <A NAME="427"></A>
 structure defined in <SPAN  CLASS="textit">ioncore/obj.h</SPAN> as the first element (or the
 first element of the structure which is the first element and so on which
 gives rise to inheritance). The WObj structure contains a pointer
-to a WObjDescr<A NAME="430"></A> class type info structure and
+to a WObjDescr<A NAME="429"></A> class type info structure and
 a list of so called ''watches''. The WObjDescr structure simply
 lists the class name, a table of dynamic functions and a pointer to
 deinitialisation function (or ''destructor'').
@@ -77,7 +77,7 @@ deinitialisation function (or ''destructor'').
 Ion does not do any reference counting, garbage collecting or other
 fancy things related to automatic safe freeing of objects with its
 simplistic object system. Instead special watches (the WWatch
-<A NAME="431"></A> structure) may be used to create safe references to
+<A NAME="430"></A> structure) may be used to create safe references to
 objects that might be destroyed during the time the specific pointer is
 needed. When an object is destroyed, its list of watches is processed,
 setting the pointers in the watches to NULL and the watch handlers for