KDE 4 namespaces
Christian.Stoitner at gmx.net
Mon May 9 17:15:45 BST 2005
On Monday, 9. May 2005 12:53, Adam Treat wrote:
> On Monday 09 May 2005 11:00 am, Christian Stoitner wrote:
> > > You'll have the same problem with Qt then... QString and QLineEdit come
> > > from differeet libs, but they both start with Q.
> > > What can help for this, other than documentation, is #include
> > > <QtCore/QString> vs #include <QtGui/QLineEdit>, so maybe we want to do
> > > the same in KDE
> > >
> > > > One thing is the most important: consistency.
> > >
> > > ... with Qt? Then this means not using namespaces :)
> > I'am also a newbe, but i think Ilkka is right.
> > Why do you have to do everything like trolltech? as far as i know Qt
> > doesn't use namespaces because Qt runs on embeded systems too.
> Because we want (well, I'd like to see...) Qt-only developers to have a new
> look at kdelibs especially for those platforms opening up with Qt4. Making
> KDE coding guidelines as consistent as possible with the Qt reduces the
> headaches for beginners and/or people primarly familiar with Qt.
and you realy think K::Class oder Kde::Class or KdeCore::Class is so much
harder to understand than KClass?
everyone who ever coded with stl knows namespaces. so every c++ programmer
should be able to combine the stl way of using namespaces with the qt way of
writing apis ;).
More information about the kde-core-devel