Talk:Spec:Initialization

Ftuffner 22:51, 15 March 2012 (UTC)

 * 1) For specification S4 and S5, does the distinction of " or greater" need to be specified?
 * 2) * Fixed. --Dchassin 23:17, 15 March 2012 (UTC)

jcfuller 16:17, 16 March 2012 (UTC)

 * 1) Maybe I'm just not seeing the how, but how can an object "know" whether another object has already performed its init function?  For example, when a transformer object looks at it's configuration object (which has no rank order dependence), how would it know that the configuration object has already been through init?
 * 2) * The object's clock is set after it has completed init, so a gl_* function can be written to allow objects to inquire whether init is done based on whether the clock is set. --Dchassin 17:55, 16 March 2012 (UTC)
 * 3) ** Not true. Some objects set their object->clock to the gl_globalclock as part of the init process, while others do not.  The object's clock is not set during init_all (in exec.c) or in object_init.  Using an 'OF_INITIALIZED' flag would be direct and unambiguous. -Mhauer 19:04, 16 March 2012 (UTC)
 * 4) * OF_INIT flag has been added to identify when an object is create but not yet initialized fully. The flag is cleared when the init process completes successfully on that object.

Dchassin 15:07, 26 April 2013 (UTC)

 * 1) /726 identifies an issue we need to address.  It is not clear in the spec whether objects that have already initialized should be initialized again if another object has deferred.  Reinitializing object could lead to race conditions.  OF_INIT should be used to determine whether init is called.