> -----Original Message----- > From: [email protected] [mailto:qt- > [email protected]] On Behalf Of > Christian Kandeler > Sent: Tuesday, July 09, 2013 1:00 PM > To: [email protected] > Subject: Re: [Qt-creator] Use of namespaces in Qt Creator's own code > > On 07/09/2013 11:11 AM, Oswald Buddenhagen wrote: > > to solve the clash problem, there are two approaches: > > - use an additional convention (ugly) > > - FooNames::Foo > > - Foo::FooClass > > - remove the redundancy > > - Foo::Plugin > > Definitely the latter. In general, I've come to resent this "double > namespacing" > that we do in a lot of places in Qt Creator (I am very much guilty of it > too). It's > probably a combination of mistrusting the C++ language and excessive use of > using directives. How about discouraging that for new plugins in the coding > conventions?
... only if the locator learns about namespaces, too. Right now I can type 'c FooPlugin' to get to the class. 'c Plugin' will bring up all kind of unrelated classes, and 'c Foo::Plugin" doesn't seem to work. Regards Kai PS: Yes, it's better to fix this in the locator instead of building the coding conventions around this missing feature. I don't have time to look into it, though ;) _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
