[Development] Is Qt allowed caching the home dir path?

Jiergir Ogoerg f35f22fan at gmail.com
Sun Oct 27 23:38:51 CET 2013


Probably, but then afaik it either (a) somehow can create barriers or (b)
implements
a broken but good enough solution like DCLP (double checked locking
pattern),
I couldn't figure out cause it uses Qt specific macros and functions.


On Mon, Oct 28, 2013 at 12:31 AM, Thiago Macieira <thiago.macieira at intel.com
> wrote:

> 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
>
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20131028/2c393abd/attachment.html>


More information about the Development mailing list