nikhilgupta10
commented
7 years ago nikhilgupta10 imported these comments from Sourceforge: The user dchassin does not exist anymore. Therefore assigning this to afisher1. "dchassin": * owner changed from jcfuller to dchassin
-
status changed from new to assigned ,
"dchassin": * status changed from assigned to accepted ,
"dchassin":A new discussion item was added to Talk:Spec:Initialization. The OF_INIT flag should be used to prevent reinitialization.
,
"dchassin":By the way, the technical manual for initialization does not document the initialization sequence completely or correctly. For example, it is missing the require name test for V3 or later.
,
"jcfuller": * owner changed from dchassin to andyfisher
- priority changed from major to critical
- version changed from trunk to 3.0
- status changed from accepted to assigned
-
milestone changed from Unscheduled to Version 3.0 RC 1 ,
"jcfuller":Status?
,
"jcfuller": * version changed from 3.0 to 3.1
-
milestone changed from Version 3.0 RC 1 to Version 3.1 RC1 ,
"jcfuller":- Description has changed:
Diff:
- Milestone: Version 3.1 RC1 --> Version 3.1 Stable
- Resolution: --> none
-
Component: Core --> none ,
"dchassin":- Owner: Andy Fisher --> David P. Chassin
-
Milestone: Version 3.1 Stable --> Unscheduled ,
"dchassin":- Milestone: Unscheduled --> Version 4.0 RC1 ,
The spec is not really clear on whether objects that have already been initialized can be called to initialize again if some other object has deferred itself. I don't think an object that has successfully initialized should be called again, but the code in init_by_deferral() does this.
,