Hi Caolán,<div><br></div><div>I was thinking in the LibreOffice identity too. Renaming the namespaces created by sun and other previous versions would help us to understand the code, but also would make we feel in a new software, a real community software. This is not so hard to do because C++ is powerful as we know, and if we try to imagine the suite in the future, is not great to maintain old names in the source, we need an identity! :-)</div> <div><br></div><div>Again, if you approve the idea, just pass this task for us, would be a pleasure.</div><div><br></div><div>Thanks for reply,</div><div>Júlio.<br><br><div class="gmail_quote">2011/4/19 Caolán McNamara <span dir="ltr"><<a href="mailto:caolanm@redhat.com">caolanm@redhat.com</a>></span><br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Fri, 2011-04-15 at 18:27 -0300, Júlio Hoffimann wrote:<br> > Hi devs,<br> ><br> ><br> > How hard is to rename all the C++ namespaces to most comprehensive and<br> > consistent names with the project?<br> <br> </div>Well, one fairly common pattern is sprinkled around of...<br> <br> namespace css = com::sun::star;<br> namespace cssu = com::sun::star::uno;<br> <br> Sticking e.g. an additional namespace alias of<br> <br> namespace libreoffice = com::sun::star;, or something of that nature, in<br> some header probably isn't the worst idea in the world. Though it does<br> generate a lot of churn to go around changing anything, and the other<br> language bindings, e.g. java and so on, wouldn't be affected, which i<br> guess has the potential for some extra confusion.<br> <br> C.<br> <br> <br> _______________________________________________<br> LibreOffice mailing list<br> <a href="mailto:LibreOffice@lists.freedesktop.org">LibreOffice@lists.freedesktop.org</a><br> <a href="http://lists.freedesktop.org/mailman/listinfo/libreoffice" target="_blank">http://lists.freedesktop.org/mailman/listinfo/libreoffice</a><br> </blockquote></div><br></div>