On 31/07/18 14:58, Edward Welbourne wrote:
I can believe static-built apps are common; and I guess apps using them would need to make source changes in order to switch to their namespaced form, or override the default of them being namespaced. What other problem(s) had you in mind ?
Exactly this problem: changing the default to a namespaced build would require source changes (*) in most applications that had been using static builds of Qt without namespaces. And this includes the applications affected by the bug that started this thread, so for them the solution won't just be "use this new version of Qt", it's going to be "use this new version of Qt AND change your source".
So, it's a matter to decide whether such namespacing should be opt-in (like today) or opt-out (if you get errors when you upgrade Qt and you don't want to fix your code, pass options to configure to disable the namespace).
(*) Sure, the changes are probably trivial (considering that would Qt also by default add a `using namespace QtNamespace` in all its headers), but it's still a SiC.
My 2 c, -- Giuseppe D'Angelo | [email protected] | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - The Qt, C++ and OpenGL Experts
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
