Search the Community
Showing results for tags 'dont_initialize'.
Found 1 result
From the docs, it is not quite clear if the scope of dont_initialize() is ALL unspawned processes, or just the ones already created when invoking dont_initialize(). "dont_initialize shall only be called in the body of the constructor ... only after having created an unspawned process instance within that same constructor or callback" From this sentence I guess that processes created *before* invoking dont_initialize() will not be executed in the constructor, but the ones *after* invoking will be executed. Am I right?