<div dir="ltr"><span style="font-size:small;text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">On Tue, Jul 31, 2018 at 2:43 PM, Kai Koehne<span> </span></span><span dir="ltr" style="font-size:small;text-decoration-style:initial;text-decoration-color:initial"><<a href="mailto:Kai.Koehne@qt.io" target="_blank" style="color:rgb(17,85,204)">Kai.Koehne@qt.io</a>></span><span style="font-size:small;text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><span> </span>wrote:</span><br style="font-size:small;text-decoration-style:initial;text-decoration-color:initial"><blockquote class="gmail_quote" style="font-size:small;text-decoration-style:initial;text-decoration-color:initial;margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br><br>I'm wondering how we can avoid symbol clashes in static Qt libs + user code.<br><br>a) Prefix all symbols with 'q', like we do for exported symbols.<br><br>This requires some bigger patches. See e.g.<span> </span><a href="https://codereview.qt-project.org/#/c/235631/" rel="noreferrer" target="_blank" style="color:rgb(17,85,204)">https://codereview.qt-project.<wbr>org/#/c/235631/</a><span> </span>for renaming all logging categories to 'qlc*' in qtbase.<br></blockquote><div style="font-size:small;text-decoration-style:initial;text-decoration-color:initial"><br></div><div>Isn't introducing a private namespace for that purpose an option?<br></div>I think it'd fare better than renaming the symbols, and in the end that's the whole reason for having them in the language, right?<br>Granted there should be an using clause at the top of the sources that use those private methods and explicit scoping for public headers (if any), but that should solve the problem I believe. Also patching it up should be relatively straightforward.</div>