turn on qDESIGN_FLAW_WITH_MODULE_INIT_DEPENDENCIES_FROM_CPP_FILE even for windows - needed for release-logging builds - for same reason I ran into with gcc (i was using log2file there too)
minor tweak to qDESIGN_FLAW_WITH_MODULE_INIT_DEPENDENCIES_FROM_CPP_FILE
at least temporarily disable SingletonObjActualInitializer
Minor, hopefully innocuous, cleanups to Execution::ModuleInitializer code
initial incomplete attempt at Execution::DependableModule support for ModuleInit
cleanup Execution::ModuleInitializer<> code usage a bit
experimental use of new DependencyModule stuff for string depending on block allocation
experiment with variant Execution::ModuleInitializer strategy
experimental fix (use mewo Execution::DependableModule::Dependency stuff) for qDESIGN_FLAW_WITH_MODULE_INIT_DEPENDENCIES_FROM_CPP_FILE
more progress cleaning up new Depenednency support code
more cleanups to depenency code
final pass for now - on Execution::ModuleInitializer - seems to work OK - just needs better testing/docs/review (and then maybe another pass of rewriting)