On segunda-feira, 28 de outubro de 2013 00:12:36, Jiergir Ogoerg wrote: > Yep, I know, the solution I proposed was also thread safe, but it didn't > require a lock/unlock > on each function call or extra memory structs around it.
Q_GLOBAL_STATIC does not lock/unlock for every access. Only for the initialisation. > Anyway, I stumbled across the home > path thingy as a side effect of looking into a different Qt issue (startup > time, which is > pretty much unrelated to this issue) so I'll leave this (non-)issue for > later cause the > Qt start up time to me is far more important. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
