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

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

diff --git a/ionnotes/node5.html b/ionnotes/node5.html
index a2634c26facf96bf4e83610e10c19731c673dc72..72551ec12a21d57cb8e6ee38939f7d4aa255950e 100644 (file)
--- a/ionnotes/node5.html
+++ b/ionnotes/node5.html
@@ -83,9 +83,9 @@ 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
-<TT>destroy_obj</TT><A NAME="615"></A>
+<TT>destroy_obj</TT><A NAME="631"></A>
 function that calls watches, the deinit routine and frees memory may
-be called directly. In all other cases the <TT>mainloop_defer_destroy</TT><A NAME="616"></A>
+be called directly. In all other cases the <TT>mainloop_defer_destroy</TT><A NAME="632"></A>
 function should be used to defer the call of <TT>destroy_obj</TT> until
 Ioncore returns to its main event loop. 
 
@@ -102,7 +102,7 @@ following cases:
       when the function created a frame to manage some other object but for
       some reason failed to reparent the object to this frame.
 </LI>
-<LI>In a deferred action handler set with <TT>mainloop_defer_action</TT><A NAME="617"></A>.
+<LI>In a deferred action handler set with <TT>mainloop_defer_action</TT><A NAME="633"></A>.
       Like deferred destroys, other deferred actions are called when
       Ioncore has returned to the main loop.
 </LI>