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

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

diff --git a/ionnotes/node5.html b/ionnotes/node5.html
index 51c46f894c67e6f0217feffedb478d18346bab93..d3aba2e7d96c6cc553064f83c0e67646e0071b54 100644 (file)
--- a/ionnotes/node5.html
+++ b/ionnotes/node5.html
@@ -83,10 +83,10 @@ original version by:  Nikos Drakos, CBLU, University of Leeds
 <P>
 To keep Ion's code as simple as possible yet safe, there are restrictions
 when the WObj
 <P>
 To keep Ion's code as simple as possible yet safe, there are restrictions
 when the WObj

-<TT>destroy_obj</TT><A NAME="619"></A>
+<TT>destroy_obj</TT><A NAME="618"></A>

 function that calls watches, the deinit routine and frees memory may
 be called directly. In all other cases the 
 function that calls watches, the deinit routine and frees memory may
 be called directly. In all other cases the 

-<TT>defer_destroy</TT><A NAME="620"></A>
+<TT>defer_destroy</TT><A NAME="619"></A>

 function should be used to defer the call of <TT>destroy_obj</TT> until
 Ioncore returns to its main event loop. 
 
 function should be used to defer the call of <TT>destroy_obj</TT> until
 Ioncore returns to its main event loop. 
 


@@ -104,7 +104,7 @@ following cases:
       some reason failed to reparent the object to this frame.
 </LI>
 <LI>In a deferred action handler set with
       some reason failed to reparent the object to this frame.
 </LI>
 <LI>In a deferred action handler set with

-      <TT>defer_action</TT><A NAME="621"></A>.
+      <TT>defer_action</TT><A NAME="620"></A>.

       Like deferred destroys, other deferred actions are called when
       Ioncore has returned to the main loop.
 </LI>
       Like deferred destroys, other deferred actions are called when
       Ioncore has returned to the main loop.
 </LI>