On Thursday 05 November 2015 18:23:37 Robin Burchell wrote: > On Thu, Nov 5, 2015, at 06:13 PM, Oswald Buddenhagen wrote: > > > Problem: performance impact, complexity of the atom/quark solution. > > > > to lessen the performance impact, we could have a #define to control the > > construction behavior of QSL at compile time. i'm not quite sure whether > > to make that opt-in or opt-out (safety vs. performance). > > Is the problem only apparent inside of plugins? Do we have a way to > detect whether someone is building plugin code at build time? (CONFIG += > plugin for qmake, I guess?) If so, couldn't the behaviour of > QStringLiteral differ for code inside of plugins, to that outside of > them?
Plugins and any library loaded by plugins that hadn't been loaded before. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
