[Development] HEADS-UP: QStringLiteral

Tor Arne Vestbø Tor.arne.Vestbo at qt.io
Wed Aug 21 18:44:55 CEST 2019

> On 21 Aug 2019, at 18:30, Thiago Macieira <thiago.macieira at intel.com> wrote:
> On Wednesday, 21 August 2019 09:17:24 PDT Tor Arne Vestbø wrote:
>>> Remember that QStringLiteral today has a drawback: if you 
>>> unload the plugin it came from, any left-over uses of it may crash. That's
>>> one  of the many reasons we don't unload plugins, but other people
>>> might.
>> Is that the only drawback? Is that the only reason we’re not doing it?
> With a proper Qt 6 implementation, yes. Not right now in Qt 5, there are a few 
> more.

Qt 6 is fine 😊 That would be great!

>> On macOS plugins are never unloaded. Could the behaviour be dependent on
>> whether or not we’re building a plugin?
> All macOS plugins or just *our* plugins? QPluginLoader doesn't unload, but 
> QLibrary does.

I have to double check the dyld sources, but in many cases the dlclose will be a no-op, and the image won’t actually unload. One of these conditions was (if I recall correctly) if the library had any thread local storage. 

Tor Arne 

More information about the Development mailing list